Hello,
This one is a little bit old but I thought I would add to
this thread anyhow. It appears that the problem with the "uncaught
bounce notifications" was with the mail client the user had been using.
The mail client that had this issue is named "Compoze" and is available
through our Web portal. When the user hit the "reply" button in Compoze,
the To: field was [EMAIL PROTECTED] address.
As a test case, I sent some mail to a test list serve I created
"[EMAIL PROTECTED]" that had 2 email addresses (my own and a
colleague) subscribed to it. I gathered results from 3 mailers: Lotus
Notes (which is the school's supported mail client), Compoze and
Evolution (my mail client) and what was returned when I clicked on the
"Reply" button and on the "Reply to all" button for each mail clients
after receiving mail. It is surprising how 3 mail clients came up with
different results by clicking on these buttons.
Lotus Notes
=> Reply
To: [EMAIL PROTECTED]
=> Reply to all
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Compoze
=> Reply
To: [EMAIL PROTECTED]
=> Reply to all
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Evolution
=> Reply
To: [EMAIL PROTECTED]
=> Reply to all
To: [EMAIL PROTECTED]
I am going to work with our Web portal people to see why compoze is
working the way it is and see if this is resolvable.
-Darren
Old Dominion University
Norfolk, VA
On Thu, 2005-12-01 at 13:53, Mark Sapiro wrote:
> Darren G Pifer wrote:
> >
> >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).
> >
> >> ===== Original Message =====
> >> Date: Nov 25, 2005 12:30 PM
> >> From: [EMAIL PROTECTED]
> >> To: [EMAIL PROTECTED]
> >> Cc:
> >> Subject: Re: [LIST] We need new officers for the spring semester!
> >>
> Although some of the header info is garbled, possibly by a copy and
> paste operation, this is clearly a copy of an "Uncaught bounce
> notification". The original "bounce" appears to be a post erroneously
> sent to [EMAIL PROTECTED] instead of [EMAIL PROTECTED]
>
> My question now, is are we sure there isn't some miscommunication
> between you, the list owner and the original user? Do we even really
> know that the original user (or anyone other than the list owner)
> actually received this specific message?
------------------------------------------------------
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
