[Mailman-Users] Making all bounces, even temporary ones, go to list owner
Whitcomb, Jeff
jmwhitco at samford.edu
Wed Feb 21 18:37:43 CET 2007
In response to Mark's email number 9 below. I have always received
delayed messages as a list owner, and did not know that I am not
supposed to having the list configured as he mentions.
The message I get is:
"The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it. This mailing list has been configured to send all unrecognized
bounce messages to the list administrator(s)."
When I open the attachment, it has:
"Your message has been delayed and is still awaiting delivery to the
following recipient(s):
<email address>
(Was addressed to <email address>)
Message delayed
Could not resolve mail server name because DNS server did not respond in
time."
The delayed message also has two attachments, one is an error status
message that says:
"Reporting-MTA: dns; mailrelay.<originating domain>
Received-From-MTA: dns; server5.<originating domain> (unverified
[xxx.xxx.xxx.xxx])
Arrival-Date: Mon, 19 Feb 2007 15:44:47 -0600
Final-Recipient: rfc822; <destination email address>
Action: delayed
Status: 0.0.0 (Unknown class - no additional status information
available)"
The other attachment appears to be the header of the original email.
Before I went through and stripped out server addresses and put fake
stuff in, I wanted to see what information I need to send where to
determine if this is an unrecognized bounce format that needs to be
added to MailMan, or if it might be something else?
Thanks,
Jeff Whitcomb, MCP
Technology Services Manager
Cumberland School of Law - Samford University
205-726-4662
-----Original Message-----
From: mailman-users-bounces+jmwhitco=samford.edu at python.org
[mailto:mailman-users-bounces+jmwhitco=samford.edu at python.org] On Behalf
Of mailman-users-request at python.org
Sent: Tuesday, February 20, 2007 5:00 AM
To: mailman-users at python.org
Subject: Mailman-Users Digest, Vol 36, Issue 28
Send Mailman-Users mailing list submissions to
mailman-users at python.org
To subscribe or unsubscribe via the World Wide Web, visit
http://mail.python.org/mailman/listinfo/mailman-users
or, via email, send a message with subject or body 'help' to
mailman-users-request at python.org
You can reach the person managing the list at
mailman-users-owner at python.org
When replying, lease edit your Subject line so it is more specific
than "Re: Contents of Mailman-Users digest..."
Today's Topics:
1. pipermail customization (Denis)
2. Re: pipermail customization (Mark Sapiro)
3. Re: pipermail customization (Denis)
4. revisiting Mailman content-type problem (Ron Brogden)
5. Re: pipermail customization (Mark Sapiro)
6. Re: revisiting Mailman content-type problem (Mark Sapiro)
7. Making all bounces, even temporary ones, go to list owner
ASAP (Kelly Jones)
8. Re: revisiting Mailman content-type problem (JB at comcast)
9. Re: Making all bounces, even temporary ones, go to list owner
ASAP (Mark Sapiro)
----------------------------------------------------------------------
Message: 1
Date: Mon, 19 Feb 2007 19:29:00 +0200
From: Denis <denis.uzvik at gmail.com>
Subject: [Mailman-Users] pipermail customization
To: mailman-users at python.org
Message-ID: <1249068897.20070219192900 at gmail.com>
Content-Type: text/plain; charset=us-ascii
Hi guys ..
It's possible customize archived message page? (like
http://mail.python.org/pipermail/mailman-users/2004-April/035963.html
)
add custom header-footer-css ?
As I understand this pages by generated by papermail. But
unfortunately i can't find way to customize papermail.
Thanks!
------------------------------
Message: 2
Date: Mon, 19 Feb 2007 09:43:33 -0800
From: Mark Sapiro <msapiro at value.net>
Subject: Re: [Mailman-Users] pipermail customization
To: Denis <denis.uzvik at gmail.com>, mailman-users at python.org
Message-ID: <PC1760200702190943330562509e0773 at msapiro>
Content-Type: text/plain; charset=iso-8859-1
Denis wrote:
>It's possible customize archived message page? (like
>http://mail.python.org/pipermail/mailman-users/2004-April/035963.html
>)
>
>add custom header-footer-css ?
See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.048.htp>.
The template is article.html.
--
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------
Message: 3
Date: Mon, 19 Feb 2007 20:00:27 +0200
From: Denis <denis.uzvik at gmail.com>
Subject: Re: [Mailman-Users] pipermail customization
To: Mark Sapiro <msapiro at value.net>
Cc: mailman-users at python.org
Message-ID: <1448776887.20070219200027 at gmail.com>
Content-Type: text/plain; charset=us-ascii
Thanks, this is interesting!
I can't understand how to force rebild files from
/usr/local/mailman2/archives/private/webman/2007-February/*
Seems for new files all ok.
/usr/local/mailman/bin/mailmanctl restart - doesn't help : (
Can you advice please?
> Denis wrote:
>>It's possible customize archived message page? (like
>>http://mail.python.org/pipermail/mailman-users/2004-April/035963.html
>>)
>>
>>add custom header-footer-css ?
> See
>
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.048.htp>.
> The template is article.html.
------------------------------
Message: 4
Date: Mon, 19 Feb 2007 12:30:40 -0800
From: Ron Brogden <rb at islandnet.com>
Subject: [Mailman-Users] revisiting Mailman content-type problem
To: Mailman Users <mailman-users at python.org>
Message-ID: <200702191230.40080.rb at islandnet.com>
Content-Type: text/plain; charset="us-ascii"
Howdy. While researching a problem that a user was having with long
URLs
getting wrapped in their Mac mail client I came across the following
thread
from last year dicussing the very same problem:
http://mail.python.org/pipermail/mailman-users/2006-February/049477.html
To summarize, "delsp=yes; format=flowed" is getting dropped during
Mailman's
parsing of the message. At the time of the note above Mark Sapiro said
that
this was due to a mix of issues within Mailman plus the underlaying
Python
libraries.
Has there been any change of the status of this issue or is the only
workaround still to turn off attachement scrubbing and empty the header
/
footer?
Mark said previously:
"You might be able to avoid the problem if you set scrub_nondigest to No
and make sure both msg_header and msg_footer are empty, but this may
not be satisfactory for other reasons."
Cheers!
Ron
--
islandnet.com
http://www.islandnet.com
support at islandnet.com
ph: (250) 383-0096 fax: (250) 383-6698
------------------------------
Message: 5
Date: Mon, 19 Feb 2007 12:39:22 -0800
From: Mark Sapiro <msapiro at value.net>
Subject: Re: [Mailman-Users] pipermail customization
To: Denis <denis.uzvik at gmail.com>
Cc: mailman-users at python.org
Message-ID: <PC17602007021912392208125df97002 at msapiro>
Content-Type: text/plain; charset=iso-8859-1
Denis wrote:
>
>I can't understand how to force rebild files from
>/usr/local/mailman2/archives/private/webman/2007-February/*
>
>Seems for new files all ok.
>
>/usr/local/mailman/bin/mailmanctl restart - doesn't help : (
You have to rebuild the archive. See 'bin/arch --help'. If this archive
is entirely from a recent Mailman, you should have no problem, but if
early parts of the archive are from older Mailman, see 'bin/cleanarch
--help'.
--
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------
Message: 6
Date: Mon, 19 Feb 2007 16:44:52 -0800
From: Mark Sapiro <msapiro at value.net>
Subject: Re: [Mailman-Users] revisiting Mailman content-type problem
To: Ron Brogden <rb at islandnet.com>, Mailman Users
<mailman-users at python.org>
Message-ID: <PC17602007021916445200464c46bd82 at msapiro>
Content-Type: text/plain; charset="iso-8859-1"
Ron Brogden wrote:
>Howdy. While researching a problem that a user was having with long
URLs
>getting wrapped in their Mac mail client I came across the following
thread
>from last year dicussing the very same problem:
>
>http://mail.python.org/pipermail/mailman-users/2006-February/049477.htm
l
>
>To summarize, "delsp=yes; format=flowed" is getting dropped during
Mailman's
>parsing of the message. At the time of the note above Mark Sapiro
said that
>this was due to a mix of issues within Mailman plus the underlaying
Python
>libraries.
>
>Has there been any change of the status of this issue or is the only
>workaround still to turn off attachement scrubbing and empty the header
/
>footer?
It's been on my ToDo list long enough. Attached is a patch you can try
if you are willing. This patch should preserve the format and delsp
parameters on Content-Type headers for the original message body.
A couple of remarks.
If msg_header and/or msg_footer contain lines with trailing spaces, if
these are added to a Format=flowed message body, the header and/or
footer will be flowed by the end MUA - make sure these do not have
trailing spaces.
In looking at the code to develop the patch, I don't really see how the
dropping of the Format and DelSp parameters causes ultimate improper
wrapping of scrubber URLs, so I'm not sure that this patch fixes that.
The problem is real and definitely manifests itself in other ways, so
the patch (assuming it is good - I did test it to make sure it didn't
break anything obvious) is needed. I'm just not sure if it will fix
your immediate problem.
Please try the patch if you can, and report. If it doesn't fix the
wrapped URLs, I'll probably need message samples to figure it out.
--
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: flowed.patch.txt
Url:
http://mail.python.org/pipermail/mailman-users/attachments/20070219/93dd
c3ac/attachment-0001.txt
------------------------------
Message: 7
Date: Mon, 19 Feb 2007 18:01:45 -0700
From: "Kelly Jones" <kelly.terry.jones at gmail.com>
Subject: [Mailman-Users] Making all bounces, even temporary ones,
go
to list owner ASAP
To: mailman-users at python.org
Message-ID:
<26face530702191701i12504aaaka034d4904f25ebc9 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Many of my customers run tightly-controlled lists where it's important
to know (immediately, if possible) if email to any of the members is
bouncing (eg, an ISP mailing its customer base), even if the bounce is
temporary.
Is there a way to do this using the bounce processing options in
Mailman? EG, set the warn threshold really low and have all warnings
be cc'd to the list owner?
An obvious hack is to tweak the alias generator to do things like:
listname-bounces: listname-owner
but is there a cleaner (and "officially supported") way?
I realize the list owners will also get "vacation" replies, but that's
OK (in this situation, it's worth the hassle of getting these to know
when email is really bouncing)
--
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
------------------------------
Message: 8
Date: Mon, 19 Feb 2007 19:31:56 -0600
From: "JB at comcast" <justbrits at comcast.net>
Subject: Re: [Mailman-Users] revisiting Mailman content-type problem
To: "Mailman Users" <mailman-users at python.org>
Message-ID: <00eb01c7548e$f4b28d60$6701a8c0 at actualshop>
Content-Type: text/plain; charset="iso-8859-1"
Mark said:
"It's been on my ToDo list long enough. ".
While making something that works 100% Mark, why not suggest that Ron's
User's (like I have done to all of mine -:) ) use www.tinyurl.com ??
NEVER had a prob with the generated stuff and it is FREE -;):):) !!
Ed
------------------------------
Message: 9
Date: Mon, 19 Feb 2007 17:46:01 -0800
From: Mark Sapiro <msapiro at value.net>
Subject: Re: [Mailman-Users] Making all bounces, even temporary ones,
go to list owner ASAP
To: "Kelly Jones" <kelly.terry.jones at gmail.com>,
mailman-users at python.org
Message-ID: <PC17602007021917460105152120cd84 at msapiro>
Content-Type: text/plain; charset=iso-8859-1
Kelly Jones wrote:
>Many of my customers run tightly-controlled lists where it's important
>to know (immediately, if possible) if email to any of the members is
>bouncing (eg, an ISP mailing its customer base), even if the bounce is
>temporary.
>
>Is there a way to do this using the bounce processing options in
>Mailman? EG, set the warn threshold really low and have all warnings
>be cc'd to the list owner?
There are a couple of settings. You need to set both
bounce_unrecognized_goes_to_list_owner and
bounce_notify_owner_on_disable to Yes. The former sends all messages
received at the -bounces address which aren't recognized and handled
by bounce processing to the list owner. This includes the vacation
autoresponders.
This leaves messages which are recognized as bounces. Of these, bounces
for addresses that aren't list members (possibly a DSN reporting a
final delivery address different from the original) will be discarded
as will 'delayed' notices. The rest will be scored. If you set
bounce_score_threshold to 1.0 or less, the member's delivery will be
disabled on the first bounce and the owner notified along with a copy
of the bounce per bounce_notify_owner_on_disable. Now, the owner will
probably want to re-enable delivery for that member if the owner
thinks the bounce is 'temporary'.
Don't be concerned about 'soft bounces' only scoring 0.5. That's wrong
in the documentation. All bounces scored at all are scored 1.0.
Other caveats. If there are any members with bounce scores currently >=
1.0, even if the info is stale, they will be disabled the next time
cron/disabled runs.
If VERP_PROBES is set to Yes in mm_cfg.py, I think it is possible for
the message to bounce for a 'temporary' reason, and the subsequent
probe to not bounce. In this case, the member won't be disabled and
the owner won't be notified of the original message bounce.
>An obvious hack is to tweak the alias generator to do things like:
>
>listname-bounces: listname-owner
>
>but is there a cleaner (and "officially supported") way?
The only problem with the above is you lose the benefits of automated
bounce processing. If you can arrange for your MTA to both pipe the
-bounces mail to the wrapper for bounce processing and deliver it to
-owner, you can have both.
--
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users at 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/
End of Mailman-Users Digest, Vol 36, Issue 28
*********************************************
More information about the Mailman-Users
mailing list