Relaying via smtp.gmail.com

[Byung-Hee HWANG]

Hi, last night i did dream about email stuff.
At the dream, Google's an engineer told me that
"Now qmail offers relaying via smtp.gmail.com,
so open your eye!" ;;

After the dream, i did google. Then i discovered
two examples, below:

[1] http://tomclegg.net/qmail/#qmail-remote-auth
[2] http://www.fehcom.de/qmail/spamcontrol/README_spamcontrol.html

Actually, smtp.gmail.com requires TLS. But there
is no mention on TLS in [1]. But [2] includes TLS!
Tonight i'll test them. Then i'll tell you about the
results!

Sincerely,

--
Byung-Hee HWANG, KNU
∑ WWW: http://izb.knu.ac.kr/~bh/

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

[Byung-Hee HWANG]

Byung-Hee HWANG <b...@izb.knu.ac.kr> writes:

> [1] http://tomclegg.net/qmail/#qmail-remote-auth
> [2] http://www.fehcom.de/qmail/spamcontrol/README_spamcontrol.html

Doing patches for qmail was somewhat difficult to
me using Postfix. So [2]'s testing postpone. Tom's
qmail-remote-auth seems good under where non-TLS.
Below is the screenshot:

@400000004a48293e28a53854 new msg 396
@400000004a48293e28e64894 info msg 396: bytes 481 from <b...@betla.desktop> qp 2000 uid 1004
@400000004a48293e2a57978c starting delivery 12: msg 396 to remote b...@izb.knu.ac.kr
@400000004a48293e2bf02564 status: local 0/10 remote 1/20
@400000004a48293e2fbbd364 delivery 12: failure: Connected_to_155.230.165.20_but_sender_was_rejected./Remote_host_said:_530_5.7.0_Must_issue_a_STARTTLS_command_first/
@400000004a48293e3221dacc status: local 0/10 remote 0/20
@400000004a48293e3506d24c bounce msg 396 qp 2002
@400000004a48293e35f0bd1c end msg 396

Above 155.230.165.20 is running Postfix with TLS environment as Google's
[smtp.gmail.com]. While testing, i discovered another good reference for
Google smarthost with qmail [3]. Later i'll try to test that, too.

Sincerely,

[3] http://dev.qmailrocks.org/smtproutes.shtml

[Roman Levitskiy]

On Mon, Jun 29, 2009 at 13:23:45 +0900, Byung-Hee HWANG wrote:
> Byung-Hee HWANG <b...@izb.knu.ac.kr> writes:
>
> > [1] http://tomclegg.net/qmail/#qmail-remote-auth
> > [2] http://www.fehcom.de/qmail/spamcontrol/README_spamcontrol.html
>

> Doing patches for qmail was somewhat difficult to
> me using Postfix. So [2]'s testing postpone. Tom's
> qmail-remote-auth seems good under where non-TLS.

I'm using qmail-remote-auth.patch (3942 bytes long, seems like it
is Tom's patch) with simple service running locally on port 26:

sis:[/root]# cat /service/smtp.2/run

#!/bin/sh
exec tcpserver -v 127.0.0.1 26 openssl s_client -quiet -connect
my.mail.provider:465 2>&1

sis:[/root]#

Several years. Just works.

--
Roman

[Byung-Hee HWANG]

Roman Levitskiy <ro...@letinet.org> writes:

> On Mon, Jun 29, 2009 at 13:23:45 +0900, Byung-Hee HWANG wrote:
>> Byung-Hee HWANG <b...@izb.knu.ac.kr> writes:
>>

>> > [1] http://tomclegg.net/qmail/#qmail-remote-auth
>> > [2] http://www.fehcom.de/qmail/spamcontrol/README_spamcontrol.html
>>

>> Doing patches for qmail was somewhat difficult to
>> me using Postfix. So [2]'s testing postpone. Tom's
>> qmail-remote-auth seems good under where non-TLS.
>
> I'm using qmail-remote-auth.patch (3942 bytes long, seems like it
> is Tom's patch) with simple service running locally on port 26:
>
> sis:[/root]# cat /service/smtp.2/run
>
> #!/bin/sh
> exec tcpserver -v 127.0.0.1 26 openssl s_client -quiet -connect
> my.mail.provider:465 2>&1
>
> sis:[/root]#
>
> Several years. Just works.

Very nice tip! Several hours ago, i saw getting connection with Google
MX (smtp.gmail.com) by qmail, too. Thank you so much!