Highlighted
Honored Contributor.
Honored Contributor.
2769 views

Telnet to port 25 testing through GWIA fails

While troubleshooting an email issue I used the old telnet to port 25, and was sending to several unrelated gmail addresses and it failed. I then tested the same at another GW 2012 SP2 site and it failed.
I have tried using Putty and telnet. Telnet was even tried from Windows and Linux. Normal GW client email sends OK, as does some backup software that uses GWIA as the SMTP relay, just not from telnet. Does anyone have any ideas why this is the case?

TELNET TRANSCRIPT:

[INDENT]220 mail.ef.com.au Ready
helo
250 mail.ef.com.au Ok
mail from:test@ef.com.au
250 Ok
rcpt to:me@gmail.com
250 Ok
data
354 Enter mail, end with "." on a line by itself

hi there at 1741
.
250 Ok
. <--------- Here is where I expect to see a "Transferred message"
500 Syntax error
.
500 Syntax error
.
500 Syntax error
.
500 Syntax error
.
500 Syntax error[/INDENT]


GWIA LOG showing the error

17:40:19 F3C8 DMN: MSG 113639 Accepted connection: [192.168.0.11] (ef5.ef.corp)
17:40:40 F3C8 DMN: MSG 113639 Receiving file: /gwsystem/efgwia2/wpgate/GWIA2/receive/811f5325.032
17:41:17 F3C0 MSG 113639 Processing inbound message: /gwsystem/efgwia2/wpgate/GWIA2/receive/811f5325.032
17:41:17 F3C0 MSG 113639 Sender: test@ef.com.au
17:41:17 F3C0 MSG 113639 Recipient: me@gmail.com
17:41:17 F3C0 DoCharSetDetection: Character Set: ISO-8859-1, Confidence = 98
17:41:17 F3C0 MSG 113639 Converting message to SMTP: /gwsystem/efgwia2/wpgate/GWIA2/send/x235f13d.008
17:41:17 F3C0 MSG 113639 Queuing message to daemon: /gwsystem/efgwia2/wpgate/GWIA2/send/s235f13d.008
17:41:17 F3C0 Recipient: me@gmail.com
17:41:17 F3D0 DMN: MSG 113639 Sending file: /gwsystem/efgwia2/wpgate/GWIA2/send/p235f13d.008
17:41:17 F3D0 NgwResQuery(gmail.com, 1, 15)
17:41:17 F3D0 Querying server (# 1) address = 192.168.0.2
17:41:17 F3D0 HEADER:
17:41:17 F3D0 opcode = QUERY, id = 54, rcode = NOERROR, flags: qr rd ra
17:41:17 F3D0 query = 1, answer = 5, authority = 0, additional = 1
17:41:17 F3D0
17:41:17 F3D0 QUESTIONS:
17:41:17 F3D0 gmail.com, type = MX, class = IN
17:41:17 F3D0
17:41:17 F3D0 ANSWERS:
17:41:17 F3D0 gmail.com
17:41:17 F3D0 type = MX, class = IN, ttl = 1 hour 9 mins 50 secs, dlen = 25
17:41:17 F3D0 preference = 10, name = aspmx2.googlemail.com
17:41:17 F3D0 gmail.com
17:41:17 F3D0 type = MX, class = IN, ttl = 1 hour 9 mins 50 secs, dlen = 11
17:41:17 F3D0 preference = 10, name = aspmx3.googlemail.com
17:41:17 F3D0 gmail.com
17:41:17 F3D0 type = MX, class = IN, ttl = 1 hour 9 mins 50 secs, dlen = 19
17:41:17 F3D0 preference = 1, name = aspmx.l.google.com
17:41:17 F3D0 gmail.com
17:41:17 F3D0 type = MX, class = IN, ttl = 1 hour 9 mins 50 secs, dlen = 9
17:41:17 F3D0 preference = 5, name = alt1.aspmx.l.google.com
17:41:17 F3D0 gmail.com
17:41:17 F3D0 type = MX, class = IN, ttl = 1 hour 9 mins 50 secs, dlen = 9
17:41:17 F3D0 preference = 5, name = alt2.aspmx.l.google.com
17:41:17 F3D0
17:41:17 F3D0 ADDITIONAL RECORDS:
17:41:17 F3D0 aspmx.l.google.com
17:41:17 F3D0 type = A, class = IN, ttl = 3 mins 3 secs, dlen = 4
17:41:17 F3D0 internet address = 173.194.79.26
17:41:17 F3D0
17:41:17 F3D0 DMN: MSG 113639 Attempting to connect to aspmx.l.google.com
17:41:18 F3D0 DMN: MSG 113639 Connected to [173.194.79.26] (aspmx.l.google.com)
17:41:19 F3D0 DMN: MSG 113639 Send Failure: 550 5.7.1 RFC 2822 specifications for more information. e5si5113815pba.357 - gsmtp
17:41:19 F3D0 DMN: MSG 113639 SMTP session ended: [173.194.79.26] (aspmx.l.google.com)
17:41:27 F476 MSG 113639 Analyzing result file: /gwsystem/efgwia2/wpgate/GWIA2/result/r235f13d.008
17:41:27 F476 MSG 113639 Command: gmail.com
17:41:27 F476 MSG 113639 Response: 220 mx.google.com ESMTP e5si5113815pba.357 - gsmtp
17:41:27 F476 MSG 113639 Command: EHLO mail.ef.com.au
17:41:27 F476 MSG 113639 Response: 250 ok
17:41:27 F476 MSG 113639 Command: MAIL FROM:<test@ef.com.au>
17:41:27 F476 MSG 113639 Response: 250 2.1.0 OK e5si5113815pba.357 - gsmtp
17:41:27 F476 MSG 113639 Command: RCPT TO:<me@gmail.com>
17:41:27 F476 MSG 113639 Response: 250 2.1.5 OK e5si5113815pba.357 - gsmtp
17:41:27 F476 MSG 113639 Command: DATA
17:41:27 F476 MSG 113639 Response: 354 Go ahead e5si5113815pba.357 - gsmtp
17:41:27 F476 MSG 113639 Detected error on SMTP command
17:41:27 F476 MSG 113639 Command: Data...
17:41:27 F476 MSG 113639 Response: 550 5.7.1 RFC 2822 specifications for more information. e5si5113815pba.357 - gsmtp

17:41:27 F476 Building undeliverable message

Can any one else confirm if they can telnet successfully through their GW 2012 SP2 GWIA to a GMAIL address

Thanks
Gordon
Labels (2)
0 Likes
14 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Telnet to port 25 testing through GWIA fails

Hi Gordon,

Have you ensured that your gwia is not an open relay, and have you checked whether or not you are blacklisted?

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
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Telnet to port 25 testing through GWIA fails

Hi Gordon,

I've just done an MXToolbox lookup on ef.com.au and it says that it doesn't exist! Perhaps take a look at your MX records? Of course MXToolbox could be having a bad day!

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
Highlighted
Visitor.

Re: Telnet to port 25 testing through GWIA fails

You have supplied no to / from / subject IN the message...

After data

To: <recipient's e-mail address><enter>
From: <your display e-mail address><enter>
Subject: <Subject field of Email message><enter>

Blah,

Foo,

.
Highlighted
Honored Contributor.
Honored Contributor.

Re: Telnet to port 25 testing through GWIA fails

laurabuckley;2282347 wrote:
Hi Gordon,

I've just done an MXToolbox lookup on ef.com.au and it says that it doesn't exist! Perhaps take a look at your MX records? Of course MXToolbox could be having a bad day!

Cheers,


He he, ef.com.au was used to protect the guilty 😉
The real site and domain isn't blacklisted anywhere.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Telnet to port 25 testing through GWIA fails

Sorry about that Gordon - I was just checking!
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
Highlighted
Honored Contributor.
Honored Contributor.

Re: Telnet to port 25 testing through GWIA fails

Bob-O-Rama;2282348 wrote:
You have supplied no to / from / subject IN the message...

After data

To: <recipient's e-mail address><enter>
From: <your display e-mail address><enter>
Subject: <Subject field of Email message><enter>

Blah,

Foo,

.


Hmmm...But I have been using this quite often over the years with no problems until now, which is quite surprising:
:
EHLO (or helo) domain name
MAIL FROM:itsupport@blah.com
RCPT TO:itsupport@blah.com
DATA
Subject: test message
<CRLF>
<CRLF>
This is a test
.
QUIT


Maybe Google are more stringent in their checks, nowadays. This may explain why the in-house developed software can't send either, their code needs updating to take into account the new rules. Nice tip Bob.

- Gordon
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Telnet to port 25 testing through GWIA fails

Hi Gordon,

Just glad that you came right. Bob, excellent advice 🙂

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
Highlighted
Visitor.

Re: Telnet to port 25 testing through GWIA fails

gordon_mzano;2282351 wrote:
Hmmm...But I have been using this quite often over the years with no problems until now, which is quite surprising.

Maybe Google are more stringent in their checks, nowadays. This may explain why the in-house developed software can't send either, their code needs updating to take into account the new rules. Nice tip Bob.


The hint was the "550 5.7.1 RFC 2822 specifications for more information." Google that, and you'll find a lot of people in your situation. A From: is required, Subject: is recommended. To: is optional as that is the mechanism by which BCC: works.

-- Bob
0 Likes
Highlighted
Visitor.

Re: Telnet to port 25 testing through GWIA fails

Just remember, Laura, "If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below..." 😉

-- Bob
Highlighted
Honored Contributor.
Honored Contributor.

Re: Telnet to port 25 testing through GWIA fails

gordon_mzano;2282343 wrote:


TELNET TRANSCRIPT:

[INDENT]220 mail.ef.com.au Ready
helo
250 mail.ef.com.au Ok
mail from:test@ef.com.au
250 Ok
rcpt to:me@gmail.com
250 Ok
data
354 Enter mail, end with "." on a line by itself

hi there at 1741
.
250 Ok
. <--------- Here is where I expect to see a "Transferred message"
500 Syntax error
.
500 Syntax error
.
500 Syntax error
.
500 Syntax error
.
500 Syntax error[/INDENT]


Interestingly the same telnet commands that fail if sent through Groupwise, work if I issue them against the ISP's SMTP relay, gmail then receives them fine.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Telnet to port 25 testing through GWIA fails

Chuckle - have done so Bob 🙂
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.