Hi - I have searched FAQ and archives to find an answer. Hoping you can
help.
I have a new list (with previously imported addresses) for announcements
only, and wish these announcements to be received immediately.
I set the defaults to allow non-digest and to not allow digest.
I wish to send out announcements in html, and so wish to make the
default for new subscribers be MIME. While I see a setting under Digest
Options (MIME_is_Default_Digest), I don't see any equivalent option
under Non-Digest Options... and new subscribers continue to come in as
plain text.
QUESTIONS:
In order to avoid having to manually change this option for each
existing subscriber, is there a way to force all existing subscribers to
receive MIME in Non-Digest mode?
If not, is there a way to force all NEW subscribers to be enrolled with
MIME as their default?
Also, is there a way to "lock" the MIME switch on, so that users who try
to change their option to plain text will be prevented from doing so?
Thanks -
Steve
Recently, my Mailman list users who use either a HotMail or MSN.COM email address have not received any messages. Mailman does not record a "bounce" from these email addresses, but they do not receive any of the list traffic. When trying to send a message to a Mailman list, the user gets the following error message:
"This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed."
And it lists the Mailman list email address. However, Mailman does not receive a bounce message. (My server is not listed with SpamHaus.org, or any of the other blacklists, so it should not be a spam filter sort of thing).
One user requested help from MSN, and they responded with:
"You are experiencing this issue because your .Net Passport <user's email address here> Profile (which is extensively used for authentication purposes) is corrupted (not updated). In order to resolve this issue, I would suggest you to Update your .NET passport profile."
They follow that with instructions to go to their MSN .NET Passport profile and re-type all the information by hand (not by cut and paste). Then a 15-step procedure is given to delete all cookies, history and temporary internet files and re-set the disk cache (space for files) to 10MB. They believe that will solve the problem but alas, it has not for the 4 users I have with MSN or HotMail email addresses.
Anyone else run into this and resolved it? I didn't see anything in the archives. If any of you have users with MSN or HotMail addresses, be advised they probably will not be able to receive emails, but you will not get "bounce" messages. They only way they will know is if they try to post to a Mailman list.
Hi List
I have a (bit aged) Redhat 9 box (Pentium II/512Mb RAM) running Mailman
2.1.6 with Postfix. Its only has to run a single moderated mailing list
sending out one email every day to around 20,000 subscribers.
Sending out the emails is not problem - it works great. The major
problem is logging in to approve the email. It (Apache/2.0.40) is so
slow that it usually times out with a 500 error after you try and
login.
Is there a way of speeding up the web interface?
Can I approve postings from the command line?
There is a large archive as they have been running this for around 3
years. Will it speed up if we trash part of the archive. If so how can I
trash archived data that is (say) over a year old?
There was a thread on this problem, but it was not really resolved, and
that user had 450,000 subscribers.
Any help appreciated.
Jon Harris
Simple question,
would it be possible to run mailman on one host, and the Postfix MTA on
another host?
The reason is that I'm configuring a new in/outgoing server that
eventually should take over the "old" one, the old should keep the web
server functionality, so I'd like to split things up.
If it can be done, any hints on how?
--
Anders Norrbring
Norrbring Consulting
I just moved a client to Dreamhost from another provider where they
also had a Mailman discussion list.
Everything is working at Dreamhost, but they have a strange request.
They want all original posts to go to all subscribers as normal. BUT,
they want all replies to ONLY go to the original poster. But they
also want those replies to be archived so the entire list can choose
to view them or not.
I've looked through all of the Mailman config options and cannot find
a way to achieve what they want, even though they swear this is the
way it worked with their old host.
Is this possible, or are they on crack?
AJ
Hello Folks,
I recently setup a mailman server with ver 2.1.6, and I am liking it so far.
Since I am not with the IT Team of my organization, I am working around
some mailman problems and this is where I need some ideas.
I setup a few mail lists (including default mailman list) in
name.comdomain, and worked with my IT folks to redirect <maillist>@
name.com to my mail server <mailist>@mine.name.com
I do get a few <maillist-name>-bounce(a)name.com emails, and I would like to
re-direct all these emails to mailman(a)name.com (or mailman(a)mine.name.com)
Does someone have ideas how to accomplish this?
I do not administer the company's mail servers.
Folks here are not open to the list.name.com domain idea, for legacy
reasons.
I have a bunch of /etc/aliases entries for each of my mail lists on
mine.name.com server.
Is there a way I can use these alaises to re-firect <maillist-bounce>@
name.com to mailman(a)name.com
Any help / ideas are appreciated.
Thanks!
Tom
I've got a mailing list running successfully in Mailman, formerly on
my own server, now being hosted at Dreamhost. A peculiarity of their
implementation is that I don't have access to the archive files or any
of the other mailman-specific directories; or apparently to the
executables either (I haven't looked really hard, or asked; it's not
key to my question).
I've also got old archives of the mailing list, both old ezmlm
archives, and from a more recent incarnation a large mbox file
collected by a user (and a good thing, since I managed to lose my copy
in a disk meltdown).
What I think I want to do is leave the new/current mailing list, and
its archives, alone, and put up the old archives in my web space. (A
more aggressive approach would be to try to attach my old archives to
the beginning of the new/current archive, so everything would be in
one place. That would require a lot of reliance on Dreamhost tech
support, since I don't have access to those files/directories, and
they might not even be willing to do it.)
So, what executables and configuration settings are key to this? I
need to run "arch", it looks like, and have a mailing list configured
that will define where it puts the resulting HTML files. Maybe also
stuff to make the page templates match the rest of the website (I did
that for the ezmlm-cgi version). And I only have to do this once
(just to convert the old archives, static, no more messages).
Might I be better off approaching this via pipermail? I'm not really
clear, but I think that's a library for message archive handling,
which mailman uses for its archives? So it might have all the parts
of what I need, and maybe give me more freedom to write page layouts?
--
David Dyer-Bennet, <mailto:dd-b@dd-b.net>, <http://www.dd-b.net/dd-b/>
RKBA: <http://www.dd-b.net/carry/>
Pics: <http://www.dd-b.net/dd-b/SnapshotAlbum/>
Dragaera/Steven Brust: <http://dragaera.info/>
Oops... forgot to send my reply to the list too. Sorry about that
Bretton, I did not mean for you to receive it twice.
Bretton Vine wrote:
<snip>
>I understand the reason, but I need a non-technical, max 4 line rationale.
>Failing that I've been instructed to switch it off for /all/ the lists we
>host for corporate clients. Mind you that instruction stands regardless.
<snip>
>Can anyone shed some light (and yes, I've googled and gone through numerous
>FAQ answers which have bought me some time but not a reason why the default
>installation behaviour is as it is for BCC to lists etc)
---------------- End original message. ---------------------
I think that the answer is quite simply that it was a design decision
made based upon what the designers thought would be desirable for
most users. This is because quite often spammers use the BCC:
mechanism to try to avoid being pegged by certain anti-spam measures
that look at the number of destination addresses to help identify
bulk-mail attempts. Personally, I believe it to be a reasonable default.
Of course, there is absolutely nothing stopping you from turning the
setting off. You probably would want some pretty aggressive anti-spam
filtering and possibly graylisting enabled on your incoming queue of
your MTA if you do that.
To override the default setting for NEW lists, you can add the
following to your mm_cfg.py file:
DEFAULT_REQUIRE_EXPLICIT_DESTINATION = No
This will not change anything on the existing lists, you will have to
change them individually or en mass with a withlist script.
Dragon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hello,
I installed and configured mailman on Debian Sarge running apache2 and exim4.
I set up a list and the list adminstrator / owner can post to the list from a
remote client. I am pretty sure that the mailman config is right and that
there is a problem with the exim4 config. Non local subscribers cannot post
to the list. The Exim4 log always says that relay is not permitted.
/var/log/exim4/mainlog:
2006-09-01 00:00:52 H=mailout01.sul.t-online.com [194.25.134.80]
F=<k.oliver(a)t-online.de> rejected RCPT <news(a)server.windfinder.com>: relay
not permitted
Here are parts of my exim4 config:
[..]
# On Debian systems, the main binary is installed as exim4 to avoid
# conflicts with the exim 3 packages.
exim_path = /usr/sbin/exim4
# Macro defining the main configuration directory.
# We do not use absolute paths.
.ifndef CONFDIR
CONFDIR = /etc/exim4
.endif
# This sets a macro DC_minimaldns if dc_minimaldns=true. If
# dc_minimaldns=false, this expands to an empty line.
.ifndef DC_minimaldns
DEBCONFminimaldnsDEBCONF
.endif
# Create other macros from Debconf. Macros created here are used in
# other places in exim config.
.ifndef DC_visiblename
DC_visiblename=DEBCONFvisiblenameDEBCONF
.endif
# Create domain and host lists for relay control
# '@' refers to 'the name of the local host'
.ifndef MAIN_LOCAL_DOMAINS
MAIN_LOCAL_DOMAINS = DEBCONFlocal_domainsDEBCONF
.endif
domainlist local_domains = MAIN_LOCAL_DOMAINS
.ifndef MAIN_RELAY_TO_DOMAINS
MAIN_RELAY_TO_DOMAINS = DEBCONFrelay_domainsDEBCONF
.endif
domainlist relay_to_domains = MAIN_RELAY_TO_DOMAINS
.ifndef MAIN_RELAY_NETS
MAIN_RELAY_NETS = DEBCONFrelay_netsDEBCONF
.endif
hostlist relay_from_hosts = 127.0.0.1 : ::::1 : MAIN_RELAY_NETS
# Specify the domain you want to be added to all unqualified addresses
# here. Unqualified addresses are accepted only from local callers by
# default. The recipient_unqualified_hosts option can be used to permit
# unqualified addresses from remote sources.
# If qualify_domain is not set, the primary_hostname value is used for
# qualification.
# The ifdef bracket makes sure that an empty debconf value is correctly
# translated to "unset".
.ifdef DC_visiblename
qualify_domain = DC_visiblename
.endif
[..]
# Home dir for your Mailman installation -- aka Mailman's prefix
# directory.
# By default this is set to "/usr/local/mailman"
# On a Red Hat/Fedora system using the RPM use "/var/mailman"
# On Debian using the deb package use "/var/lib/mailman"
# This is normally the same as ~mailman
MAILMAN_HOME=/var/lib/mailman
#
# User and group for Mailman, should match your --with-mail-gid
# switch to Mailman's configure script.
# Value is normally "mailman"
MAILMAN_USER=list
MAILMAN_GROUP=daemon
#
# Domains that your lists are in - colon separated list
# you may wish to add these into local_domains as well
domainlist MAILMAN_DOMAINS=news.server.windfinder.com
#
# -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
#
# These values are derived from the ones above and should not need
# editing unless you have munged your mailman installation
#
# The path of the Mailman mail wrapper script
MAILMAN_WRAP=MAILMAN_HOME/mail/mailman
#
# The path of the list config file (used as a required file when
# verifying list addresses)
MAILMAN_LISTCHK=MAILMAN_HOME/lists/${lc::$local_part}/config.pck
[..]
begin routers
mailman_router:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.pck
local_part_suffix_optional
local_part_suffix = -bounces : -bounces+* : \
-confirm+* : -join : -leave : \
-owner : -request : -admin
transport = mailman_transport
[..]
begin transports
mailman_transport:
driver = pipe
command = MAILMAN_WRAP \
'${if def:local_part_suffix \
{${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
{post}}' \
$local_part
current_directory = MAILMAN_HOME
home_directory = MAILMAN_HOME
user = MAILMAN_USER
group = MAILMAN_GROUP
Any idea how to configure Exim4 to allow posting to mailing list for
subscribers like someone(a)somedomain.tld?
Hello,
Currently "View subscribers list" displays members in the following format:
first.last at my.domain.com
Is it possible to change the format to:
first.last(a)my.domain.com
Thanks
Tom
