Hi Raji,
Thx for the log, but unfortunately it tells us nothing more...
The heloEhloEnforcement tag allow to make allow optional, but if hello
is sent by a client, it must be valid, meaning it must be of the form
220 client.com ESMTP
HELO server.com
250 client.com
The missing parameter James complaints about is the 'server.com'
I was saying to double-check the hostname resolution (ping server.com
must be sucessful from your client and from your server), but it seems
you are using IP addresses and not hostnames.
The next step is to take a wireshark dump (filter on smtp) and see what
the HELO command you are sending looks like. I guess you didn't change
anything to your mail client before having that issue?
Thx,
Eric
On 20/12/11 16:37, Raju Buchi wrote:
Hi Eric
I have changed the SMPT log level to DEBUG and the following are the logs
generated when I triggered an email.
INFO 10:17:09,696 | james.smtpserver | ID=8894235 Connection established
from ip-xxx-xxx-xxx-xxx.ec2.internal (xxx-xxx-xxx-xxx)
DEBUG 10:17:09,796 | james.smtpserver | ID=8894235
org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler
received: EHLO
DEBUG 10:17:09,796 | james.smtpserver | ID=8894235 Lookup command handler
for command: EHLO
INFO 10:17:09,797 | james.smtpserver | ID=8894235
org.apache.james.protocols.smtp.core.esmtp.EhloCmdHandler: [501 5.5.4
Domain address required: EHLO]
DEBUG 10:17:09,799 | james.smtpserver | ID=8894235
org.apache.james.protocols.smtp.core.SMTPCommandDispatcherLineHandler
received: HELO
DEBUG 10:17:09,799 | james.smtpserver | ID=8894235 Lookup command handler
for command: HELO
INFO 10:17:09,799 | james.smtpserver | ID=8894235
org.apache.james.protocols.smtp.core.HeloCmdHandler: [501 5.5.4 Domain
address required: HELO]
INFO 10:18:01,159 | james.smtpserver | ID=8894235 Connection closed for
ip-xxx-xxx-xxx-xxx.ec2.internal (xxx-xxx-xxx-xxx)
I also have the ip address (xxx-xxx-xxx-xxx) in the smtpserver.xml
authorizedAddresses. Also tried doing
<heloEhloEnforcement>false</heloEhloEnforcement>.
I am not sure what you meant by "Does your server resolve correctly the
hostnames?". Is it James server or the instance from where an email is
triggered? On james server I actually see that when a request is sent from
a ec2 instance, it resolves its private (internal) IP address instead of
the public IP. I am guessing this is because James SMTP server is also
hosted on an EC2 instance within same region.
Thanks
- Raju
On Mon, Dec 19, 2011 at 11:02 PM, Eric Charles<[email protected]> wrote:
Hi Raju,
Does your server resolve correctly the hostmanes?
You could use wireshark to verify the ehlo commands.
Can you also define the SMTP log level to DEBUG and send here the logs?
Thx,
Eric
On 20/12/11 00:15, Raju Buchi wrote:
Can you please elaborate more on this. Where do I need to look to check
the
arguments?
- Raju
On Mon, Dec 19, 2011 at 3:28 PM, Norman Maurer<norman.maurer@**
googlemail.com<[email protected]>
wrote:
This looks like the issued HELO / EHLO command did not contain an
argument
, which is needed per RFC.
Bye
Norman
Am 19.12.2011 um 20:03 schrieb Raju
Buchi<raju.buchi@contentpilot.**net<[email protected]>
:
Hello Everyone...
I have been using james as SMTP server (Hosted on Amazon EC2 cloud) for
quite sometime. Emails were sent out properly last week, but today, when
I
sent out an email, James logs shows me the following message.
INFO 13:51:51,210 | james.smtpserver | ID=10921142 Connection
established
from xx.xx.xx.xx ( xx.xx.xx.xx )
INFO 13:51:51,222 | james.smtpserver | ID=10921142
org.apache.james.protocols.**smtp.core.esmtp.**EhloCmdHandler: 501
[5.5.4
Domain address required: EHLO]
INFO 13:51:51,225 | james.smtpserver | ID=10921142
org.apache.james.protocols.**smtp.core.HeloCmdHandler: 501 [5.5.4
Domain
address required: HELO]
INFO 13:51:57,613 | james.smtpserver | ID=10921142 Connection closed
for
xx.xx.xx.xx ( xx.xx.xx.xx )
Also, I have mentioned both the public ip and private ip address of the
EC2
instance. Also tried having just the public ip, but did not work.
Can any one help me to figure out the issue?
Thanks
- Raju
------------------------------**------------------------------**
---------
To unsubscribe, e-mail:
server-user-unsubscribe@james.**apache.org<[email protected]>
For additional commands, e-mail:
[email protected].**org<[email protected]>
--
Eric http://about.echarles.net
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
server-user-unsubscribe@james.**apache.org<[email protected]>
For additional commands, e-mail:
[email protected].**org<[email protected]>
--
Eric http://about.echarles.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]