Highlighted
mcharbonneau@ot1 Absent Member.
Absent Member.
1525 views

420 TCP read error (caused by "AUTH NTLM CRAM-MD5 LOGIN") ?

Our site cannot e-mail the domain "ebasetech.com".

The GWIA logs show:
10:37:26 672 MSG 5643316 Sender: Admin@ottawaheart.ca
10:37:26 672 MSG 5643316 Building message: s09cdce6.010
10:37:26 672 MSG 5643316 Recipient: drawlins@ebasetech.com

10:37:27 680 DMN: MSG 5643316 Connected to [80.71.15.36] (webmail.ebasetech.com)

10:42:29 680 DMN: MSG 5643316 SMTP session ended: [80.71.15.36] (webmail.ebasetech.com)
10:42:29 680 DMN: MSG 5643316 Send Failure: 420 TCP read error
10:42:29 128 MSG 5643316 Analyzing result file: /media/nss/DOM1/OHICO/wpgate/gwia/result/r09cdce6.010
10:42:29 128 MSG 5643316 Detected error on SMTP command
10:42:29 128 MSG 5643316 Command: EHLO smtpin.ottawaheart.ca
10:42:29 128 MSG 5643316 Response: 420 TCP read error


If I capture the packets on the GWIA server and request "Follow TCP Stream", I get:
220 ***********************************************************************************
EHLO smtpin.ottawaheart.ca
250-ebasetech.com [207.35.222.131], this server offers 5 extensions
250-AUTH NTLM CRAM-MD5 LOGIN
250-SIZE 0
250-XXXA
250-AUTH=LOGIN
250B


I've tried reducing our MTU size on the GWIA server since this resolved "420 TCP read error" for one particulare site on our old NetWare server (We're on SLES10 now) but this didn't help.

I also tried what's suggested at this site, to disable Path MTU Discovery.
http://darenji.blogspot.co.uk/2009/05/groupwise-gwia-tcp-420-read-write-error.html

I'm just grasping right now hoping someone has other ideas?

Thanks,
Marc

Labels (2)
0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Re: 420 TCP read error (caused by "AUTH NTLM CRAM-MD5 LOGIN"

Just a quick suggestion....

Try using direct telnet commands (details below) and see if you can send an e-mail to that domain. Could be that they are looking for some kind of authentication method.

helo <your domain name><enter>
response should be as follows
250 OK

mail from: <your Email Address><enter>
response should be as follows
250 OK - mail from <your Email address>

rcpt to: <recipient address><enter>
response should be as follows
250 OK - Recipient <recipient address>

data<enter>
response should be as follows
354 Send data. End with CRLF.CRLF

To: <recipient's display name><enter>
From: <your display name><enter>
Subject: <Subject field of Email message><enter>
<Enter you body text><enter><enter> . <enter>
response should be as follows
250 OK

quit<enter>


Of course I could be totally wrong, but perhaps it's worth a try!

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: 420 TCP read error (caused by "AUTH NTLM CRAM-MD5 LOGIN") ?

On 11/12/2012 1:06 AM, laurabuckley wrote:
>
> Just a quick suggestion....
>
> Try using direct telnet commands (details below) and see if you can
> send an e-mail to that domain. Could be that they are looking for some
> kind of authentication method.
>
> helo <your domain name><enter>
> response should be as follows
> 250 OK
>
> mail from: <your Email Address><enter>
> response should be as follows
> 250 OK - mail from <your Email address>
>
> rcpt to: <recipient address><enter>
> response should be as follows
> 250 OK - Recipient <recipient address>
>
> data<enter>
> response should be as follows
> 354 Send data. End with CRLF.CRLF
>
> To: <recipient's display name><enter>
> From: <your display name><enter>
> Subject: <Subject field of Email message><enter>
> <Enter you body text><enter><enter> . <enter>
> response should be as follows
> 250 OK
>
> quit<enter>
>
>
> Of course I could be totally wrong, but perhaps it's worth a try!
>
> Cheers,
>
>

i tried that mysefl laura, and it worked.

but the more interesting question is if a GW 8 gWIA can send there.
Perhaps you could send a test mail to postmaster?
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: 420 TCP read error (caused by "AUTH NTLM CRAM-MD5 LOGIN"

We are "fronted" by IronPorts so no luck in testing here I'm afraid. GWIA behind a firewall.

It was just a suggestion! Perhaps that's the problem?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Knowledge Partner
Knowledge Partner

Re: 420 TCP read error (caused by "AUTH NTLM CRAM-MD5 LOGIN") ?

Laura,

On 12.11.2012 10:06, laurabuckley wrote:
>
> Just a quick suggestion....
>
> Try using direct telnet commands (details below) and see if you can
> send an e-mail to that domain. Could be that they are looking for some
> kind of authentication method.
>
> helo <your domain name><enter>


FWIW, this should be EHLO to be a really useful test. It is very easily
possible that HELO works, but EHLO (i.e ESMTP) nit, or vice-versa.

But as for the issue itself: If we could see the real LAN trace, there's
a 90% chnance we could identify the issue, and a 100% chnace to identify
the culprit (e.g local or remote site).

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: 420 TCP read error (caused by "AUTH NTLM CRAM-MD5 LOGIN"

Thank you Massimo
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.