Hi - I have searched FAQ and archives to find an answer. Hoping you can
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
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?
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.
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
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.
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
I have a bunch of /etc/aliases entries for each of my mail lists on
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.
we had some problems with apache2 and mailman - after upgrading the
server the lists are not shown anymore on the listinfo-site
Under /var/lib/mailman/list my lists are still there - i guess the
databaseconfig isn't read properly or could it be missconfiguration in
I recently installed mailman.
How do I stop mailman from sending a confirmation e-mail if the e-mail
address is already subscribed to the list?
Right now, a message is sent stating that the e-mail address is already
One of my users' messages are always sent out to list members with a
I have tried unsubscribing him and resubscribing him. Same result.
Most other members are posting fine (though some never bother!).
What could be causing this and how can I run diagnostics to trace the
problem? Or, even better, how can I fix it?
I am running Mailman v 2.1.7. I am not allowed to upgrade to 2.1.8 as
the installation is provided by a third party (CPanel) via my web host.
Recently I found a fairly huge amount of files in the shunt queue (around
1500). All I could gather from the error log is that most of them were from an
old bug in parsing weird charsets and the later ones were due to the post and
smtp-failur logfiles being owned by root. So I fixed the perms (had already
upgraded to 2.1.8 a month or so ago) and all was well.
Then I ran bin/unshunt.
Then people started complaining that they were getting a few hundred old
What am I missing here? From what I've been able to dig up on the list
archives the qfiles/shunt directory should only contain messages that never
made it out to any lists due to some error in config, perms or some bug in
mailman itself. But it's looking like these all did somehow make it through
mailman previously and were sent a second time. A few other tidbits:
-looking at some samples, msgids are the same, so it wasn't a user getting a
rejection and then posting again
-the dupes DO NOT show up in the web archive
Any other info I can supply here? Mailman 2.1.8, ruby 1.8.2, FreeBSD 4.7.
Bway.net - New York's Best Internet - www.bway.net
spork(a)bway.net - 212.655.9344
I wish to filter the emails to a mail list owner by doing the following:
insert the line:
I am using fedora core linux server system.
Thank you in advance for your reply.