pushing email directly through gmail - 06/07/10 03:38 AM
OK this is going to leave a few behind immediately but here goes:
openssl s_client -connect smtp.gmail.com:587 -starttls smtp
ehlo user
auth plain (removed)
mail from: <myusername@gmail.com>
rcpt to: < myusername@gmail.com>
data
test
.
and when I do the dot . alone on the line it's supposed to accept and deliver it. but it just sits there, forever accepting line after line of input. If I ctrl-c out to stop it, it does not send. Actual interaction:
235 2.7.0 Accepted
mail from: < myusername@gmail.com>
250 2.1.0 OK r12sm18803824ixi.14
rcpt to: < myusername@gmail.com>
250 2.1.5 OK r12sm18803824ixi.14
data
354 Go ahead r12sm18803824ixi.14
From: myusername@gmail.com
To: myusername@gmail.com
Subject: this is a test message
This is a test message
this is only a test
.
.
stop
^R
and it can't be made to accept the message and send. I'm not alone:
http://in.answers.yahoo.com/question/index?qid=20100428073821AATBWdc
He didn't get any help either. FWIW I am trying to get authenticated relaying going on some of my bash scripts so they can send email out, even when there's no local SMTP server that accepts relaying. I have it working fine (using "expect") for non ssl, but I wanted to get the ssl variant working because I want to support gmail specifically and they only do ssl smtp. This may be a problem only with gmail. (I've already fought through some other weird quirks, like the "rcpt to" must be LOWER case, others don't care) It's funny gmail is the only one I've ran into that doesn't explicitly say to end the message with a period on an empty line, they just say "go ahead".
(fyi the auth plain format is the uuencode of chr(0)USERNAMEchr(0)PASSWORD )
openssl s_client -connect smtp.gmail.com:587 -starttls smtp
ehlo user
auth plain (removed)
mail from: <myusername@gmail.com>
rcpt to: < myusername@gmail.com>
data
test
.
and when I do the dot . alone on the line it's supposed to accept and deliver it. but it just sits there, forever accepting line after line of input. If I ctrl-c out to stop it, it does not send. Actual interaction:
235 2.7.0 Accepted
mail from: < myusername@gmail.com>
250 2.1.0 OK r12sm18803824ixi.14
rcpt to: < myusername@gmail.com>
250 2.1.5 OK r12sm18803824ixi.14
data
354 Go ahead r12sm18803824ixi.14
From: myusername@gmail.com
To: myusername@gmail.com
Subject: this is a test message
This is a test message
this is only a test
.
.
stop
^R
and it can't be made to accept the message and send. I'm not alone:
http://in.answers.yahoo.com/question/index?qid=20100428073821AATBWdc
He didn't get any help either. FWIW I am trying to get authenticated relaying going on some of my bash scripts so they can send email out, even when there's no local SMTP server that accepts relaying. I have it working fine (using "expect") for non ssl, but I wanted to get the ssl variant working because I want to support gmail specifically and they only do ssl smtp. This may be a problem only with gmail. (I've already fought through some other weird quirks, like the "rcpt to" must be LOWER case, others don't care) It's funny gmail is the only one I've ran into that doesn't explicitly say to end the message with a period on an empty line, they just say "go ahead".
(fyi the auth plain format is the uuencode of chr(0)USERNAMEchr(0)PASSWORD )