Mark Sapiro wrote:
> If the bounce is reported directly back to Mailman as a
> reject at the SMTP level, there should be something in Mailman's
> smtp-failure log.
B-I-N-G-O (I think)! The smtp-failure log has entries like:
Apr 27 01:20:09 2006 (12765) All recipients refused: {'[EMAIL PROTECTED]':
(550, 'Verification failed for <[EMAIL PROTECTED]>\nNo Such
User Here\nSender verify failed')}, msgid:
<[EMAIL PROTECTED]
Apr 27 01:20:09 2006 (12765) delivery to [EMAIL PROTECTED] failed with
code 550: Verification failed for <[EMAIL PROTECTED]>
No Such User Here
Sender verify failed
Seems like SMTP is rejecting mail that is supposed to have come from
"[EMAIL PROTECTED]". That address does not - and never did -
exist as a real account as far as I know. In the past (when all was
working) the server must have been configured with less stringent sender
verification, or some exception for "mailman-" addresses.
Sure enough, if I temporarily create an account "[EMAIL PROTECTED]",
everything starts working as expected. Not sure if that's the "proper"
solution...I'm guessing I don't really need the account, but rather an
SMTP rule of some sort to allow the necessary sender addresses.
Now I have the ammunition I need to confront my host again...THANKS!!
Kris
------------------------------------------------------
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
