Re: [gentoo-user] Postfix, courier-imap: checks if working

[laurent]

Hi Mike,

I receive the mail sent with your script. It verbose this:

send: 'ehlo host.domain.com\r\n'
reply: '250-host.domain.com\r\n'
reply: '250-PIPELINING\r\n'
reply: '250-SIZE 10240000\r\n'
reply: '250-VRFY\r\n'
reply: '250-ETRN\r\n'
reply: '250-STARTTLS\r\n'
reply: '250-AUTH LOGIN PLAIN\r\n'
reply: '250-AUTH=LOGIN PLAIN\r\n'
reply: '250-ENHANCEDSTATUSCODES\r\n'
reply: '250-8BITMIME\r\n'
reply: '250 DSN\r\n'
reply: retcode (250); Msg: host.domain.com
PIPELINING
SIZE 10240000
VRFY
ETRN
STARTTLS
AUTH LOGIN PLAIN
AUTH=LOGIN PLAIN
ENHANCEDSTATUSCODES
8BITMIME
DSN
send: 'mail FROM:<root@×××××××××××.com> size=427\r\n'
reply: '250 2.1.0 Ok\r\n'
reply: retcode (250); Msg: 2.1.0 Ok
send: 'rcpt TO:<laurent@×××××××××××.com>\r\n'
reply: '250 2.1.5 Ok\r\n'
reply: retcode (250); Msg: 2.1.5 Ok
send: 'data\r\n'
reply: '354 End data with <CR><LF>.<CR><LF>\r\n'
reply: retcode (354); Msg: End data with <CR><LF>.<CR><LF>
data: (354, 'End data with <CR><LF>.<CR><LF>')
send: 'Content-Type: multipart/mixed; 
boundary="===============1111368381694963480=="\r\nMIME-Version: 
1.0\r\nFrom: root@×××××××××××.com\r\nTo: 
laurent@×××××××××××.com\r\nDate: Wed, 08 Apr 2009 17:04:45 
+0200\r\nSubject: Mail testing 
message\r\n\r\n--===============1111368381694963480==\r\nContent-Type: 
text/plain; charset="us-ascii"\r\nMIME-Version: 
1.0\r\nContent-Transfer-Encoding: 7bit\r\n\r\nTest message body 
;)\r\n--===============1111368381694963480==--\r\n.\r\n'
reply: '250 2.0.0 Ok: queued as 4DDD1F24001\r\n'
reply: retcode (250); Msg: 2.0.0 Ok: queued as 4DDD1F24001
data: (250, '2.0.0 Ok: queued as 4DDD1F24001')
send: 'quit\r\n'
reply: '221 2.0.0 Bye\r\n'
reply: retcode (221); Msg: 2.0.0 Bye

So it looks like working.
Actually I'm trying to make apache send an e-mail via postfix. I went 
through installing a complete virtual mail host but maybe I will go back 
to a simpler way.
I got the smtp, pop, imap installed, I don't really need the virtual 
host stuff. I could send email even before. hm. Obscure.

I'm using neko vm as server side programming, trying to make neko make 
apache send an e-mail. I think my next step is to connect apache to postfix.
I'm looking into this, if you have any idea where I should look you're 
welcome.

Thanks
Laurent

Mike Kazantsev a écrit :
> On Wed, 08 Apr 2009 01:04:53 +0200
> laurent <laurent@××××××××××××.org> wrote:
>
>
>> Why don't I have thos lines showing:
>>
>
> Short: because you (client) have to send some of them _to_ server, since
> it doesn't know what you need when you just connected.
>
>
>> EHLO domain.com
>>
>
> That's what a typical client sends in response to server smtp
> announcement.
>
>
>> 250-mail.domain.com
>> 250-PIPELINING
>> 250-SIZE 10240000
>> 250-VRFY
>> 250-ETRN
>> 250-STARTTLS
>> 250-AUTH LOGIN PLAIN
>> 250-AUTH=LOGIN PLAIN
>> 250-XVERP
>> 250 8BITMIME
>>
>
> And that's what server responds to it, further announcing it's
> capabilities, so client may choose how to relay the message thru it.
>
>
> Try this simple python script to check smtp capability of your server:
> http://fraggod.net/svc/dumpz/d7936/
>
> Just save it into some file like "smtp_test.py", replace "domain" with
> address of your server and use "python smtp_test.py" to launch it.
> It should show you whole protocol exchange between client and server,
> along with ocurred errors, if any.
>
>
> For me (working case), it's output looks like this ("domain.com" here is
> my mail domain, for example case):
>
> send: 'ehlo [127.0.0.1]\r\n'
> reply: '250-domain.com\r\n'
> reply: '250-PIPELINING\r\n'
> reply: '250-SIZE 10240000\r\n'
> reply: '250-VRFY\r\n'
> reply: '250-ETRN\r\n'
> reply: '250-STARTTLS\r\n'
> reply: '250-ENHANCEDSTATUSCODES\r\n'
> reply: '250-8BITMIME\r\n'
> reply: '250 DSN\r\n'
> reply: retcode (250); Msg: domain.com
> PIPELINING
> SIZE 10240000
> VRFY
> ETRN
> STARTTLS
> ENHANCEDSTATUSCODES
> 8BITMIME
> DSN
> send: 'mail FROM:<mail_test@××××××.com> size=390\r\n'
> reply: '250 2.1.0 Ok\r\n'
> reply: retcode (250); Msg: 2.1.0 Ok
> send: 'rcpt TO:<postmaster@××××××.com>\r\n'
> reply: '250 2.1.5 Ok\r\n'
> reply: retcode (250); Msg: 2.1.5 Ok
> send: 'data\r\n'
> reply: '354 End data with <CR><LF>.<CR><LF>\r\n'
> reply: retcode (354); Msg: End data with <CR><LF>.<CR><LF>
> data: (354, 'End data with <CR><LF>.<CR><LF>')
> send: 'Content-Type: multipart/mixed; boundary="===============0122837587=="\r\nMIME-Version: 1.0\r\nFrom: mail_test@××××××.com\r\nTo: postmaster@××××××.com\r\nDate: Wed, 08 Apr 2009 07:22:07 +0600\r\nSubject: Mail testing message\r\n\r\n--===============0122837587==\r\nContent-Type: text/plain; charset="us-ascii"\r\nMIME-Version: 1.0\r\nContent-Transfer-Encoding: 7bit\r\n\r\nTest message body ;)\r\n--===============0122837587==--\r\n.\r\n'
> reply: '250 2.0.0 Ok: queued as 555F1101FDC\r\n'
> reply: retcode (250); Msg: 2.0.0 Ok: queued as 555F1101FDC
> data: (250, '2.0.0 Ok: queued as 555F1101FDC')
> send: 'quit\r\n'
> reply: '221 2.0.0 Bye\r\n'
> reply: retcode (221); Msg: 2.0.0 Bye
>
>
>