Re: [Mailman-Users] GNU Mailman roadmap
* Barry Warsaw : [...] > Here's the plan: Mark is going to put a 2.1.13 bug fix release out soon > and will continue to fix only the most important bugs on the 2.1 branch. > He'll forward port those fixes to the 2.2 branch for the few people who > are running it from source, but there will never be a Mailman 2.2 > release. For all practical purposes, Mailman 2.2 is dead. Mark will be > joining me to focus all new development work on Mailman 3.0. Yay - go 49ers! ;-) Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Using Mailman with Multi Mail Server
* Hien HUYNH HUU : > Could Mailman be configured with multi mail server (at least 2 > mail server) at the same time ? So that It can transfer huge > numbers of emails at the same time . If yes, please let me know > how to configure It. I'm pretty sure you are doing it wrong (configuring your MTA, I mean) - or perhaps you are simply limited badnwith-wise. You might want to show us you MTA/Mailman integration so that we can come up with some helpful hints. Other than that, I think you have three options: 1. Get a load balancer. Their prices are down to the low five digit range nowadays. 2. Build yourself a load balancer (helpful Google keywords might be "ldirector", "linux lvs" and "pacemaker", "openais", "heatbeat" for availability). 3. If mail is leaving your MTA at a slow rate but the delivery from Mailman to the MTA is fast, try running several queue runners and specify an SMTPHOST wit a DNS record pointing to several addresses (I'm not really sure about this one, perhaps Mark could clarify). Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Wer schläft, sündigt nicht. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] OT: Yahoo Deferrals
Hello Ralf, * Ralf Hildebrandt : > * Jeff Grossman : >> I have a question regarding Yahoo deferrals. I know this subject has >> been talked about a lot. Everything I could find via Google was from at >> least a year ago though. I was wondering if anybody has found new ways >> of limiting the Yahoo deferrals? I run two mailing lists. > > I run (with others) mail.python.org, and we send assloads of mail to > yahoo! > > What we did: > > * set up DKIM for python.org > * subscribed to/set up Yahoo's FBL: http://feedbackloop.yahoo.net/ > * made sure that whoever complains @yahoo gets unsubscribed silently > within a jiffy. > > We haven't seen any large scale deferrals for a long time now. I second that. > I also use: > yahoo.com slow: > in transport_maps with > > slow unix - - - - - smtp > in master.cf and > > slow_delivery_rate_delay = 1s > in main.cf This, OTOH, is a pretty interesting choice - you do limit yourself to 100 * 3600 mails per hour (you didn't show any slow_destination_concurrency_limit settings, so I'm assuming stock process limits) and that really makes a difference? Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #19: voll konfigurierbar - nicht vorinstalliert. (Peter Berlich) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] OT: Yahoo Deferrals
* Jeff Grossman : > I have a question regarding Yahoo deferrals. I know this subject has > been talked about a lot. Everything I could find via Google was from at > least a year ago though. I was wondering if anybody has found new ways > of limiting the Yahoo deferrals? I run two mailing lists. Each one is > an announcement only list which I send one message to each week. One > list is about 12,000 users and the other is about 9,000 users. I have > noticed that a majority of the e-mail addresses are from yahoo.com so I > get a lot of the deferral messages and it takes a little while to get > them all sent out. Here is what I have done so far. > > I am running Mailman version 2.1.12. I have full personalization turned > on to help with bounces. I have all of the verp options turned on: > > VERP_CONFIRMATIONS = Yes > > VERP_PROBES = Yes > > VERP_PERSONALIZED_DELIVERIES = Yes > > Everything on the mailman side is working pretty well. > > I am running Postfix 2.6.3. I have the following configuration settings > in my main.cf file: > > slow_destination_recipient_limit = 5 You are using VERP - every message will be sent with one recipient only, so you can safely remove this setting. > slow_destination_concurrency_limit = 2 > > slow_destination_concurrency_failed_cohort_limit = 4 You are limiting yourself to eight temporary failures before Yahoo! is declared dead. A higher failed_cohort_limit (e.g. 2000) would allow far more temporary failures before delivery to Yahoo is suspended. I suggest you give it a try once and compare the results. I further suggest checking you logs and looking for scache entries (conn_use=x in delivery lines and it's own scache entries). Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Recursive: Adj. See Recursive -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] MM admin interface wide open
* Mark Sapiro : > Mark Sapiro wrote: > > >Ulf Hofemeier wrote: > >> > >>PS. if you email me, I can provide you with the URL to my MM installation. > > > > > >If you send it to me, I'll check it out. > > > After a little off list back and forth, Ulf wrote: > > >I had no site admin password set. Setting one with mmsitepass did the > >trick. Thank you for pointing this out. Maybe it would be worthwhile > >to add a line of code that checks whether a site admin pass has been > >set for future versions? I tried to find a solution for my problem on > >your mailman-user list, but couldn't. I have a hard time believing > >that I'm the only one who has run into this problem though. > > > >Thank you for looking into it. Great support and I appreciate it :-) > > > Not having ever set a site password should not cause this problem. If > the password was never set, there would be no data/adm.pw file at all > and authenticating the site password should fail. > > I think this issue could only occur if at some point someone actually > set a null site password. > > Still, it's worth fixing it so that a null password doesn't work. I > can't see that anyone would actually want passwordless access to the > admin interface except maybe in the case of a server that was not > exposed on the internet al all, but probably not even then. > > Does anyone need to have null passwords work in Mailman? I could only think of a corporate server, where the directories containing Mailman's admin interface are protected by e.g. Kerberos/LDAP (i.e. Active Directory). Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman + postfix = strange behaviour
* Marek Kozlowski : >> The message is delivered to a maildir store. I guess this is not a >> Mailman problem, but a Postfix one. Perhaps you got address rewriting >> wrong - is the mail really supposed to be delivered to >> kozlo...@alpha.mini.pw.edu.pl with the local(8) delivery agent? After >> all, your mail address seems to be kozlo...@mini.pw.edu.pl, without >> the "alpha" part - but I don't know your mail setup. > > Normal mail sent to any of the followings: > > kozlo...@alpha.mini.pw.edu.pl > m.kozlow...@alpha.mini.pw.edu.pl > kozlo...@mini.pw.edu.pl > m.kozlow...@mini.pw.edu.pl > > is delivered OK! I couldn't possibly know that ;-) Well, so this is now really a Postfix problem. I suggest adding "-v" to the "local" stanza in master.cf, execute "postfix reload", send another mail, capture the log data and ask on postfix-users. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman + postfix = strange behaviour
* Marek Kozlowski : > Stefan Förster wrote: >> There is a wiki entry for this at http://wiki.list.org/x/A4E9 which >> describes various strategies to troubleshoot this problem. >> >> In my personal experience, this is a very helpful ressource, and >> checking everything that is mentioned there has helped me often in the >> past. > > Didn't help. > > This is a part of /var/log/mail.log . Seems *everything* is OK... but I > got NO mail... > > Aug 20 12:49:12 alpha amavis[11953]: (11953-14) FWD via SMTP: > -> > ,BODY=7BIT 250 2.0.0 Ok, id=11953-14, > from MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as 127EB2A203E The lsit messages is reinjected to Postfix, the queue ID is 127EB2A203E. > Aug 20 12:49:12 alpha postfix/local[12267]: 127EB2A203E: > to=, > orig_to=, relay=local, delay=0.15, > delays=0.07/0/0/0.07, dsn=2.0.0, status=sent (delivered to maildir) The message is delivered to a maildir store. I guess this is not a Mailman problem, but a Postfix one. Perhaps you got address rewriting wrong - is the mail really supposed to be delivered to kozlo...@alpha.mini.pw.edu.pl with the local(8) delivery agent? After all, your mail address seems to be kozlo...@mini.pw.edu.pl, without the "alpha" part - but I don't know your mail setup. When using a content_filter, you should make sure that you only do virtual address rewriting once, i.e. either the main smtpd (or the one you use for injecting messages generated by Mailman) _or_ the smtpd used for reinjection from amavisd-new should have set "receive_override_options=no_address_mappings" - only one, not both of them, preferarbly the one used for reinjection from amavisd-new. Anyways, this is getting off-topic. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman + postfix = strange behaviour
* Marek Kozlowski : > :-) > I have Gentoo, Postfix and Mailman > I've configured according to > http://www.gnu.org/software/mailman/mailman-install/node13.html > The bahaviour is very strange: > > - mail do my mailing list goes to ML archive -- OK > > - if there are wrong adddressess (cause I have deleted some users) I got > the error in logs: > " User unknown in local recipient table; > from= to= " -- OK > > - I can see in logs: > " myserver postfix/local[7449]: 2DC4B2A2052: to=, > relay=local, delay=0.2, delays=0.08/0/0/0.12, dsn=2.0.0, status=sent > (delivered to command: /usr/lib64/mailman/mail/mailman post somelist)" -- > OK > > Everything seems OK but no mail sent to mailing list is delivered to no > user's mailbox. What's wrong?? There is a wiki entry for this at http://wiki.list.org/x/A4E9 which describes various strategies to troubleshoot this problem. In my personal experience, this is a very helpful ressource, and checking everything that is mentioned there has helped me often in the past. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Strange Wiki entry for Postfix Tuning
* Mark Sapiro :
> Stefan Förster wrote:
> > list_lists | awk '(NR > 1){print $1}' | \
>
> or
>
> list_lists --bare | \
Thank you, tbh, I didn't read list_lists manpage.
> > I'm running a Debian package of Mailman and I know that it is
> > modified, I just don't know to which extent. Perhaps someone with more
> > knowledge could comment on the availability of those two helper
> > commands in a standard Mailman installation? Perhaps they must be
> > executed as the Mailman user, or with some special environment.
>
>
> In the standard source distribution, all the command line commands
> including list_lists and list_members are available in Mailman's bin/
> directory and run from there without any special environment.
>
> They do need to be run directly or via sudo by root or some user in
> Mailman's group.
That makes sense. The Debian package takes care to create symlinks to
those binaries in /usr/sbin, but it's good to know where to find those
on non-Debian systems.
> Is it the case in Debian that any user on a shared system can run say
> list_members on any list?
Since Mailman's "bin" directory has 755 permissions on Debian, every
user can attempt to run these commands. Most directories (except
private archives) in /var/lib/mailman have world read/execute
permissions, but it seems that the actual data is owned by group
"list" and only readable by group/owner. So running either
"list_lists" or "list_members " result in a EPERM traceback.
Cheers
Stefan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Strange Wiki entry for Postfix Tuning
* Ralf Hildebrandt :
> * Stefan Förster :
> > | smtp_mx_session_limit (default: 2)
> >
> > While I can certainly imagine larger sites having somewhere between
> > five to ten MXs, 100 seems a bit... oversized.
>
> maybe it tries to set a very hight threshold, thus ALWAYS using ALL
> MXes?
You don't have an infinite amount of smtp(8) delivery agents, and you
don't want to keep them all busy trying the 14th MX of a destination
which is most probably dead.
What you actually want to do is ensure that you try at least
floor($num_mx / 2) + 1
different hosts (hello, greylisting!). Mailman can help you in solving
this:
list_lists | awk '(NR > 1){print $1}' | \
while read list; do
list_members $list
done | cut -d@ -f2 | sort -u > /tmp/domains
num_mx=0; while read domain; do
num_tmp=$(dig $domain mx +short | wc -l)
if [ $num_tmp -gt $num_mx ]; then
num_mx=$num_tmp
fi
done < /tmp/domains
echo "Maximum number of MX entries: $num_mx"
echo "smtp_mx_session_limit should be: $((num_mx/2+1))"
In my case, this script returns "7", so smtp_mx_session_limit should
be "4". The problem with this script is, however, that it relies on
"list_lists" and "list_members" being available to a user with shell
access.
I'm running a Debian package of Mailman and I know that it is
modified, I just don't know to which extent. Perhaps someone with more
knowledge could comment on the availability of those two helper
commands in a standard Mailman installation? Perhaps they must be
executed as the Mailman user, or with some special environment.
Cheers
Stefan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Strange Wiki entry for Postfix Tuning
* Ralf Hildebrandt : > Bary Warsaw or Brad Knowles. According to my knowledge they haven't > married. I might be wrong though. Barry, Brad, I apologize. No offense intended. Lack of coffee. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Strange Wiki entry for Postfix Tuning
Hello, I've discovered that the FAQ at http://wiki.list.org/x/rIA9 mentions to set smtp_mx_session_limit=100. While normally, I would reject such a suggestion as outright wrong, I noticed that this were comments made by Barry Knowles, and you don't just ignore hints from someone with that much experience in mailing lists. So, what is the reason for that setting? From man 5 postconf: ,[ man 5 postconf | less +/^smtp_mx_session_limit ] | smtp_mx_session_limit (default: 2) | | The maximal number of SMTP sessions per delivery request before | giving up or delivering to a fall-back relay host, or zero (no | limit). This restriction ignores sessions that fail to complete | the SMTP initial handshake (Postfix version 2.2 and earlier) or | that fail to complete the EHLO and TLS handshake (Postfix version | 2.3 and later). | | This feature is available in Postfix 2.1 and later. ` While I can certainly imagine larger sites having somewhere between five to ten MXs, 100 seems a bit... oversized. Any hints/insights are really appreciated. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Help!! Spam Flood!
* Mark Sapiro wrote: > There are many tools available for dealing with spam at this level that > are much more effective than Mailman is. Since I've read this several times in the past months, it makes me wonder if it is planned to drop some of the content filtering features that mailman provides in MM3. I really hope that MM3 will continue to provide at least the possibility to cut some unwanted attachment types, ignore the HTML part of a mail and so on. I totally agree that spam prevention is a much more suitable task for a MTA or a dedicated content filtering framework like amavisd-new, but I think that some minimal filtering functionalitiy should be retained in MM3. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Message Delays
* stevenmark1...@aol.com wrote: > Hi i run a mailman list and am having complaints from members because , for > example an email is sent to the list at 0800 hrs and they are not > receiving it until 2300hrs , the members all have different isp mailboxes > from a > variety of isp's , the message is hitting the server from the sender but is > very erratic at getting to peoples inboxes , any ideas as to why , as the > company i buy the list through say there are no issues with the list when > quite clearly there are Without the mailserver's logs, this is hard to debug. The next time a message is delivered with a large delay, find out the message-id of that post to the list, and try asking the company running your list for you for the following details: 1. The time the message with the given message id and the recipient who had a complaint entered the queue of that company's mail server. 2. The time of all delivery attempts to the receivers mail server. If there is more than one attempt, they should provide you with the errors which prevented a successful delivery. Since not all of your list's subscribers have problems receiving the mail in a timely manner I don't think this is a mailman problem at all. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Der Preis der Freiheit ist ewige Wachsamkeit! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
* Brad Knowles wrote: > on 7/8/09 6:12 PM, Stefan Förster said: > >> Thanks for your advice, Brad. The problem is that, due to policy >> reasons, outgoing mail has to pass a content filter, running locally >> on the Mailman box. With VERP... > > Chuq von Rospach wrote some stuff in the FAQ detailing his experience > with how VERP impacted performance on the systems he was managing. Of > course, this doesn't necessarily apply directly to your case, but it is > instructive to read. To be honest - I never understood where he got his numbers from. Or to be more precisely, how he got that lucky (note that I obfuscated the listname): # list_members mylist | cut -d@ -f2 | sort | uniq -c | sort -rn | head -3 1414 gmx.de 1009 web.de 404 freenet.de # list_members mylist | wc -l 2966 For that list, there would be 5 connections from Mailman to the local MTA for 2827 recipients, followed by <= 139 connections for the remainder of the whole list, i.e. no more than 144 delivery attempts. With VERP, there would be 2966 connections from Mailman to the local MTA. With the content filter set up the way it is, without VERP, the MTA would create no more than 144*2 queue files and the content filter would in turn create 144 subdirectories with about 3 files each, for a total of 720 files and 144 directories created/unlink'd. VERP'd, I'd have to create/unlink 14830 files and 2966 directories. And yes, I know that the MTA might create more than one file per message delivery - I was assuming the "best case". Perhaps I just got "unlucky" with the recipient distribution for that particular list - if it is of any importance to the lsit archives, I'd gladly investigate other lists I'm running. Or perhaps you could provide some live data from python.org lists? BTW - will MM3 be able to utilize the VERP features offered by many modern MTAs? >> I guess I will simply move the list server to another computer (and a >> different network). > > OTOH, moving the mailing list function to a different server and > separating that from the content scanning system is also a good idea, > including lots of other reasons. My main reason to move the whole installation is mainly that in another network, I don't have to scan every outgoing message. After all, it's not Mailman's fault that the box is heavily loaded. > Good luck, and I hope that this works out for you. Thank you, Brad. Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
* Brad Knowles wrote: > on 7/8/09 11:56 AM, Stefan Förster said: > >> Bummer. There is no way to implement that, our mailing list server is >> already suffering from too much traffic, it's quite old hardware, >> after all. > > Take a look at the stuff on "performance tuning" in the FAQ. Even > really old hardware can perform amazingly well, if it's tuned correctly. > I guarantee that you would be astonished at what I can achieve with an > ancient Compaq Pentium-133 laptop with 64MB of RAM and a 10GB hard drive > (upgraded from 1GB). > > If you've already done as much performance tuning as you can do, then > obviously you're not going to squeeze any more blood out of that turnip. > But I would suggest that you familiarize yourself with these sections > to make sure that you're actually doing as much as you can. Thanks for your advice, Brad. The problem is that, due to policy reasons, outgoing mail has to pass a content filter, running locally on the Mailman box. With VERP... I guess I will simply move the list server to another computer (and a different network). Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Rewriting or identifying late bounces
* Mark Sapiro wrote: > Stefan Förster wrote: >> generated by recipi...@intern.example.com >> mailbox is full: retry timeout exceeded >> >> Is there any way to rewrite those addresses or to help Mailman >> identify those bounces correctly? >> >> And yes, this a pretty stupid thing to do on their ISPs part... > > > Mailman has a whole host of heuristic recognizers for non-compliant DSNs, > but it doesn't try to guess if a non-member bouncing address might be a > munged version of a member address. Because it's a pretty stupid thing to do - at least the fact that addresses are not rewritten twice. > The 'best' solution for recognizing original recipients of bounced > messages is Mailman's VERP like capability. This puts the original > recipient's address in the envelope sender address so the envelope in this > case is from invalidlist-bounces+recipient=example@lists.incertum.net. > When the bounce is returned to that address, the MTA delivers it to the > list-bounces address and Mailman recognizes the original recipient as > recipi...@example.com from the envelope recipient of the DSN. > > The cost of this approach is that Mailman has to send an individual > message to the outgoing MTA for each recipient. Bummer. There is no way to implement that, our mailing list server is already suffering from too much traffic, it's quite old hardware, after all. Thanks anyways Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #283: whoami - Whoami ist nur was für Leute mit Alzheimer! (Begründung von Microsoft Deutschland für das Entfernen des Befehls aus Windows NT) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Rewriting or identifying late bounces
Hello world, some of my list members have a mail address like recipi...@example.com - nothing special about that. When mail is delivered to their address, their ISPs mail server rewrite the address internally to recipi...@intern.example.com and try to deliver them to the users mailbox. If for any reason, e.g. quota, this fails, a NDR/DSN is sent with the new name: Received: from mout3.example.com (mout3.example.com [195.4.92.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.incertum.net (Postfix) with ESMTPS for ; Tue, 7 Jul 2009 23:09:54 +0200 (CEST) Received: from [195.4.92.10] (helo=0.mx.example.com) by mout3.example.com with esmtpa (ID exim) (port 25) (Exim 4.69 #92) id 1MOHvF-000306-UO for invalidlist-boun...@lists.incertum.net; Tue, 07 Jul 2009 23:09:53 +0200 Received: from mbox134.example.com ([195.4.93.134]:43037) by 0.mx.example.com with esmtpa (ID exim) (port 25) (Exim 4.69 #79) id 1MOHvF-0001Qz-H2 for invalidlist-boun...@lists.incertum.net; Tue, 07 Jul 2009 23:09:53 +0200 Received: from exim by mbox134.example.com with local (Exim 4.69 #91) id 1MOHvF-0007qp-Dc for invalidlist-boun...@lists.incertum.net; Tue, 07 Jul 2009 23:09:53 +0200 X-Failed-Recipients: recipi...@intern.example.com Auto-Submitted: auto-replied From: Mail Delivery System To: invalidlist-boun...@lists.incertum.net Subject: Mail delivery failed: returning message to sender Message-Id: Date: Tue, 07 Jul 2009 23:09:53 +0200 X-purgate-ID: 149285::1247000993-22A6-9D72E1E7/0-0/0-18 This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: save to inbox generated by recipi...@intern.example.com mailbox is full: retry timeout exceeded Is there any way to rewrite those addresses or to help Mailman identify those bounces correctly? And yes, this a pretty stupid thing to do on their ISPs part... Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 You're here because you know something...you can't explain but you feel it... that there's something wrong with the world. --Morpheus, from The Matrix -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] How to unshunt?
* Ulf Dunkel wrote: > >> On Unix, for various reasons, the current directory is normally *not* >> in the search path for commands. You need to prefix the command name >> with the directory name (for current directory, you can abbreviate >> that to "./") like this: >> >> calamus:/var/lib/mailman/bin# ./unshunt > > Cool - thank you for pointing me to this. Works fine. I just wonder why > various other executables in the mailman/bin folder are executed without This is getting way offtopic, but a quick type command follwed if needed by ls -l $(which command) where "command" is one of the binaries you can execute (i.e. without a leading "./" in mailman/bin) will probably enlighten you :-) Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman + Postfix - Too Many Connections
* "Lie, Jafaruddin" wrote: > We sent out mailing lists to schools here in Australia, and recently we've > been getting "Too Many Connections #421" errors from them. Mails destined to > gmail or hotmail are OK. Not really a mailman problem, have a look at: http://www.postfix.org/QSHAPE_README.html#backlog Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Eher hält der Mensch das Feuer im Munde als ein Geheimnis. - Petronius -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Patch for use of Postfix VERP support
* Jesper Dybdal wrote: > If anybody should be interested, I've placed the modified patch, > directly usable for 2.1.11, at > http://www.dybdal.dk/mailman-2.1.11-postfix-verp.patch Uh oh. I remember that patch, I've even tested it (German: http://www.incertum.net/archives/307-Postfix,-Mailman-und-XVERP.html), but it was incomplete (I found that out only weeks after I had written that test). I don't remember any specific details, but there were definitely problems with double VERP'ifying. Something with the monthly reminders. Whatever you do, don't simply go live with this one, perform more testing first: Password reminders, monthly membership reminders, moderation messages, reject messages and so on. Don't get me wrong, being able to reduce the number of queue files created can be a major performance increase on busy servers, the above patch just doesn't cut it. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Archives and International Character Sets(Mailman2.1.11)
* Mark Sapiro wrote:
> Stephen J. Turnbull wrote:
>
>> Mark Sapiro writes:
>>
>>> add_language('en', 'English (USA)', 'utf-8', 'ltr')
>>
>> Shouldn't this probably be default by now?
>
>
> Yes, it should. But, we have superstitious beliefs that something
> unintended will be broken by this. Yet, I continue to suggest it as a
> workaround, and I've never recieved a report of a problem, so I will
> at least test it as default for Mailman 2.2.
If changing a language definition like that, doesn't that mean one
will have to change the various predefined template files, all message
codes for that language and after that recreate the archive files?
Ciao
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
"The brain is a wonderful organ. It starts working the moment you get up in
the morning, and does not stop until you get into the office."
-- Robert Frost (1874-1963)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Recommended way to get subscriber list with full names?
* Jan Steinman <[EMAIL PROTECTED]> wrote: > My client needs to periodically get a list of subscribers, including > the names they entered, and to have a count. > > I put 'list_members -f -p NewsletterName | sort -d -b -f' in a php > script with secret URL for her to use, but it is failing with > "Permission denied: '/private/var/mailman/lists/newslettername/ > config.pck'." What does "periodically" mean? Once every five minutes? Do you really need real time data? If you followed the installation instructions carefully, you created a dedicated user who owns Mailman files and directories and can execute the command cited above. Simply execute the command as this user, write the output to a defined location and then have your PHP script read that file and display it. Judging from the error message above, you are running MacOS X which supports the traditional Unix "cron" daemon as well as a new service called "launchd". You can use both of them to create the required output periodically. If you did not create a dedicated user for Mailman during installation then I'm out of ideas. Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #203: Öffentliche Adressverzeichnisse - Spammers Umschreibung für das Usenet. (Marc Haber) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Postfix, Mailman, and postfix-to-mailman.py trouble
Followup to myself:
* Stefan Förster <[EMAIL PROTECTED]> wrote:
> * Craig Stacey <[EMAIL PROTECTED]> wrote:
>> master.cf:
>> mailmancom unix - n n - - pipe
>> flags=FR user=list argv=/www/lists.example.com/bin/postfix-to-
>> mailman.py ${nexthop} ${user}
>> mailmanorg unix - n n - - pipe
>> flags=FR user=list argv=/www/lists.example.org/bin/postfix-to-
>> mailman.py ${nexthop} ${user}
>> mailmannet unix - n n - - pipe
>> flags=FR user=list argv=/www/lists.example.net/bin/postfix-to-
>> mailman.py ${nexthop} ${user}
[...]
>> All the docs specify you should put this line in main.cf:
>>
>> mailman_destination_recipient_limit = 1
Did you do that?
I.e., did you specify:
mailmancom_destination_recipient_limit = 1
mailmanorg_destination_recipient_limit = 1
mailmannet_destination_recipient_limit = 1
Ciao
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
"The axiom 'An honest man has nothing to fear from the police'
is currently under review by the Axiom Review Board" -- Terry Prachett, "Men At
Arms"
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Postfix, Mailman, and postfix-to-mailman.py trouble
* Craig Stacey <[EMAIL PROTECTED]> wrote:
> master.cf:
> mailmancom unix - n n - - pipe
> flags=FR user=list argv=/www/lists.example.com/bin/postfix-to-
> mailman.py ${nexthop} ${user}
> mailmanorg unix - n n - - pipe
> flags=FR user=list argv=/www/lists.example.org/bin/postfix-to-
> mailman.py ${nexthop} ${user}
> mailmannet unix - n n - - pipe
> flags=FR user=list argv=/www/lists.example.net/bin/postfix-to-
> mailman.py ${nexthop} ${user}
>
>
> transport:
> lists.example.com mailmancom:
> lists.example.org mailmanorg:
> lists.example.net mailmannet:
>
> /var/log/mail.info:
>
> Oct 27 14:39:23 owney postfix/pipe[16420]: 0788A8F6B2:
> to=<[EMAIL PROTECTED] >, relay=mailmancom, delay=0, status=sent
> (lists.example.com)
> Oct 27 14:39:23 owney postfix/pipe[16420]: 0788A8F6B2:
> to=<[EMAIL PROTECTED] >, relay=mailmancom, delay=0, status=sent
> (lists.example.com)
> Oct 27 14:39:23 owney postfix/pipe[16420]: 0788A8F6B2:
> to=<[EMAIL PROTECTED] >, relay=mailmancom, delay=0,
> status=sent (lists.example.com)
You are sending three messages to three different localparts
([EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]) in one domain (lists.example.com), so
Postfix is using the same transport - pretty normal so far.
> Then, from /www/lists.example.com/logs/smtp, we see only one come out
> the other side:
>
> Oct 27 14:39:23 2008 (2652) <[EMAIL PROTECTED]
>> smtp to core-other for 2 recips, completed in 0.013 seconds
I think the "post" logfile would be more interesting.
> Three messages go in, one comes out the other end.
>
> I did some logging, and found that postfix-to-mailman.py is only
> processing *one* message. The script gets the listname from this line:
>
> local = sys.argv[2]
>
> All the docs specify you should put this line in main.cf:
>
> mailman_destination_recipient_limit = 1
>
> I can find no documentation on that particular config, but it seems
> like it's telling postfix to only put one recipient per message when
> sending to mailman, which would jibe with what the variable setting in
> the above script is looking for.
No, since sys.argv[1] should yield the ${nexthop} setting from
master.cf, i.e. the recipient domain (which is ignored by the script).
> However, it looks like that setting is totally being ignored by our
> postfix install. If I type "postconf", I do *not* see
> "mailman_destination_recipient_limit" listed in the output. That
> seems to me to indicate to me that it's not being honored.
That's perfectly normal - any custom variables defined in main.cf
don't show in postconf -n output.
Ciao
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
Wenn Frauen nicht mehr wissen, was sie tun sollen, ziehen sie sich aus, und das
ist wahrscheinlich das
Beste, was Frauen tun können.
Samuel Beckett
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
[Mailman-Users] Feature reqeust for wiki.list.org - short URLs
Hello world, first of all, the Mailman wiki at http://wiki.list.org/ is really very helpful. I've come to find it's structure very clean and easy to understand. Especially the FAQ part is very, very helpful and saved me lots of time when trying to troubleshoot a problem. But - there is one thing about the length of URLs. Let's consider for example (long line incoming): http://wiki.list.org/display/DOC/4.16+How+do+I+prevent+duplicate+copies+of+email+coming+to+the+list If I click on Tools -> Info, the wiki presents me the shorter URL: http://wiki.list.org/x/eoA9 Do you think it's possible to modify the wiki code as to present this shorter URL on every page so that one could copy the short link without having to call Tools -> Info? Cheers Stefan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Default cahrset for 'de' to ISO8859-15/UTF-8?
* Mark Sapiro <[EMAIL PROTECTED]> wrote: > Stefan Förster wrote: >> >> I wonder if there are any plans to change the default charset for the >> 'de' locale of Mailman to anything else than ISO8859-1, because this >> charset cannot even represent our current currency symbol. > > There are no short term plans to change character sets, but if you were > to publish a bazaar branch with your changes (on launchpad or elsewhere) > and post a note about it to the [EMAIL PROTECTED] list so > that the possible implications such as for German speaking Swiss users > could be discussed, we could easily pick your changes up. I don't have any idea what you mean by "Bazaar branch", but I will look into the mailman-developers archive and I found the launchpad resository for Mailman. > Longer term, Mailman is moving to full unicode internally and utf-8 > encoding. That's good news. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Mac OS X ate my ~/.signature. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Default cahrset for 'de' to ISO8859-15/UTF-8?
Hello world, I wonder if there are any plans to change the default charset for the 'de' locale of Mailman to anything else than ISO8859-1, because this charset cannot even represent our current currency symbol. I have changed this myself for now (adding needed variables to mm_cfg.py, converting translated templates to the new charset, recreating pod files), but I think it _might_ be a good idea to change the default charset for all languages spoken mostly by countries which are in the 'Euro' currency zone to at least ISO8859-15. I acknowledge there might be some difficult cases (for exmaple, in Switzerland, there are people who might be interested in running a mailing list with a 'de' or 'fr' locale, but they don't use the 'Euro' as currency there). Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Insanity isn't a disease, it's a way of life -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Any way to prevent un-subscribing?
* Elizabeth Schwartz <[EMAIL PROTECTED]> wrote: > Our administration wants to use a mailman list for broadcast-only > official communications to students. > I've been asked to prevent the students from un-subscribing. Is there > a way to do that in any version of mailman? And/or any other > convenient mechanism? The list is a bit unwieldy for plain email > aliases. If you are using some kind of "aliases" file where "listname-unsubscribe" points to the "mailman" script, remove that alias. Deactivate your web interface or generate random passwords for every student and block access to the page where one can reset passwords. Remove the "listname-request" alias, too, so students can't use Mailman's advanced features to unsubscribe themselves. Probably not what you wanted to hear, isn't it? Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #241: Performance - Figur im (Kür)Programm der Schwierigkeitsstufe 10. (Manfred Worm Schäfer) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Recipients missing on list post
* Stefan Förster <[EMAIL PROTECTED]> wrote:
> * Mark Sapiro <[EMAIL PROTECTED]> wrote:
>> I'm not sure if this is better, but if your Python is 2.4 or later, see
>> <http://wiki.list.org/x/-IA9> for a patch that can be applied to
>> Mailman/Handlers/SMTPDirect.py to produce copious debugging output
>> from Python's smtplib to Mailman's error log
>
> I put thos in place, thank you. Furthermore, I've written a small
> script to parse Mailman and Postfix logs once a day - the next time a
> recipient is omitted I will be notified. Now I have to wait...
This one did the trick. Thanks again, this was _very_ helpful.
>> You could also patch Mailman/Handlers/SMTPDirect.py to add
>>
>> syslog.write('smtp', 'recips this chunk = %d', len(recips))
>
> Listing the number of recipients that the SMTP handler gets is a good
> idea, I've added that one, too.
>
> I will report my findings the next time I run into this issue.
I have identified the source of my issues: It turned out that the
Mailman installation I inherited was more heavily modified than I
thought - and one of those modifications was the source of the issue I
described. I decided to permanently take care of this and did a clean
reinstall, followed by artitifical stress testing and as expected, the
problem vanished.
I apologize for the noise my inquiry caused.
Cheers
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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=show&file=faq01.027.htp
Re: [Mailman-Users] Recipients missing on list post
* Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Stefan Förster wrote:
>>
>> Now, 22+26+19+158 equals 225 and not 226 - no rejected mails, no
>> NOQUEUE entries. Either Postfix or Mailman is lying. How can I find
>> out which one it is, aside from running ngrep/tcpdump?
>
>
> I'm not sure if this is better, but if your Python is 2.4 or later, see
> <http://wiki.list.org/x/-IA9> for a patch that can be applied to
> Mailman/Handlers/SMTPDirect.py to produce copious debugging output
> from Python's smtplib to Mailman's error log
I put thos in place, thank you. Furthermore, I've written a small
script to parse Mailman and Postfix logs once a day - the next time a
recipient is omitted I will be notified. Now I have to wait...
>> Which additional configuration data do I have to provide to aid in
>> remote debugging this?
>
>
> Just for curiosity, try the following:
>
> bin/list_members listname >file1
> sort -f file1 >file2
> sort -f -u file1 >file3
> diff file2 file3
No output.
> You could also patch Mailman/Handlers/SMTPDirect.py to add
>
> syslog.write('smtp', 'recips this chunk = %d', len(recips))
Listing the number of recipients that the SMTP handler gets is a good
idea, I've added that one, too.
I will report my findings the next time I run into this issue.
Ciao
Stefan
--
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
--
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=show&file=faq01.027.htp
[Mailman-Users] Recipients missing on list post
Hello world, if the host running my Mailman installation is experiencing a high load (i.e., high CPU usage, many CPU cycles waiting for I/O), posts to some lists are sometimes sent out with about 1 in 300 subscribers missing. First of all, I verified that the recipients who didn't receive posts didn't have mail delivery suspended - they didn't. Then I looked into Mailman logs, which yield the following entries: #v+ /var/log/mailman/post: Jun 19 11:13:07 2008 (3760) post to listname from [EMAIL PROTECTED] size=42101, message-id=<[EMAIL PROTECTED]>, success #v- #v+ /var/log/mailman/smtp: Jun 19 11:13:09 2008 (3760) <[EMAIL PROTECTED]> smtp to listname for 226 recips, completed in 1.179 seconds #v- Notice the 226 recipients and the long time it takes to submit the messages (1.179 seconds) - as I said, the system is somewhat "congested" at that time. Let's have a look at the corresponding Postfix log entries: #v+ Jun 19 11:13:07 mout03 postfix/smtpd[7065]: connect from localhost[127.0.0.1] Jun 19 11:13:07 mout03 postfix/smtpd[7065]: B251578003: client=localhost[127.0.0.1] Jun 19 11:13:07 mout03 postfix/cleanup[7062]: B251578003: message-id=<[EMAIL PROTECTED]> Jun 19 11:13:07 mout03 postfix/qmgr[3962]: B251578003: from=<[EMAIL PROTECTED]>, size=42602, nrcpt=22 (queue active) Jun 19 11:13:07 mout03 postfix/smtpd[7065]: B630678004: client=localhost[127.0.0.1] Jun 19 11:13:07 mout03 postfix/cleanup[7062]: B630678004: message-id=<[EMAIL PROTECTED]> Jun 19 11:13:07 mout03 postfix/qmgr[3962]: B630678004: from=<[EMAIL PROTECTED]>, size=42627, nrcpt=26 (queue active) Jun 19 11:13:07 mout03 postfix/smtpd[7065]: C041B78005: client=localhost[127.0.0.1] Jun 19 11:13:07 mout03 postfix/cleanup[7062]: C041B78005: message-id=<[EMAIL PROTECTED]> Jun 19 11:13:08 mout03 postfix/qmgr[3962]: C041B78005: from=<[EMAIL PROTECTED]>, size=42419, nrcpt=19 (queue active) Jun 19 11:13:08 mout03 postfix/smtpd[7065]: 2DD0D78003: client=localhost[127.0.0.1] Jun 19 11:13:08 mout03 postfix/cleanup[7062]: 2DD0D78003: message-id=<[EMAIL PROTECTED]> Jun 19 11:13:08 mout03 postfix/qmgr[3962]: 2DD0D78003: from=<[EMAIL PROTECTED]>, size=42153, nrcpt=158 (queue active) Jun 19 11:13:09 mout03 postfix/smtpd[7065]: disconnect from localhost[127.0.0.1] #v- Now, 22+26+19+158 equals 225 and not 226 - no rejected mails, no NOQUEUE entries. Either Postfix or Mailman is lying. How can I find out which one it is, aside from running ngrep/tcpdump? Which additional configuration data do I have to provide to aid in remote debugging this? Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #68: WWW - World Wide Waiting -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Authorization required with FireFox 3
* Sascha Schmidt <[EMAIL PROTECTED]> wrote: > yesterday, 2 days after the release of FireFox 3 I'm trying to login to > my mailman 2.1.10 installation. After entering the correct password the > errormessage "Authorization failed" is shown. Deleting the Browser > Cache/Cookies didn't fix the problem. > > There's no problem logging in with Firefox 2 and IE. > Someone can reproduce this behaviour? Login with Firefox 3 (on OSX) works perfectly well. I suggest capturing the actual HTTP requests and responses exchanged during login to ease debugging this. Probably it's just some cookie acception problem. Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #297: extensiv getestet - Bislang verschwiegener Bestandteil der letzten Lieferung (Lutz Donnerhacke) -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Queue problems
* Allan Odgaard <[EMAIL PROTECTED]> wrote: > On 17 Jun 2008, at 18:53, Mark Sapiro wrote: > >> Brad Knowles wrote: >> >>> On 6/17/08, Allan Odgaard wrote: >>> >>>> I transferred a lot of list members from a previous list. A dozen >>>> of these >>>> has left errors like the following in `logs/smtp-failures`: >>>> >>>> delivery to <> failed with code 450: >>>> 4.1.2 <>: Recipient address rejected: >>>> Domain not found >>> >>> You're doing DNS validation on your outbound >>> mail. Don't do that. Pay attention to the stuff >>> in section 6 of the FAQ, especially including >>> 6.6, 6.8, 6.12, etc >> >> Also, fix your MTA configuration so it returns a 5xx status, not a 450 >> for a non-existant domain. > > To the best of my knowledge, this can not be “fixed” (for Postfix). If > Postfix is unable to obtain DNS settings for a domain, it will treat > it as a temporary error, and will return 450, regardless of settings > (and to me this seems correct, as not being able to obtain DNS > settings is likely because something is down). postconf -e unknown_address_reject_code=550 Read the description of this setting - it will STILL return a 45x if the error is _temporary_, whereas "temporary" is defined by your local resolver library (this works very well in most cases). > If on the other hand it _does_ find a name server for the domain and > there is no MX record, _then_ can it be treated as a permanent error. ITYM "no MX- and no A-RR". > If others should run into this problem > `reject_unknown_recipient_domain` was the setting I had to disable in > Postfix’s `smtpd_recipient_restrictions`. You can easily create a dedicated smtpd instance for injection of mails generated by mailman. Have a look at http://wiki.list.org/pages/viewpage.action?pageId=4030642 - I use SMTPPORT = 10026 in /etc/mailman/mm_cfg.py and in /etc/postfix/master.cf: 127.0.0.1:10026 inet n - - - - smtpd -o content_filter= -o mynetworks=127.0.0.0/8 -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_milters -o smtpd_client_connection_count_limit=0 -o smtpd_client_connection_rate_limit=0 -o smtpd_error_sleep_time=0 -o smtpd_soft_error_limit=1001 -o smtpd_hard_error_limit=1000 -o smtpd_restriction_classes= -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_data_restrictions=reject_unauth_pipelining -o smtpd_end_of_data_restrictions= -o smtpd_delay_reject=no -o local_header_rewrite_clients= Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Queue problems
* Brad Knowles <[EMAIL PROTECTED]> wrote: > On 6/17/08, Allan Odgaard wrote: > >> I transferred a lot of list members from a previous list. A dozen of these >> has left errors like the following in `logs/smtp-failures`: >> >>delivery to «address» failed with code 450: >>4.1.2 «address»: Recipient address rejected: >>Domain not found > > You're doing DNS validation on your outbound > mail. Don't do that. Pay attention to the stuff > in section 6 of the FAQ, especially including > 6.6, 6.8, 6.12, etc Not 100% related: What happens if my MTA does DNS validation and rejects addresses who yield an NXDOMAIN (as opposed to a SERVFAIL) with a permanent error code instead of creating a bounce? Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] distributing of the mail is not ok
Am 09.06.2008 um 16:05 schrieb [EMAIL PROTECTED]: Stefan Förster wrote: Am 09.06.2008 um 10:16 schrieb [EMAIL PROTECTED]: I installed mailman. I created a mailing list to test if mailman works fine or not. Well, mailman seems alsmot to work but there is just a problem. Let's assume, I have a mailing list : "test". And the mail used for this mailing list is "[EMAIL PROTECTED]", the members have to send their mails at [EMAIL PROTECTED], sure, this email exists, but if a member sends a mail to this address, the mail sticks with the folder of the email (/var/spool/vmail/lists.mydomain.tld/test/new/), and so the email is not distributed to the list. I didn't find a solution, I think this is a problem with the configuration... Any ideas? Obviously, you did not configure your MTA (Sendmail, Exim, Postfix) to forward those mails to Mailman. Instead, the mail is delivered to the correspondent maildir in /var/spool. Mailman integration for various MTAs is described here: http://www.list.org/mailman-install/mail-server.html Oops, yeah, I've forgotten to configure my MTA. So, it's done, alsmot: Jun 9 15:50:46 kaduma-hosting postfix/smtpd[28245]: warning: database /etc/aliases.db is older than source file /etc/aliase => "postmap aliases" : "[...] Jun 9 16:01:32 kaduma-hosting postfix/postmap[29980]: warning: aliases, line 27: record is in "key: value" format; is this an alias file? Jun 9 16:01:32 kaduma-hosting postfix/postmap[29980]: warning: aliases, line 30: record is in "key: value" format; is this an alias file? Jun 9 16:01:32 kaduma-hosting postfix/postmap[29980]: warning: aliases, line 31: record is in "key: value" format; is this an alias file? Jun 9 16:01:32 kaduma-hosting postfix/postmap[29980]: warning: aliases, line 32: record is in "key: value" format; is this an alias file? Jun 9 16:01:32 kaduma-hosting postfix/postmap[29980]: warning: aliases, line 33: record is in "key: value" format; is this an alias file? [...]"|| The correct command to create a hash file out of a file that is (a) listed in Postfix's "alias_database" setting is to execute the command "newaliases". "postmap" OTOH doesn't know how to deal with files containing "key: value" pairs (note the ":"). Jun 9 15:50:46 kaduma-hosting postfix/smtpd[28245]: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled Jun 9 15:50:46 kaduma-hosting postfix/smtpd[28245]: fatal: open database /var/lib/mailman/data/virtual-mailman.db: No such file or directory => I've tried many solutions... but it's not fixed. For the first warning, try to remove the "nis:mail.aliases" entry in "alias_maps". Execute "postconf alias_maps" to see the current setting ,then explicitely set it in a way that doesn't include "nis:mail.aliases". For the second warning you obviously have to create the "database" file for "/var/lib/mailman/data/virtual-mailman". See below. Im my main.cf (for postfix) : virtual_alias_maps = mysql:/etc/postfix/mysql-virtual_aliases.cf, mysql:/etc/postfix/mysql-virtual_aliases_mailbox.cf, hash:/var/lib/mailman/data/aliases virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual_mailboxes.cf, hash:/var/lib/mailman/data/virtual-mailman It's just plain wrong to reference "/var/lib/mailman/data/virtual- mailman" in virtual_mailbox_maps. Remove it. Execute "postmap /var/lib/mailman/data/virtual-mailman". Inspect "/var/ lib/mailman/data/aliases". If this is an alias file and you need the entries, include it in "alias_maps" and "alias_database". Execute "newaliases" if needed. If you don't need "/var/lib/mailman/data/ aliases", remove any references to it. Restart Postfix. Cheers Stefab -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Mac OS X: Almost perfect. Almost. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] distributing of the mail is not ok
Am 09.06.2008 um 10:16 schrieb [EMAIL PROTECTED]: I installed mailman. I created a mailing list to test if mailman works fine or not. Well, mailman seems alsmot to work but there is just a problem. Let's assume, I have a mailing list : "test". And the mail used for this mailing list is "[EMAIL PROTECTED]", the members have to send their mails at [EMAIL PROTECTED], sure, this email exists, but if a member sends a mail to this address, the mail sticks with the folder of the email (/var/spool/vmail/lists.mydomain.tld/test/new/), and so the email is not distributed to the list. I didn't find a solution, I think this is a problem with the configuration... Any ideas? Obviously, you did not configure your MTA (Sendmail, Exim, Postfix) to forward those mails to Mailman. Instead, the mail is delivered to the correspondent maildir in /var/spool. Mailman integration for various MTAs is described here: http://www.list.org/mailman-install/mail-server.html Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Mac OS X: Eating ~/.signature files since 2003. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Mail getting stuck in queue
Am 06.06.2008 um 23:46 schrieb Laura Conrad: Mark> If your Python is at least 2.4.x, you can follow the instructions for Mark> modifying Mailman/Handlers/SMTPDirect.py to produce more debugging Mark> output in Mailman's error log which may help you find more. Do not do Mark> this with Python 2.3.x for the reason mentioned in the FAQ. OK. It isn't completely stuck, but it's taking a lot longer to send out a few messages than I'd expect. Right now, the last post in the post log was at 16:30, and at 17:39, "tail error" says: Jun 06 17:37:59 2008 qrunner(14342): send: 'rcpt TO:<[EMAIL PROTECTED] >\r\n' Jun 06 17:38:29 2008 qrunner(14342): reply: '250 ok\r\n' Jun 06 17:38:29 2008 qrunner(14342): reply: retcode (250); Msg: ok Jun 06 17:38:29 2008 qrunner(14342): send: 'rcpt TO:<[EMAIL PROTECTED] >\r\n' Jun 06 17:38:59 2008 qrunner(14342): reply: '250 ok\r\n' Jun 06 17:38:59 2008 qrunner(14342): reply: retcode (250); Msg: ok Jun 06 17:38:59 2008 qrunner(14342): send: 'rcpt TO:<[EMAIL PROTECTED] >\r\n' Jun 06 17:39:29 2008 qrunner(14342): reply: '250 ok\r\n' Jun 06 17:39:29 2008 qrunner(14342): reply: retcode (250); Msg: ok Jun 06 17:39:29 2008 qrunner(14342): send: 'rcpt TO:<[EMAIL PROTECTED] >\r\n' Does this tell you anything? Basically either your Postfix needs from 17:38:29 to 17:38:59 to accept a single recipient or Mailman needs 30 seconds to read the response. It if is Postfix, you will either notice something in your maillog right away or at least you will be able to produce valuable debugging output running postconf -e debug_peer_list=127.0.0.1 && postfix reload (replace 127.0.0.1 with the IP of your Mailman server if they don't run on the same box) Aside from misconfiguration or server load, one thing that immediately comes to my mind are excessive errors - after more than smtpd_soft_error_limit, this kind of slowdown is exactly what happens. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Mac OS X ate my ~/.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=show&file=faq01.027.htp
Re: [Mailman-Users] server load..
This a follow-up to a quite old posting on this list. I just read something on postfix-users and feel that it is relevant for this question. The OP wanted to deal with a larger mail volume: * Khalil Abbas <[EMAIL PROTECTED]> wrote: > hi mailman guys .. my question is, I have a 100,000+ subscribers > mailing list, and hosting it with godaddy.com (Celeron 2000, 2 GBs > RAM) .. but they only allow 100,000 emails per day for each > dedicated server, so I have to buy a new server now, and it's a bit > expensive.. On postfix-users, Wietse Venema and Victor Duchovni said about Postfix scalability: Victor Duchovni wrote: > On Wed, Jun 04, 2008 at 02:29:35PM -0400, Wietse Venema wrote: >> Without content filtering, a 5-year old single-CPU machine could >> do this easily. However, 1 million messages in a day of 50 kbyte >> each means you need 10+Mbit/s of network bandwidth. > > Postfix on modern hardware, and a cooperative I/O subsystem, can handle > a million messages an hour. [...] I hope that this will offer some insight into what modern MTAs are capable off. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Still amiss: ~/.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=show&file=faq01.027.htp
Re: [Mailman-Users] Mailman Address Format
* Carlos Williams <[EMAIL PROTECTED]> wrote: > Why does mailman do this? I don't understand the "bounce" parameter > and or why it does not show its from "[EMAIL PROTECTED]". The "listname-bounce" localpart is used for automatic bounce detection. Have a look at: <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.028.htp> Bounce detection is an integral part of every mailing list managing software: It allows users whose email addresses are not valid any longer to be removed from the list without the need for a human being to manually look at logfiles to determine this. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Free speech tastes better than free beer. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] virtual domains
* Mark Sapiro <[EMAIL PROTECTED]> wrote: > Melinda Gilmore wrote: > >> I know this has been covered alot and I do see alot of talk in the >> archives, but I am new to the whole, mailman/postfix/apache/redhat >> world and the instructions are not clear to me because of that. Is >> there anyone out there that has the actually settings and what files >> to change in postfix, apache, mta, and whatever to get virtual >> domains to work. Am I to understand that if I had a list called >> [EMAIL PROTECTED] (our domain) and I want a virtual >> domain to go with it called [EMAIL PROTECTED] I can get this to work? > > > Not exactly. If you have a list named "something" that is currently in > the lists.service.osu.edu domain, you could move it to the network.org > domain, but the whole idea of virtual domains in Mailman is that the > various domains are disjoint (although currently list names still have > to be globally unique). > > If you just want to be able to mail to [EMAIL PROTECTED] in > addition to mailing to [EMAIL PROTECTED] and have either > address go to the list, this would all be done in Postfix and DNS. I think one would have to add [EMAIL PROTECTED] to acceptable_aliases, too. As a remark, I really think that integration of Mailman into Postfix using relay_domains and postfix-to-mailman.py should be included in the official installation documentation. Postfix's concept of virtual_alias_domains is very poweful and therefore offers lot's of ways you can totally break your mail system if you are inexperienced - you can break recipient validation or introduce mail loops, for example. Any aliasing needed can still be done with virtual_alias_maps if one absolutely _has_ to have aliases. With relay_recipient_maps you get better control about acceptable recipients (although you have to set this up yourself, I didn't see any way in Mailman to handle this in an automatic way). And as a last advantage, on a busy server, I personally would refrain from using Berkeley BD hash tables, because updates to those are not done "atomically" which might seriously break mail to lists if mail arrives while the maps are updated. Using CBD tables help's a lot here, safe for the much smaller memory footprint. Cheers Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Science is what happens when preconception meets verification. -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] excessive bounce notifications..
Damnit, that is * Stefan Förster <[EMAIL PROTECTED]> wrote: > easily handle around 7k rejected mails per second on 100 concurrent, per MINUTE, ofc! Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 ...And god said, let there be a Satan, so people won't blame everything on me... -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] excessive bounce notifications..
* Khalil Abbas <[EMAIL PROTECTED]> wrote: > I recieve over 2000 messages from mailman-bounces every day with > subject: Uncaught bounce notification.. and when opening any message > it's nothing but another Spam Ad about pills or shoes or other > stuff.. how can I stop these ADs from being sent to my Admin email? > it's becoming a real pain as it takes forever to download to the > inbox.. on the other hand, I don't want to disable the notification > because sometimes it might be a bounce that mailman couldn't detect > so I remove it manually from the list .. If you do not wan't to disable those notifications in Mailman, the easiest way seems to filter the messages bevor they are delivered to mailman. This probably involves some configuration in your MTA - but have you tried out the "Spam Filtering" options in your admin webinterface? As for your mailserver: A very effective open source spam filtering tool is amavisd-new which is written in Perl and can classify incoming messages as ham or spam using a pre-defined set of rules (to catch typcial pill ads, Nigerian 419 frauds and so on), a Bayes style filter (which you can train to "learn" which messages are spam), numerous DNS blacklists to e.g. compare advertised URLs against blacklists and distributed spam tracking systems like Razor or Pyzor. You can download it at: http://www.ijs.si/software/amavisd/ Please note that, depending on the volume of messages it has to filter, amavisd-new might need a non-trivial amount of memory and CPU time. On a dualcore Opteron with 2 GB RAM, I can filter between four and eight messages per second. Another option is to configure your mail server to do more checks on incoming messages. Since I don't know what MTA you are using, I can only give you some general guidelines on that: A first step would be to enforce compliance to the (E)SMTP protocol in you MTA, i.e. reject the message when the (E)SMTP syntax is invalid or the presented name in the HELO/EHLO greeting is either invalid or not fully qualified (you have to THOROUGHLY TEST the latter!). This solution deson't consume any noticeable ressources. On the aforementioned server, I can easily handle around 7k rejected mails per second on 100 concurrent, incoming connections made by spambots. A second step would be to enforce a technique called greylisting on hosts which don't have a reverse DNS name or whose hostname looks like a dialup name, e.g. "22-22-22-22.dialup.provider.example.org". You can find information on greylisting at http://www.greylisting.org/ In terms of resources, greylisting is very cheap. On the aforementioned server, I can easily handle about 1k rejects per minute due to hosts not passing greylisting. As a last step, you can make use of various realtime DNS black lists, for exampe zen.spamhaus.org. I cannot give you any specific recommendations on which blacklists to use, and I can't give you any guidelines on your policy, i.e. whether you want to reject a message if the sending host is in one, two, three or more blacklists. There are Postfix style policy daemon, Sendmail style milters and generic SMTP proxies around which all allow you to configure quite sophisticated policies on when to reject a message according to DNSBL hits. For some general information on the use of blacklists, please refer to your MTA's documentation. On the aforementioned server, supported by a highly tuned local DNS cache, I can handle about 200 policy decisions per second at most. Cheers Stefan -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] server load..
* Khalil Abbas <[EMAIL PROTECTED]> wrote: > hi guys, I posted this message a couple of days ago but didn't get > any satisfying answers.. neither did I find a good answer in the Faq > cause it's too "technical" .. so here's my message again: Actually, Brad Knowles' answer was quite good. > hi mailman guys .. my question is, I have a 100,000+ subscribers > mailing list, and hosting it with godaddy.com (Celeron 2000, 2 GBs > RAM) .. but they only allow 100,000 emails per day for each > dedicated server, so I have to buy a new server now, and it's a bit > expensive.. I found another cheap service, $30/month dedicated > servers and they offer unlimited emails per day.. but its > characteristics are a bit low: AMD, 512 MB RAM .. my question is, > will mailman with such a huge list which is also rapidly growing > work on such server? knowing that I only send 1 email newsletter a > day to the list and none of the users can send to the list but me.. A day has 24 hours. Each hour has 60 minutes. Each minute has 60 seconds. That makes for a total of 86400 seconds per day.That means that you had to send out about 2 mails per second. Given a setting of SMTP_MAX_RCPTS of 500, that means that mailman would deliver about 200 mails to your MTA - non personalized, non VERP'ed. This is not a problem at all from an MTA's point of view (perhaps somebody with more knowledge of Mailman can, again, say something about Mailman's memory requirements with that many recipients). Even with default configurations and a rather poor DNS cache, I can't see a problem with that. Now, you still have to do bounce processing - which again, with 10 recipients, shouldn't be that much of a problem. So given that you have a non-personalized list, don't do VERP, I'd say: Go for it. If you need personalization or need to do VERP in Mailman: I'd say forget it. Now if you want a more educated answer, review what Brad said. > another question, is it easy to install mailman manually? cause in > godaddy's control panel it's ready to install with 1 click.. but > with the new cheap service I have to install it myself.. and is > there a ready-to-install script that does everything automatically > like that in the control panels? Thanks for everything mates .. Mailmans installation manual http://www.list.org/mailman-install/index.html is one of the most detailed and easy to understand writings I have ever seen. Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 Aut agere aut mori. (Either action or death.) -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] Don`t get my mailinglist to run (mailman & postfix)
* Kai Behncke <[EMAIL PROTECTED]> wrote: > Postfix runs finely. I made some tests with the php-command "mail" and could > sent mails to my self. > > I installed mailman from source with > "./configure --prefix=/usr/local/mailman --with-groupname=mailman > --with-username=mailman --with-mail-gid=postfix --with-cgi-gid=apacheuser > --with-mailhost=igf-srv-gin.igf.Uni-Osnabrueck.de > --with-urlhost=igf-srv-gin.igf.Uni-Osnabrueck.de" > > bin/check_perms gave no errors at all. > > I created a side wide mailinglist,started the mailman qrunner,site password > and can create a new mailinglist at: > > http://igf-srv-gin.igf.uni-osnabrueck.de/mailman/create > > ...and the list is created, also the entries in /usr/local/mailman/aliases: > > "# STANZA START: big_test > # CREATED: Fri May 16 19:30:00 2008 > big_test: "|/usr/local/mailman/mail/mailman post big_test" > big_test-admin: "|/usr/local/mailman/mail/mailman admin big_test" > big_test-bounces: "|/usr/local/mailman/mail/mailman bounces big_test" > big_test-confirm: "|/usr/local/mailman/mail/mailman confirm big_test" > big_test-join:"|/usr/local/mailman/mail/mailman join big_test" > big_test-leave: "|/usr/local/mailman/mail/mailman leave big_test" > big_test-owner: "|/usr/local/mailman/mail/mailman owner big_test" > big_test-request: "|/usr/local/mailman/mail/mailman request big_test" > big_test-subscribe: "|/usr/local/mailman/mail/mailman subscribe big_test" > big_test-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe big_test" > I can register as a new user to the list and get a confirmation > mail.I confirm subscribing and try to send mails to that list but > they are not send to the registered users Can anyone help > please?? We would need some more logging information. For example, is there anything in the Postfix mail log (usually /var/log/maillog or something similar)? Is there anything in mailman's error or smtp log? > And I have another question: > > To send mails to [EMAIL PROTECTED] > > is a really complicated name. is there a possibility to send it to (for > example): > > [EMAIL PROTECTED] > > But how and where can I define "my_adress.de". Yo can add alias addresses which mailman feels responsible for in the admin web interface: http://your listserver>/mailman/admin//privacy/recipient The option name is "acceptable_aliases". Then you just need to have control over a mailserver to define an alias from [EMAIL PROTECTED] to [EMAIL PROTECTED] (and of course, the MX record for my_adress.de must point to that particular server). Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 FdI #306: Shockwave Flash - Augenkrebs (Felix von Leitner) -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] List of owners and subscribers
Throw in a
* Stefan Förster <[EMAIL PROTECTED]> wrote:
> list_lists | awk '(NR > 1){print $1}' | while read line; do
> echo "List: $line"
list_admins "$line"
> list_members -f "$line"
> done
exactly there ;)
And ofc, this now assumes that list_admins is in your $PATH, too.
Cheers
Stefan
--
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=show&file=faq01.027.htp
Re: [Mailman-Users] List of owners and subscribers
* Melinda Gilmore <[EMAIL PROTECTED]> wrote:
> Has anyone out there put together and scripts that might extract out owners
> and subscribers to a list. Where you could see all the list and all their
> subscribers in one place.
My English is not that good and I'm not really sure if I understand
what you actually want to achieve, but what about something like:
list_lists | awk '(NR > 1){print $1}' | while read line; do
echo "List: $line"
list_members -f "$line"
done
This assumes you (1) have shell access to the box hosting Mailman and
(2) that list_lists and list_members are in your $PATH.
Cheers
Stefan
--
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=show&file=faq01.027.htp
Re: [Mailman-Users] gmail to hotmail problem
* Johnny Kosela <[EMAIL PROTECTED]> wrote: > When i send a message from the gmail account to the list. Not every > time but a lot of the times the message does not show up at the > hotmail account. Sending mail from and to the other accounts seems > to work fine. [...] > Anyone have seen this problem before? Or know if there is anything > to do about it? hotmail.com is notoriously known for silently discarding mails. Try a search on the mailing lists for your favourite MTA (Postfix, Exim, whatever). Have a look at: http://postmaster.msn.com/Services.aspx#SenderSolutions Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 -- 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=show&file=faq01.027.htp
Re: [Mailman-Users] How many bounces
* [EMAIL PROTECTED] wrote: > I understand how to set bounce thresholds, but is there a place to > see where indidivual users are at regarding bounces? Let's say I > have the threshold set to 5 bounces. Obvioulsy mailman is keeping > track of each users number of bounces that are "current". How can I > see where each user is at? It seems it would make a nice column > addition to the Membership Management table. As for now, you can either parse bounce logs or just klick on an individual user in the Membership Management table. And yes, a feature to display users sorted by bounce, e.g., would come in handy. Ciao Stefan -- Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9 -- 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=show&file=faq01.027.htp
