[Mailman-Users] strange bounce message

2005-09-16 Thread Anne Ramey
A couple of people have sent replies to one of my lists today and 
several of the messages bounced like this:

   ===
THIS IS A WARNING MESSAGE ONLY
YOU DO NOT NEED TO RESEND YOUR MESSAGE
===
 
  A temporary error occured while delivering to the following address(es):
 
pfenno at ncees.org: 454 TLS not available, must be connected via TCP
 
  I will continue trying to send the message until it is delivered or
  expires.

They've replied without incident before.  It looks like they have 
changed something on their end to require the message to be delivered 
TLS, which the server this message is attempting to deliver to does not 
support, and that there is nothing I can do...is that correct.  What can 
I tell the sender to do to prevent this? Any pointers would be 
appreciated.  I've been using mailman for a couple of years and haven't 
run into this before.
-- 
Anne
--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] strange bounce message

2005-09-16 Thread Mark Sapiro
Anne Ramey wrote:

A couple of people have sent replies to one of my lists today and 
several of the messages bounced like this:

   ===
THIS IS A WARNING MESSAGE ONLY
YOU DO NOT NEED TO RESEND YOUR MESSAGE
===
 
  A temporary error occured while delivering to the following address(es):
 
pfenno at ncees.org: 454 TLS not available, must be connected via TCP
 
  I will continue trying to send the message until it is delivered or
  expires.

They've replied without incident before.


Are you saying the list is pfenno at ncees.org and replyers received
that bounce instead of the reply going to the list? Are they all in
the same domain? Did the bounces all come from the same MTA? which one?


It looks like they have 
changed something on their end to require the message to be delivered 
TLS, which the server this message is attempting to deliver to does not 
support, and that there is nothing I can do...is that correct.


Maybe. This may also be a temporary issue with your incoming MTA that
may resolve before the messages expire and they may be ultimately
delivered.


What can 
I tell the sender to do to prevent this? Any pointers would be 
appreciated.  I've been using mailman for a couple of years and haven't 
run into this before.

Probably nothing, but it may depend on the answers to my first set of
questions.

If in fact something has changed at their end, they probably can't do
anything about it unless they changed it in which case they should
already know what to do about it.

--
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] strange bounce message

2005-09-16 Thread jc dill
Anne Ramey wrote:
 A couple of people have sent replies to one of my lists today and 
 several of the messages bounced like this:
 
===
 THIS IS A WARNING MESSAGE ONLY
 YOU DO NOT NEED TO RESEND YOUR MESSAGE
 ===
  
   A temporary error occured while delivering to the following address(es):
  
 pfenno at ncees.org: 454 TLS not available, must be connected via TCP
  
   I will continue trying to send the message until it is delivered or
   expires.
 
 They've replied without incident before.  It looks like they have 
 changed something on their end to require the message to be delivered 
 TLS, which the server this message is attempting to deliver to does not 
 support, and that there is nothing I can do...is that correct.  What can 
 I tell the sender to do to prevent this? Any pointers would be 
 appreciated.  I've been using mailman for a couple of years and haven't 
 run into this before.

This is an smtp mail server error which has nothing to do with mailman. 
  It looks like the message is coming from their local smtp server and 
is saying that their smtp server can't reach your smtp server.  If the 
people who are getting these bounce messages are all sending from 
different servers then the problem is with your smtp server.

jc

--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] strange bounce message

2005-09-16 Thread Mark Sapiro
Anne Ramey wrote:

Mark Sapiro wrote:
 Anne Ramey wrote:
 
 
A couple of people have sent replies to one of my lists today and 
several of the messages bounced like this:

  ===

  THIS IS A WARNING MESSAGE ONLY
  YOU DO NOT NEED TO RESEND YOUR MESSAGE
  ===

A temporary error occured while delivering to the following address(es):

  pfenno at ncees.org: 454 TLS not available, must be connected via TCP

I will continue trying to send the message until it is delivered or
expires.

They've replied without incident before.
 
 
 
 Are you saying the list is pfenno at ncees.org and replyers received
 that bounce instead of the reply going to the list? 
They are telling me the reply when to all but 3 people on the list, who 
got this message.

I'm confused. W replied to the list. The reply reached the list and was
received by all but X, Y and Z who received the above message. Is this
correct? Were X, Y and Z prior posters in the thread and mentioned in
To: or Cc:?


Are they all in
 the same domain?
I think so, yes.
  Did the bounces all come from the same MTA? which one?
I think they must have come from the ncees.org mta, but I don't see the 
corresponding messages in the logs.

What was in the From: header of the above message?

That specific message should only be sent to the sender of the post, W
in this case. Is it possible that W received the three messages (or
one message) mentioning X, Y and Z?


snip
 If in fact something has changed at their end, they probably can't do
 anything about it unless they changed it in which case they should
 already know what to do about it.

Not likely with this group.  If their tech dept.s changed something, 
they may have no idea.  I'm trying to figure out if it has to do with 
mailman's method of delivery or the sender's/replier's method of sending 
(in addition to trying to figure out what to tell them).


That's what I was trying to say. If something changed at their end,
they personally probably can't do anything about it unless they
personally did the change.

I'm still not sure what's going on, but I am guessing that what really
happened is that W's reply was sent directly to X, Y and Z (via To: or
Cc:) and your list didn't send to them at all and the 'delivery delay'
notice(s) was sent to W and that the problem has nothing to do with
your list and involves delivery of mail from W directly to X, Y and Z.

We need more specific information about what was sent and how and who
received these notices and their full contents and headers, not just
the above excerpt, before we can know for sure.

--
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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=showamp;file=faq01.027.htp


Re: [Mailman-Users] strange bounce message

2005-09-16 Thread Mark Sapiro
I'm looking at this again and I have more thoughts/questions.

Mark Sapiro wrote:

Anne Ramey wrote:

Mark Sapiro wrote:
 Anne Ramey wrote:

snip

A temporary error occured while delivering to the following address(es):

  pfenno at ncees.org: 454 TLS not available, must be connected via TCP


snip

 
 Are you saying the list is pfenno at ncees.org and replyers received
 that bounce instead of the reply going to the list? 


You didn't really answer. Is pfenno at ncees.org the list or perhaps
a list member or?


snip

  Did the bounces all come from the same MTA? which one?
I think they must have come from the ncees.org mta, but I don't see the 
corresponding messages in the logs.


I don't think so. The message appears to have originated from an MTA
that was trying to deliver to [EMAIL PROTECTED] and was unable to
establish an SMTP session. If there's anything in the logs at
ncees.org it would only be a connection refusal.

I think we still need more information.

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

--
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=showamp;file=faq01.027.htp