Re: [Mailman-Users] Not all subscribers receive emails
I could temporarily solve the problem by simply restarting my server. Then, for about one whole week, everything went perfectly. But yesterday the same problem appeared again. It is not a real solution for me to restart my server weekly so does anybody have an idea? @Mark: Thanks, but SMTP_MAX_RCPTS is already set to 10 Mark Sapiro schrieb: Matthias Rank wrote: Hi everybody. I have a problem with Mailman. When I send an email to a list this won't be any problem for very little lists up to a size of about 15 subscribers. But if the list grows there are more and more people who don't receive emails and produce bounces like testlist: [EMAIL PROTECTED] bounce score: 1.0 or testlist: [EMAIL PROTECTED] has stale bounce info, resetting. The amazing is that there is no obvious system which persons do not receive emails, especially these are not always the same people and they are member of different email providers. Furthermore there are some (few) people who do hardly receive any email sent with Mailman although their email-accounts are okay. I'm using plesk, so any other mta than qmail won't work, if this might be the problem. I'm very confused and would be very glad about help. Some MTA in the delivery chain is not accepting more that 15 (?) recipients per message. Presumably, this is the qmail that Mailman is talking to. If it is your qmail, you may be able to adjust it to accept more recipients, or you can set SMTP_MAX_RCPTS = 10 in mm_cfg.py to tell Mailman to never send to more than 10 recipients per SMTP transaction. Once you do this, I think the bulk of your bounces will go away. Then you can investigate any remaining non-receipt problems. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing mm_cfg.py for existing lists
Hi, This problem is now solved, I think... Mark Sapiro ([EMAIL PROTECTED]) kirjoitteli (7.4.2008 17:55): SMTP_MAX_RCPTS is a setting that affects all SMTP delivery. It is not a list setting. Setting it in mm_cfg.py and restarting Mailman is all that is required. Ok, that's good to know for sure! Why do you think it isn't effective? After restarting Mailman I still got Too many recipients errors in the Sendmail log (maillog). Now I checked again, and there are still Too many recipients errors, but when I check later entries, I find out that the Hotmail emails have finally been sent. I didn't do any systematic checking, but on the basis of a small sample, it seems that everything works OK!! Note that if you mis spell SMTP_MAX_RCPTS in your mm_cfg.py setting, it won't work and there will be no complaint. That sure is easy to misspell - btw, misspell is one word, not two. :-D Hank van Cleef ([EMAIL PROTECTED]) kirjoitteli (7.4.2008 18:42): I think you will have to set the limit lower than 9. My list runs with SMTP_MAX_RCPTS = 5 Thanks Hank, We will let it be 9 now for a while - so far the list admins haven't complained. :-) If there will be problems again, I will lower the value, as you suggested. I'm glad I found this mailing list, it already proved helpful. Thanks all! - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. fax +358 9 493 981 * Mobile +358 40 771 2098 (only sms) [EMAIL PROTECTED] * http://www.greenspot.fi -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing mm_cfg.py for existing lists
On 4/8/08 5:20 AM, Jussi Hirvi at [EMAIL PROTECTED] wrote: Hi, This problem is now solved, I think... Mark Sapiro ([EMAIL PROTECTED]) kirjoitteli (7.4.2008 17:55): SMTP_MAX_RCPTS is a setting that affects all SMTP delivery. It is not a list setting. Setting it in mm_cfg.py and restarting Mailman is all that is required. Ok, that's good to know for sure! Why do you think it isn't effective? After restarting Mailman I still got Too many recipients errors in the Sendmail log (maillog). Now I checked again, and there are still Too many recipients errors, but when I check later entries, I find out that the Hotmail emails have finally been sent. The way you phrased that makes it sound like outgoing messages were merely being deferred for the too many recipients error and not bounced. If that's true, I hope you realize that changing the setting in Mailman only affects messages given to sendmail after you made the change. Anything already in sendmail's outgoing queue from before you made the change is not affected by the change as Mailman is no further involvement with the message at that point. -- Larry Stone [EMAIL PROTECTED] http://www.stonejongleux.com/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Changing mm_cfg.py for existing lists
Larry Stone ([EMAIL PROTECTED]) kirjoitteli (8.4.2008 14:35): The way you phrased that makes it sound like outgoing messages were merely being deferred for the too many recipients error and not bounced. Yes, exactly so. If that's true, I hope you realize that changing the setting in Mailman only affects messages given to sendmail after you made the change. Anything already in sendmail's outgoing queue from before you made the change is not affected by the change as Mailman is no further involvement with the message at that point. Yes, I realize that. - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. fax +358 9 493 981 * Mobile +358 40 771 2098 (only sms) [EMAIL PROTECTED] * http://www.greenspot.fi -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Bounces and disk quota exceeded
Greetings, Some of my list admins want to be able to know if any member of their lists are with disk quota exceeded. I am sending a message to a test list and I have created a user in our system with a very small disk quota. I know that this user has already his disk quota exceeded and I've verified that sending him a message directly from my personal email address. (I've received a message from my mbx server with the usual notification undelivered mail returned to sender I´ve set the parameter bounce_score_threshold to 0.5 and even now that member's subscription is not disabled and I, as the list owner, have not received any bounce notification. Can anyone tell me what is the issue, please ? ===|=== = Joao Sa Marta| Email: [EMAIL PROTECTED] = = Centro de Informatica|Tel: 239 853178 (directo) = = da Universidade de | Tel: 239 853170 (Geral) = = Coimbra | Fax: 239 853189 = = Apartado 3080| http://www.uc.pt/pessoal/samarta = = 3001-401 Coimbra | = ===|=== -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Not all subscribers receive emails
Matthias Rank wrote: I could temporarily solve the problem by simply restarting my server. Then, for about one whole week, everything went perfectly. But yesterday the same problem appeared again. It is not a real solution for me to restart my server weekly so does anybody have an idea? This does not seem to be a Mailman issue. It seems more likely to be something to do with your MTA. You need to go over your MTA logs and determine what messages are bouncing and why? -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Unsubscribe footer
How do you insert a line in the footer to include a direct link for unsubscribing similar to the one at the bottom of this list's emails? Thanks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Bounces and disk quota exceeded
João Sá Marta wrote: I am sending a message to a test list and I have created a user in our system with a very small disk quota. I know that this user has already his disk quota exceeded and I've verified that sending him a message directly from my personal email address. (I've received a message from my mbx server with the usual notification undelivered mail returned to sender I´ve set the parameter bounce_score_threshold to 0.5 and even now that member's subscription is not disabled and I, as the list owner, have not received any bounce notification. Can anyone tell me what is the issue, please ? Do you have bounce_processing and all three bounce notifications set to Yes? What's in Mailman's bounce and smtp-failure logs after you send to this test list? Does mail to the list-bounces address get properly delivered to Mailman? What happens if you send an ordinary message to the list-bounces address? -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Unsubscribe footer
[EMAIL PROTECTED] wrote: How do you insert a line in the footer to include a direct link for unsubscribing similar to the one at the bottom of this list's emails? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.015.htp regarding personalization. Once the list's personalize attribute is Yes, you can put Unsubscribe: %(user_optionsurl)s in msg_footer. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Phantom moderation pending requests heldmsg files
On Apr 7, 2008, at 6:03 PM, Mark Sapiro wrote:
Chris Waltham wrote:
A couple of weeks ago our Mailman 2.0 server crashed (a physical
problem, it wasn't Mailman's fault!) and we had to upgrade to 2.1
in a
real hurry. As a result, I had to copy the entire ~mailman/data
directory... which may not have been such a good idea:
[EMAIL PROTECTED] ~/data]$ ls -al | wc -l
40054
There are a _lot_ of files prefixed with heldmsg- in the data
directory, as you can see. There are entries all the way back to
2005,
in fact! I realize that I'm going to have to deal with all those
files
at some stage, but I currently have another problem.
Depending on what else you did, these files may now be orphans, but
see
http://www.python.org/cgi-bin/faqw-mm.py?
req=showfile=faq04.074.htp.
Thanks Mark, I'll check that out.
A user
administers a list called ams-announce, and they are receiving
emails with the subject The [EMAIL PROTECTED] mailing
list has 31 request(s) waiting for your consideration. However, when
they or I go to the admin interface, there are no pending requests.
The user has been getting the same message for more than a week now,
always with the same amount (31) of pending messages but there are
never actually any messages there for the admin to discard.
Oddly, there are no files prefixed with heldmsg-ams-announce in
the /
home/mailman/data directory, however I did grep for the string ams-
announce in _all_ heldmsg files and there are many matches --
virtually all of it looks like spam. I suppose, then, that I have two
questions:
* how can I print how many moderation requests a list has pending,
and
is there a way to flush the pending requests from the command-line?
(The FAQ entries deal with doing it via the web interface, before
2.1.5's feature of discard all messages)
* can I print a list of what lists have what files pending in the
format of heldmsg-$listname-$msgID, so that I can cross-reference the
files I have on the filesystem (many of which are really old) with
what the lists think need to be delievered?
First of all, the bogus '31 ams-announce moderator request(s)' email
is
almost certainly not coming from your current Mailman 2.1.9
installation. I have never seen a report of a case like this where the
email was not coming from some old/backup/test/whatever installation
whose cron/checkdbs was still being run.
Guess what? This report also fails your criteria... it was the old
server. :-( I thought I removed the NFS mount for mailman, but it was
in the automounter so the cron job could still successfully run!
That'll teach me for not just removing the user. And because the old
server had the same name as the new server and I wasn't a list admin,
I couldn't compare headers. Color me embarrassed...
Second, the '31' has nothing to do with data/heldmsg-* files. These
files have the messages themselves, but not the pending request
information. The data for the 'moderator request(s)' email come from
the lists/listname/request.pck file. If you want to see what's there,
you can dump it with bin/dumpdb, and you can clear it by simply
removing the file, although if you dump it first, I think you'll see
it's devoid of requests just like the admindb interface says.
Yep, I bet it is:
[EMAIL PROTECTED] ~/lists/ams-announce]$ dumpdb request.pck
[- start pickle file -]
- start object 1 -
{'version': (0, 1)}
[- end pickle file -]
Whereas if I run the dumpdb command on a list I know has outstanding
requests, I see the request itself. Guess I know how this works, now!
As far as getting a list of what messages are pending for each list in
the form heldmsg-$listname-$msgID is concerned, there's nothing that
will give you that in a nice list, but if you go to a specific list's
request.pck file and dump it with bin/dumpdb, you'll see one entry
like
'version': (0, 1)
and for each held message, entries like
id: (1, (time, sender, subject, reason, filename, msgdata))
and entries with 2 or 3 as the first item of the value which are held
subscribe and unsubscribe requests.
In the held message entries, the key, id, is the number you call
$msgID; time is the time in seconds that the message was held; sender,
subject and reason are self explanitory; filename is the name of the
held message file and msgdata is a dictionary of the message's
metadata at the time it was held.
Note that if you have any request.db files, these are residue from
your
prior installation. I don't know if you did an actual upgrade of your
2.0 installation to 2.1.9, but if you did, the data from the
request,db files should have been automatically migrated to the
request.pck files by bin/update as part of the 2.1.9 install. If that
isn't what happened, then I'm not sure what you're faced with in terms
of recovering any held messages.
With the exception of 3-4 lists (out of 800+), I let the make update
command run
Re: [Mailman-Users] Phantom moderation pending requests heldmsg files
Chris Waltham wrote: With the exception of 3-4 lists (out of 800+), I let the make update command run so I presume that actually upgraded the lists. I think I might just delete the holdmsg files en masse, I can't see why (organizationally) I should need to keep them. When you delete these files, it is better to use bin/discard as discussed in http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.074.htp rather than just rm. This is because bin/discard actually removes the held message from the requests.pck file (see below). However, if the heldmsg-* file is an orphan, it won't be removed by bin/discard, so you need to run bin/discard first and then rm any files left. The problem with just removing the heldmsg-* file is if there are a large number of held messages for a single list, the admindb CGI can time out trying to create the held messages page, and just removing the heldmsg-* files without also removing the request.pck entries won't cure this time out. I think I did remove pending_requests.db (or whatever it's called) when I did the upgrade, but I think it was empty anyway. You may be thinking of the global data/pending.db file, but this is different. The items in that file if any were moved to the list specific pending.pck file, and they are the confirmation tokens and associated data for actions waiting confirmation, they are not the actions waiting moderator approval which were in requests.db, now requests.pck. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] ANNOUNCE: GNU Mailman 3.0a1 (Leave That Thing Alone)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After far too long, I'm finally happy to announce the availability of GNU Mailman version 3.0 alpha 1, code name Leave That Thing Alone. Hopefully, I needn't point out that this version is not suitable for production. Instead, I'm making it available to provide an early snapshot of where Mailman 3 is going, and to give interested developers, users and integrators something real to play with. I am looking forward to your feedback and contributions, and I hope you will at least download the package and give what works a try. For now, I would prefer if all discussion about 3.0a1 were held on the mailman-developers mailing list. Please don't submit bug reports to SourceForge; it's far too early for that. Ideally, you'll be interested enough to create your own branches and push them to Launchpad for all of us to look at. For detailed information on 3.0a1, please read docs/ALPHA.txt. This will explain what works and what doesn't, how to run the test suite and how to actually create, populate, and deliver to some mailing lists. Much does not yet work, but everything that does work is very well documented using Python's doctest framework. Please note that Python 2.5 is required, but a C compiler is no longer needed. You will need some third party packages, but everything you need is available in the Python Cheeseshop. You can download both the tarball and egg file for 3.0a1 from the Cheeseshop as well: http://pypi.python.org/pypi/mailman/3.0.0a1 You'll probably want the source tarball. I hope you will find this first snapshot useful and encouraging. Please participate! Enjoy, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkf8JbMACgkQ2YZpQepbvXGtxgCguOrVEuZ61VnCe86nwkWHXGBm b7sAoLn2fUbRLDmRdWusYxfsAu21FAxw =eiPc -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
