Subject: postfix-to-mailman.py does not handle mailman-loop@___domain
Date: Sun, 27 Dec 2009 06:42:46 +0100
Package: mailman
Version: 1:2.1.11-11
Severity: normal
One of my list admins uses a T-Online account, which rejects spam,
creating a mail loop.
Mailman detects this and tries to send the message to mailman-loop@___domain,
which fails because I use postfix-to-mailman.py for the ___domain and it
doesn't seem to know about mailman-loop.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31.7-nokmem-tomodachi
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mailman depends on:
ii adduser 3.110 add and remove users and groups
ii apache2 2.2.9-10+lenny6 Apache HTTP Server metapackage
ii apache2-mpm-prefork [htt 2.2.9-10+lenny6 Apache HTTP Server - traditional n
ii cron 3.0pl1-105 management of regular background p
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-18 GNU C Library: Shared libraries
ii lighttpd [httpd] 1.4.19-5 A fast webserver with minimal memo
ii logrotate 3.7.1-5 Log rotation utility
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii postfix [mail-transport- 2.5.5-1.1 High-performance mail transport ag
ii pwgen 2.06-1 Automatic Password generation
ii python 2.5.2-3 An interactive high-level object-o
ii python-support 0.8.4lenny1 automated rebuilding support for P
ii ucf 3.0016 Update Configuration File: preserv
mailman recommends no packages.
Versions of packages mailman suggests:
pn listadmin <none> (no description available)
ii lynx 2.8.7dev9-2.1 Text-mode WWW Browser (transitiona
ii spamassassin 3.2.5-2+lenny1 Perl-based spam filter using text
-- debconf information:
* mailman/site_languages: de, en
* mailman/used_languages: de en
* mailman/create_site_list:
* mailman/queue_files_present: continue regardless
* mailman/default_server_language: en
mailman/gate_news: true
Acknowledgement sent
to "Thijs Kinkhorst" <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Tue, 29 Dec 2009 20:00:02 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does
not handle mailman-loop@___domain
Date: Tue, 29 Dec 2009 20:39:45 +0100
On Sun, December 27, 2009 06:42, Tobias Diedrich wrote:
> One of my list admins uses a T-Online account, which rejects spam,
> creating a mail loop.
> Mailman detects this and tries to send the message to mailman-loop@___domain,
> which fails because I use postfix-to-mailman.py for the ___domain and it
> doesn't seem to know about mailman-loop.
Thanks for your report. I am adding '-loop' to the list in
postfix-to-mailman.py under the "# Check for control extension on local
part" comment. Can you confirm that this resolves your problem?
thanks,
Thijs
Acknowledgement sent
to Tobias Diedrich <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 30 Dec 2009 16:42:03 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does
not handle mailman-loop@___domain
Date: Wed, 30 Dec 2009 17:32:23 +0100
Thijs Kinkhorst wrote:
> On Sun, December 27, 2009 06:42, Tobias Diedrich wrote:
> > One of my list admins uses a T-Online account, which rejects spam,
> > creating a mail loop.
> > Mailman detects this and tries to send the message to mailman-loop@___domain,
> > which fails because I use postfix-to-mailman.py for the ___domain and it
> > doesn't seem to know about mailman-loop.
>
> Thanks for your report. I am adding '-loop' to the list in
> postfix-to-mailman.py under the "# Check for control extension on local
> part" comment. Can you confirm that this resolves your problem?
I think it should rather be added to the "# Redirect required
addresses to" since AFAICS it's a global user with no corresponding
mailing list.
--
Tobias PGP: http://8ef7ddba.uguu.de
Acknowledgement sent
to Thijs Kinkhorst <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 30 Dec 2009 16:57:02 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does not handle mailman-loop@___domain
Date: Wed, 30 Dec 2009 17:55:58 +0100
On woansdei 30 Desimber 2009, Tobias Diedrich wrote:
> > Thanks for your report. I am adding '-loop' to the list in
> > postfix-to-mailman.py under the "# Check for control extension on local
> > part" comment. Can you confirm that this resolves your problem?
>
> I think it should rather be added to the "# Redirect required
> addresses to" since AFAICS it's a global user with no corresponding
> mailing list.
Actually, I think it is, and that the corresponding mailinglist is the 'site
list', usually named 'mailman'. This is what I construct from reading the
code. -loop seems similar in this way to -owner which is also in that same
spot.
Can you try if adding the suffix to the list I mentioned solves your problem?
thanks,
Thijs
Acknowledgement sent
to Tobias Diedrich <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 30 Dec 2009 18:00:03 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does
not handle mailman-loop@___domain
Date: Wed, 30 Dec 2009 18:57:53 +0100
Thijs Kinkhorst wrote:
> On woansdei 30 Desimber 2009, Tobias Diedrich wrote:
> > > Thanks for your report. I am adding '-loop' to the list in
> > > postfix-to-mailman.py under the "# Check for control extension on local
> > > part" comment. Can you confirm that this resolves your problem?
> >
> > I think it should rather be added to the "# Redirect required
> > addresses to" since AFAICS it's a global user with no corresponding
> > mailing list.
>
> Actually, I think it is, and that the corresponding mailinglist is the 'site
> list', usually named 'mailman'. This is what I construct from reading the
> code. -loop seems similar in this way to -owner which is also in that same
> spot.
>
> Can you try if adding the suffix to the list I mentioned solves your problem?
Sure, this yields the following error message in the end:
<[email protected]>: Command died with status 6:
"/var/lib/mailman/bin/postfix-to-mailman.py". Command output: Illegal
command: loop
Or if I run /var/lib/mailman/mail/mailman manually:
ari:~# /var/lib/mailman/mail/mailman loop mailman
Illegal command: loop
--
Tobias PGP: http://8ef7ddba.uguu.de
Acknowledgement sent
to Tobias Diedrich <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 30 Dec 2009 18:06:02 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does
not handle mailman-loop@___domain
Date: Wed, 30 Dec 2009 19:03:50 +0100
Tobias Diedrich wrote:
> Sure, this yields the following error message in the end:
>
> <[email protected]>: Command died with status 6:
> "/var/lib/mailman/bin/postfix-to-mailman.py". Command output: Illegal
> command: loop
>
> Or if I run /var/lib/mailman/mail/mailman manually:
> ari:~# /var/lib/mailman/mail/mailman loop mailman
> Illegal command: loop
BTW the reason why I assumed it's a special site-wide address is
because the offending message was sent to <somelist> by a
nonsubscriber so was forwarded to <somelist>-admin, bounced there
and then went to mailman-loop (and not <somelist>-loop).
HTH,
--
Tobias PGP: http://8ef7ddba.uguu.de
Acknowledgement sent
to Tobias Diedrich <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 30 Dec 2009 18:15:03 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does
not handle mailman-loop@___domain
Date: Wed, 30 Dec 2009 19:14:26 +0100
Tobias Diedrich wrote:
> BTW the reason why I assumed it's a special site-wide address is
> because the offending message was sent to <somelist> by a
> nonsubscriber so was forwarded to <somelist>-admin, bounced there
> and then went to mailman-loop (and not <somelist>-loop).
I have to correct myself here a bit after looking at the postmaster
message again:
The 'message needs to be moderated mail' goes to -owner.
mailman expands owner to [email protected] and sends it with
envelope sender mailman-bounces
t-online bounces and postfix delivers to mailman-bounces
mailman expands mailman-bounces to [email protected] this time
with envelope sender mailman-loop
t-online bounces and postfix tries to deliver to mailman-loop
mailman-loop is an unknown user
--
Tobias PGP: http://8ef7ddba.uguu.de
Acknowledgement sent
to Thijs Kinkhorst <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 30 Dec 2009 21:06:06 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does not handle mailman-loop@___domain
Date: Wed, 30 Dec 2009 22:02:57 +0100
On woansdei 30 Desimber 2009, Tobias Diedrich wrote:
> I have to correct myself here a bit after looking at the postmaster
> message again:
>
> The 'message needs to be moderated mail' goes to -owner.
> mailman expands owner to [email protected] and sends it with
> envelope sender mailman-bounces
> t-online bounces and postfix delivers to mailman-bounces
> mailman expands mailman-bounces to [email protected] this time
> with envelope sender mailman-loop
> t-online bounces and postfix tries to deliver to mailman-loop
> mailman-loop is an unknown user
I've dug somewhat deeper and it seems that Mailman itself expects this to
happen with mail to that address (still 'mailman' below is the name of the
site list):
# The ultimate loop stopper address
mailman-loop: /var/lib/mailman/data/owner-bounces.mbox
This is from the aliases file that Mailman generates in its native Postfix
interface.
As I do not use postfix-to-mailman.py myself I'm open to suggestions on how to
handle the -loop ___domain in its context.
cheers,
Thijs
Acknowledgement sent
to Tobias Diedrich <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Thu, 31 Dec 2009 07:48:06 GMT) (full text, mbox, link).
Subject: Re: [Pkg-mailman-hackers] Bug#562700: postfix-to-mailman.py does
not handle mailman-loop@___domain
Date: Thu, 31 Dec 2009 08:40:35 +0100
Thijs Kinkhorst wrote:
> I've dug somewhat deeper and it seems that Mailman itself expects this to
> happen with mail to that address (still 'mailman' below is the name of the
> site list):
>
> # The ultimate loop stopper address
> mailman-loop: /var/lib/mailman/data/owner-bounces.mbox
>
> This is from the aliases file that Mailman generates in its native Postfix
> interface.
>
> As I do not use postfix-to-mailman.py myself I'm open to suggestions on how to
> handle the -loop ___domain in its context.
I think the best way would be to delivere it to
mailman-loop@localhost, with an envelope sender of
postmaster@localhost like this (untested, apparently I manged to get
the host onto some (hopefully temporary) t-online blocklist while
testing this...)
# Redirect mailman-loop special address
if local in ('mailman-loop'):
os.execv("/usr/sbin/sendmail",
("/usr/sbin/sendmail", "-f", "postmaster@localhost", "mailman-loop@localhost"))
sys.exit(0)
HTH,
--
Tobias PGP: http://8ef7ddba.uguu.de
Acknowledgement sent
to Roger Lynn <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Wed, 12 May 2010 15:06:07 GMT) (full text, mbox, link).
Subject: mailman-loop not handled by recommended Exim config
Date: Wed, 12 May 2010 15:28:57 +0100
Package: mailman
Followup-For: Bug #562700
Hi,
I believe this bug also exists in the Exim configuration recommended in
/usr/share/doc/mailman/README.Exim4.Debian
The Exim transport passes the "loop" command to the Mailman wrapper
program, which doesn't know anything about it.
As mentioned previously in this bug, upstream recommend adding
"mailman-loop: /var/lib/mailman/data/owner-bounces.mbox" to
/etc/aliases. However the default Debian Exim configuration doesn't
allow delivery to files in /etc/aliases.
The Debian Exim maintainers recommend adding a router/transport pair for
delivery to a file and in /usr/share/doc/exim4-base/README.Debian.gz
give /usr/share/doc/mailman/README.Exim4.Debian as an example of how it
can be done.
Thanks,
Roger
-- System Information:
Debian Release: 5.0.4
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages mailman depends on:
ii adduser 3.110 add and remove users and groups
ii cron 3.0pl1-105 management of regular background p
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii exim4 4.69-9 metapackage to ease Exim MTA (v4)
ii exim4-daemon-light [mail 4.69-9 lightweight Exim MTA (v4) daemon
ii libc6 2.7-18lenny2 GNU C Library: Shared libraries
ii lighttpd [httpd] 1.4.19-5+lenny1 A fast webserver with minimal memo
ii logrotate 3.7.1-5 Log rotation utility
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii pwgen 2.06-1 Automatic Password generation
ii python 2.5.2-3 An interactive high-level object-o
ii python-support 0.8.4lenny2 automated rebuilding support for P
ii ucf 3.0016 Update Configuration File: preserv
mailman recommends no packages.
Versions of packages mailman suggests:
ii listadmin 2.40-2.2 command line mailman moderator que
pn lynx <none> (no description available)
pn spamassassin <none> (no description available)
-- debconf information:
mailman/queue_files_present: abort installation
* mailman/default_server_language: en (English)
mailman/update_passwords:
* mailman/gate_news: false
mailman/update_aliases:
* mailman/site_languages: en (English)
* mailman/used_languages: en
* mailman/create_site_list:
Acknowledgement sent
to Roger Lynn <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Tue, 18 May 2010 08:33:03 GMT) (full text, mbox, link).
Subject: Re: Bug#562700: mailman-loop not handled by recommended Exim config
Date: Tue, 18 May 2010 09:29:28 +0100
I was intending to follow up to this bug with a suggested router and
transport pair for Exim, as soon as I got around to working them out.
However, I prefer the alternative approach suggested by upstream in
http://mail.python.org/pipermail/mailman-users/2010-May/069504.html
which is simply to alias mailman-loop to root, or whichever local system
user you prefer. So something similar to the following would be added to
/etc/aliases
mailman-loop: root
While I don't understand Mailman's Postfix configuration, I believe this
this is a nice simple solution which would probably solve the problem
for Postfix too.
Roger
Acknowledgement sent
to Thijs Kinkhorst <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Mon, 24 May 2010 14:21:04 GMT) (full text, mbox, link).
On tiisdei 18 Maaie 2010, Roger Lynn wrote:
> I was intending to follow up to this bug with a suggested router and
> transport pair for Exim, as soon as I got around to working them out.
> However, I prefer the alternative approach suggested by upstream in
> http://mail.python.org/pipermail/mailman-users/2010-May/069504.html
> which is simply to alias mailman-loop to root, or whichever local system
> user you prefer. So something similar to the following would be added to
> /etc/aliases
>
> mailman-loop: root
>
> While I don't understand Mailman's Postfix configuration, I believe this
> this is a nice simple solution which would probably solve the problem
> for Postfix too.
This may be an interesting suggestion, but I don't think there's a way in
Debian for a package to add a system-wide mail alias.
Cheers,
Thijs
Acknowledgement sent
to "USPS Priority Solutions" <[email protected]>:
Extra info received and forwarded to list. Copy sent to Mailman for Debian <[email protected]>.
(Thu, 26 Jan 2017 19:09:05 GMT) (full text, mbox, link).
Dear Customer,
This is to confirm that your item has been shipped at January 24.
Review the document that is attached to this e-mail!
Your help is greatly appreciated,
Tracy Shafer,
USPS Chief Station Manager.
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.