On 4/17/06, Jeff Friedrichs <[EMAIL PROTECTED]> wrote:
> ------ Forwarded Message
> From: Mail Delivery Subsystem <MAILER-DAEMON>
> Date: Sat, 8 Apr 2006 11:55:46 -0400 (EDT)
> To: <[EMAIL PROTECTED]>
> Subject: Returned mail: see transcript for details
>
> The original message was received at Sat, 8 Apr 2006
> 11:55:40 -0400 (EDT) from v20-5-p19.yy.net
> [208.199.x.y]
>
>    ----- The following addresses had permanent fatal
> errors ----- <[EMAIL PROTECTED]>
>     (reason: 550-Callback setup failed while verifying
> <[EMAIL PROTECTED]>)
>
>    ----- Transcript of session follows ----- ... while
> talking to my-domain.org.:
> >>> DATA
> <<< 550-Callback setup failed while verifying
> <[EMAIL PROTECTED]>
> <<< 550-Called:   204.255.x.y
> <<< 550-Sent:     MAIL FROM:<>
> <<< 550-Response: 553 5.3.0 REJECT # IP 67.19.206.84
> rejected by BRS
> <<< 550-The initial connection, or a HELO or MAIL
> FROM:<> command was
> <<< 550-rejected. Refusing MAIL FROM:<> does not help
> fight spam, disregards
> <<< 550-RFC requirements, and stops you from receiving
> standard bounce
> <<< 550-messages. This host does not accept mail from
> domains whose servers
> <<< 550-refuse bounces.
> <<< 550 Sender verify failed
> <<< 550 5.1.1 <[EMAIL PROTECTED]>... User
> unknown
> <<< 503 valid RCPT command must precede DATA
> Reporting-MTA: dns; host.yy.net
> Received-From-MTA: DNS; v20-5-p19.yy.net
> Arrival-Date: Sat, 8 Apr 2006 11:55:40 -0400 (EDT)
>
> Final-Recipient: RFC822; [EMAIL PROTECTED]
> Action: failed
> Status: 5.1.1
> Remote-MTA: DNS; my-domain.org
> Diagnostic-Code: SMTP; 550-Callback setup failed while
> verifying <[EMAIL PROTECTED]>
> Last-Attempt-Date: Sat, 8 Apr 2006 11:55:46 -0400
> (EDT)
>
> ------ End of Forwarded Message

This is the result of your attempt to send a message to the list, I guess?
It looks like your hosting company's mail server is rejecting messages
whose SMTP servers don't accept mail. Which is to say, yy.net won't
accept mail from my-domain.org, so my-domain.org refuses to accept
mail from yy.net.

This doesn't seem to be a mailman issue, but, rather, a MTA configuration issue.

--
- Patrick Bogen
------------------------------------------------------
Mailman-Users mailing list
[email protected]
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&amp;file=faq01.027.htp

Reply via email to