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.
Dear List -
I recently have changed mail servers and my attempt at moving Mailman
appears to have only partially succeeded.
check_perms comes back fine - Good.
cron is running the news_port command every 5 minutes (good cron check)
The web interface works fine - all list look great - Good.
Mail sent to a list appears in a qfile - Good.
Qrunner is running - Good.
Mailmanctrl is running - Good.
Nothing is being sent to Postfix - Bad!!!
Qfile In directory purged just in case, still nothing.
Gentoo 2.6.13 running 2.6.13-gentoo.r3 kernel, 64-bit, on an AMD64 3000.
Postfix - but nothing fancy - no virtual domains, etc.
Mailman 2.1.5-r3 build via emerge into the standard location
Help!!! <with a smile>
I got the following error if some people using MS Outlook send mails
with german umlauts in the subject. Those mails don't go through! I'm
using Mailman 2.1.5 on debian woody. Is this a mailman or user side
Date: Wed, 29 Mar 2006 11:51:33 +0200
Mar 29 11:51:36 2006 (330) Uncaught runner exception: unknown encoding
Mar 29 11:51:36 2006 (330) Traceback (most recent call last):
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
sys.modules[modname].process(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 74, in
prefix_subject(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Handlers/CookHeaders.py", line 265, in
"/root/backport/mailman-2.1.5/debian/mailman/var/lib/mailman/pythonlib/email/Header.py", line 285, in append
LookupError: unknown encoding
I run several mailing lists under Mailman 2.1.6. Recently
one of my mailing lists received 2 spam messages, I was able
to delete one of them using the moderator admindb interface, but
when I tried to delete the second message, I got the "hit a bug"
page (traceback is listed below).
At that point I: ran check_db and check_perms, restarted the daemon,
cleared out the locks. No luck.
I found the heldmsg in data/ and deleted the message manually,
which seems to have made matters worse. Now when I access the
admindb web page for the mailing list, it throws the error right away before displaying the admindb page (same traceback as before).
I suspect I may have not deleted everything I need to delete. I have
considered upgrading to 2.1.7, but thought I should resolve this issue
Any advice would be greatly appreciated, thanks,
admin(24303): [----- Traceback ------]
admin(24303): Traceback (most recent call last):
admin(24303): File "/usr/local/mailman-2.1.6//scripts/driver", line 101, in
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Cgi/admindb.py", line 2
34, in main
admin(24303): num += show_helds_overview(mlist, form)
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Cgi/admindb.py", line 4
85, in show_helds_overview
admin(24303): mlist.HandleRequest(id, mm_cfg.DISCARD)
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/ListAdmin.py", line 167
, in HandleRequest
admin(24303): forward, addr)
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/ListAdmin.py", line 353
, in __handlepost
admin(24303): syslog('vette', note)
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/Syslog.py", lin
e 40, in write
admin(24303): self.write_ex(kind, msg, args, kws)
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/Syslog.py", lin
e 58, in write_ex
admin(24303): logf.write(msg + '\n')
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/StampedLogger.p
y", line 73, in write
admin(24303): Logger.write(self, "%s %s" % (prefix, msg))
admin(24303): File "/usr/local/mailman-2.1.6/Mailman/Logging/Logger.py", lin
e 91, in write
admin(24303): UnicodeError: ASCII encoding error: ordinal not in range(128)
admin(24303): [----- Python Information -----]
admin(24303): sys.version = 2.2.3 (#1, Mar 9 2006, 18:16:14)
[GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-53)]
admin(24303): sys.executable = /usr/bin/python
admin(24303): sys.prefix = /usr
admin(24303): sys.exec_prefix = /usr
admin(24303): sys.path = /usr
admin(24303): sys.platform = linux2
admin(24303): [----- Environment Variables -----]
Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.
After creating a new list with a (clearly not properly setup) new install of
mailman, when sending a message to the list address I get the following
This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 9): 550 <testlist(a)mydomain.com>: Recipient
address rejected: User unknown in local recipient table
I pulled my actual domain out of this error. Oddly enough all messages
regarding subscribing etc work just fine. Users simply cannot post
messages. Any ideas? Thanks.
I have around 32 aliases setup and they all are working fine with an
exception of one in particular which has around 140 users.
For some unknown reason sending mail to this alias, not everyone (140
users) on this list get messages. Few do and others don't?
Is there a way to check for corruption? What should I be looking for?
I'm kinda lost.
Any recommendation will be appreciated.
I'm running mailman v2.1.5-8 on debian (sarge).