Jump to content

Email Trouble


Bill H
 Share

Recommended Posts

Here is are the three lines of Wireshark I receive when trying to use one particulat Email Server:

 

 

Line_____Frame______Originate IP_____Destination IP__Service

2479___13.643247___211.146.45.24___34.41.150.162___SMTP___Response: 220 APPSERVER1.XXX.local SMTP service ready

2481___13.644240___34.41.150.162___211.146.45.24___SMTP___Command: EHLO localhost

2483___13.659967___211.146.45.24___34.41.150.162___SMTP___Response: 500 Syntax error, command unrecognized

 

It looks like the Email Server does not understand the newer EHLO command.

 

Under this condition the Email Client would then send the older HELO command.

 

PBXNSIP does not send the HELLO command.

 

Is this a bug or a missing condition?

 

Bill H

Link to comment
Share on other sites

Here is are the three lines of Wireshark I receive when trying to use one particulat Email Server:

 

 

Line_____Frame______Originate IP_____Destination IP__Service

2479___13.643247___211.146.45.24___34.41.150.162___SMTP___Response: 220 APPSERVER1.XXX.local SMTP service ready

2481___13.644240___34.41.150.162___211.146.45.24___SMTP___Command: EHLO localhost

2483___13.659967___211.146.45.24___34.41.150.162___SMTP___Response: 500 Syntax error, command unrecognized

 

It looks like the Email Server does not understand the newer EHLO command.

 

Under this condition the Email Client would then send the older HELO command.

 

PBXNSIP does not send the HELLO command.

 

Is this a bug or a missing condition?

 

Well that message itself is not a problem. It is actually the only way to find out if the server understands EHLO.

 

Does the rest of the email delivery work?

Link to comment
Share on other sites

Well that message itself is not a problem. It is actually the only way to find out if the server understands EHLO.

 

Does the rest of the email delivery work?

 

 

No it does not process any futher than that.

 

The Wireshark just sits there.

 

That is why I suspected that PBXNSIP was nor responding to the "Response: 500 Syntax error, command unrecognized" message.

 

Bill H

Link to comment
Share on other sites

No it does not process any futher than that.

 

The Wireshark just sits there.

 

That is why I suspected that PBXNSIP was nor responding to the "Response: 500 Syntax error, command unrecognized" message.

 

Hmm. I remember there was a problem with those old servers. Might be fixed already. Maybe you can wait a few days and then try the upcoming 3.1.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...