Re: [Mailman-Users] Virtual hosts
At 4:57 PM +0900 4/13/07, Stephen J. Turnbull wrote: Right, my point is that readers of the Mailman FAQ are are there because they're thinking Mailman 'should' be able to do something about this, but as I understand it (I haven't actually had to deal with, so I haven't seen it in the wild) you've saying the rewriting could be happening *anywhere*, so there's not much that Mailman can do. Correct. There's nothing that Mailman can do to help with this situation. So site admins need to make sure via the DNS, not Mailman, that what goes out is what is going to come back. Right? Also correct. But we need something in our FAQ to identify what the real problem is and what the appropriate admins will have to do, because Mailman administrators will certainly be affected by this kind of thing, even if there's nothing they can do to prevent it. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list [EMAIL PROTECTED] 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] HTML causing list-wide bounce?
At 5:49 PM -0400 4/13/07, Paul Tomblin wrote: The email message causing the issue -- .html format http://www.soarol.com/tmp/EmailList-HTMLerror-2.html First comment - why the hell is he sending javascript in an email message? That plus the Paypal thing probably screams scammer to most mail filters. Because it's happening to everybody, I'm betting it's an outgoing mail filter. If so, then Michael would be well advised to look at the mail filtering process that is being used on the mail system and the Mailman server. For obvious performance reasons, you want to do all mail filtering on the inbound leg only, and avoid any further filtering on the outbound leg. If that had been done in this case, the message would have been rejected before it ever got to Mailman, and once the message was cleaned up, it wouldn't have resulted in all the rejections from the outbound filter -- because there wouldn't have been any outbound filter. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- Mailman-Users mailing list [EMAIL PROTECTED] 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] HTML causing list-wide bounce?
Brad Knowles wrote: At 5:49 PM -0400 4/13/07, Paul Tomblin wrote: The email message causing the issue -- .html format http://www.soarol.com/tmp/EmailList-HTMLerror-2.html First comment - why the hell is he sending javascript in an email message? That plus the Paypal thing probably screams scammer to most mail filters. Because it's happening to everybody, I'm betting it's an outgoing mail filter. If so, then Michael would be well advised to look at the mail filtering process that is being used on the mail system and the Mailman server. For obvious performance reasons, you want to do all mail filtering on the inbound leg only, and avoid any further filtering on the outbound leg. I found that the postfix /etc/postfix/access file allows you to specify domains that can't send you email (for instance, I reject anything from *.com.cn), but it also prevents you from sending email to those domains. So it's possible that a locally created email would not trigger any incoming mail filter but would trigger those same filters on the outbound. -- Paul Tomblin [EMAIL PROTECTED] Stay calm, be brave, and wait for the signs! -- Mailman-Users mailing list [EMAIL PROTECTED] 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] Problem with virtual domain
Giancarlo Rubio wrote: I'm try to configure mailman with postfix and have a mistake when send mail to server. The web interface is run correctly. My list (virtual domain) [EMAIL PROTECTED] My real domain pontonetsistemas.com.br When i send a mail to list i get this message (int the mta) Apr 13 08:29:27 fileserver postfix/qmgr[53878]: E38C71CCD1: from=[EMAIL PROTECTED], size=1722, nrcpt=1 (queue active) Apr 13 08:29:27 fileserver postfix/virtual[68735]: E38C71CCD1: to=[EMAIL PROTECTED], orig_to=[EMAIL PROTECTED], relay=virtual, delay=0.49, delays=0.47/0.01/0/0.01, dsn=5.1.1, status=bounced (unknown user: [EMAIL PROTECTED]) - Mostrar texto das mensagens anteriores - I find similar errors on this list, but no way to solve this My configurations files snip mailman/mm_cf.py MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['openbsd-br.org','openbsd-br.org'] It is unnecessary to have a domain listed more than once in POSTFIX_STYLE_VIRTUAL_DOMAINS (but it does no harm). Warning, I know almost nothing about Postfx. All the mailman stuff, and as far as I can tell the Postfix stuff too, looks fine to me. This is really a Postfix question, not a Mailman question. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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] Help: Digests not working after upgrade
Yasean Khan wrote: Senddigests when executed does nothing.. nothing gets written to the log either. Is there a lists/listname/digest.mbox file? Is the list's digest_send_periodic attribute set to Yes? yes to both Then assuming cron/sendigests is pointing at the right Mailman, a digest should be sent or there should be some error reported in Mailman's error log. Is prefix set correctly in cron/paths.py? it should contain in your case there should be prefix = '/usr/lib/mailman/' in cron/paths.py. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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