You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by an...@oc384.net on 2011/09/21 00:23:42 UTC

logging issue when response=554

I got this in my log:

INFO  17:08:16,852 | james.mailetcontext | Attempting delivery of
Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net to
host mx1.comcast.net. at 76.96.62.116 from andrew@xxx.com for addresses
[xxx@comcast.net]
INFO  17:08:17,069 | james.mailetcontext | Could not connect to SMTP
host: 76.96.62.116, port: 25, response: 554
INFO  17:08:17,069 | james.mailetcontext | Temporary exception delivering
mail
(Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net:
INFO  17:08:17,069 | james.mailetcontext | Storing message
Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net
into outgoing after 2 retries

It didn't really tell me much.  I captured the traffic on the interface
and found this:

"554 imta14.westchester.pa.mail.comcast.net comcast 174.48.my.ip Comcast
requires that all mail servers must have a PTR record with a valid
Reverse DNS entry. Currently your mail server does not fill that
requirement. For more information, refer to:
http://help.comcast.net/content/faq/PTR"

It would be good if the log entries contained more of the reject message.

-Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


RE: logging issue when response=554

Posted by an...@oc384.net.
I used tcpdump and then WireShark to view the capture file.  Not all mail
servers object to the missing PTR.  Apparently comcast does however I
was able to send mail to gmail accounts prior to setting my reverse DNS
PTR record so your issue may be something else.

Yeah you'll want to make sure your originating IP works w/reverse lookup.

-Andrew


On 9/20/2011, "Hillel Bilman" <hb...@ecommunicate.biz> wrote:

>Hi,
>
>I think you may have answered my question on why emails to gmail have been
>failing. I get the same symptoms
>of 20/09/11 21:18:52 INFO  James.Mailet: RemoteDelivery: Attempting delivery
>of Mail1316546231564-61-to-gmail.com to host gmail-smtp-in.l.google.com. at
>209.85.229.26 for addresses [testclient@gmail.com]
>20/09/11 21:19:24 INFO  James.Mailet: RemoteDelivery: Exception delivering
>message (Mail1316546231564-61-to-gmail.com) - [EOF]
>20/09/11 21:19:24 INFO  James.Mailet: RemoteDelivery: Temporary exception
>delivering mail (Mail1316546231564-61-to-gmail.com:
>20/09/11 21:19:24 INFO  James.Mailet: RemoteDelivery: Storing message
>Mail1316546231564-61-to-gmail.com into outgoing after 0 retries
>
>1. How did you capture the traffic on the Interface? Did you need to use
>wireshark?
>2. If we force James to bind on one IP and ensure that IP has a reverse DNS
>lookup, then when it connects to another mail server it has to use that IP.
>
>Is this what you did?
>
>Thanks
>
>-----Original Message-----
>From: andrew@oc384.net [mailto:andrew@oc384.net]
>Sent: 21 September 2011 12:24 AM
>To: server-user@james.apache.org
>Subject: logging issue when response=554
>
>I got this in my log:
>
>INFO  17:08:16,852 | james.mailetcontext | Attempting delivery of
>Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net to
>host mx1.comcast.net. at 76.96.62.116 from andrew@xxx.com for addresses
>[xxx@comcast.net] INFO  17:08:17,069 | james.mailetcontext | Could not
>connect to SMTP
>host: 76.96.62.116, port: 25, response: 554 INFO  17:08:17,069 |
>james.mailetcontext | Temporary exception delivering mail
>(Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net:
>INFO  17:08:17,069 | james.mailetcontext | Storing message
>Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net
>into outgoing after 2 retries
>
>It didn't really tell me much.  I captured the traffic on the interface and
>found this:
>
>"554 imta14.westchester.pa.mail.comcast.net comcast 174.48.my.ip Comcast
>requires that all mail servers must have a PTR record with a valid Reverse
>DNS entry. Currently your mail server does not fill that requirement. For
>more information, refer to:
>http://help.comcast.net/content/faq/PTR"
>
>It would be good if the log entries contained more of the reject message.
>
>-Andrew
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>For additional commands, e-mail: server-user-help@james.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


RE: logging issue when response=554

Posted by Hillel Bilman <hb...@ecommunicate.biz>.
Hi,

I think you may have answered my question on why emails to gmail have been
failing. I get the same symptoms
of 20/09/11 21:18:52 INFO  James.Mailet: RemoteDelivery: Attempting delivery
of Mail1316546231564-61-to-gmail.com to host gmail-smtp-in.l.google.com. at
209.85.229.26 for addresses [testclient@gmail.com]
20/09/11 21:19:24 INFO  James.Mailet: RemoteDelivery: Exception delivering
message (Mail1316546231564-61-to-gmail.com) - [EOF]
20/09/11 21:19:24 INFO  James.Mailet: RemoteDelivery: Temporary exception
delivering mail (Mail1316546231564-61-to-gmail.com:
20/09/11 21:19:24 INFO  James.Mailet: RemoteDelivery: Storing message
Mail1316546231564-61-to-gmail.com into outgoing after 0 retries

1. How did you capture the traffic on the Interface? Did you need to use
wireshark?
2. If we force James to bind on one IP and ensure that IP has a reverse DNS
lookup, then when it connects to another mail server it has to use that IP.

Is this what you did?

Thanks

-----Original Message-----
From: andrew@oc384.net [mailto:andrew@oc384.net] 
Sent: 21 September 2011 12:24 AM
To: server-user@james.apache.org
Subject: logging issue when response=554

I got this in my log:

INFO  17:08:16,852 | james.mailetcontext | Attempting delivery of
Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net to
host mx1.comcast.net. at 76.96.62.116 from andrew@xxx.com for addresses
[xxx@comcast.net] INFO  17:08:17,069 | james.mailetcontext | Could not
connect to SMTP
host: 76.96.62.116, port: 25, response: 554 INFO  17:08:17,069 |
james.mailetcontext | Temporary exception delivering mail
(Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net:
INFO  17:08:17,069 | james.mailetcontext | Storing message
Mail1316548949650-5ce6d995-d4aa-48af-8bff-7f236a53e843-to-comcast.net
into outgoing after 2 retries

It didn't really tell me much.  I captured the traffic on the interface and
found this:

"554 imta14.westchester.pa.mail.comcast.net comcast 174.48.my.ip Comcast
requires that all mail servers must have a PTR record with a valid Reverse
DNS entry. Currently your mail server does not fill that requirement. For
more information, refer to:
http://help.comcast.net/content/faq/PTR"

It would be good if the log entries contained more of the reject message.

-Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org