FW: [Mailman-Users] No Bounce Notification

Tony web at thetrick.us
Mon Sep 20 20:24:40 CEST 2004

Attached is most of the log file.  Please let me know if anyone finds
anything out of the ordinary.


-----Original Message-----
From: Tony [mailto:web at thetrick.us]
Sent: Sunday, September 19, 2004 2:41 PM
To: Mark Sapiro; mailman-users at python.org
Subject: RE: [Mailman-Users] No Bounce Notification

See comments below:  It appears without the knowing what the logs are
saying, there is little that can be done.  I have logged a case with the
helpdesk and will let you know the results.

Thanks again for your help and responses.  At least I understand a bit of
what is going on.

>Thanks for the info and your help Mark.  I have done some looking at the
>Cpanel site, but will do some more.
>I sent the test message per your instructions and as a result, the list
>owner received this message:
>Subject: Uncaught bounce notification
>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).
>For more information see:
>It appears the bounce process is processing the messages, but is only
>forwarding on unrecognized messages.  What is it doing with recognized
>bounce messages?

Yes, the message above is exactly the expected result for an
unrecognized bounce. For a recognized bounce, bounce processing should
note the bounce in the bounce log I've mentioned before (actually, it
does this for the unrecognized bounces as well). It then updates the
bounce score for the user and takes any appropriate action as
determined by the options on the Bounce Processing page for the list.

The settings you reported earlier in this thread should unsubscribe the
user and notify the list owner on the first bounce.

>The settings in Cpanel are minimal and the settings in Mailman appear to be
>correct.  I prefer not going to the webhoster helpdesk blind without having
>a sense of the problem.  Does the above statement of the problem appear to
>be accurate?   Anyone have any additional thoughts?

My thoughts are:

1) Is the list actually sending mail? (I assume you would be asking
different questions if it weren't, but assumptions are always risky.)
Yes, mail is being sent to the "one" good address on this testlist

2) Are there actually invalid addresses on the list that should be
bouncing? (It would be easy to mass subscribe one to be sure. Maybe
you've already done this.)
Invalid addresses are as follows:
12345 at operamail.com; abc at abc.abc; noaddess at yahoo.com; tony at tony.tony

When I subscribed everyone on my testlist, I received the bounce
confirmation for all of the addresses that were just added, included the
invalid ones.

3) What's in the Mailman bounce log?
Wish we knew.  I don't have access to them

4) Are there any relevant entries in the Mailman error log (in the same
directory as the bounce log)?
Wish we knew.  I don't have access to them

Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.766 / Virus Database: 513 - Release Date: 9/17/2004

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Mailman_Log.txt
Url: http://mail.python.org/pipermail/mailman-users/attachments/20040920/b8084ef1/attachment.txt 

More information about the Mailman-Users mailing list