Postfix + Amavis problems

[John Seth]

Have you tried adding extra headers, such as the Subject: line? Since it
appears to be wanting more headers, Postfix may be sending more than
you're fiving Amavis... This is usually how I test an smtp connection
myself:
--
$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mail.domain.com ESMTP Postfix
EHLO mail.domain.com
250-mail.domain.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-XVERP
250 8BITMIME
MAIL FROM: user at domain.com
250 Ok
RCPT TO: user at domain.com
250 Ok
DATA
354 End data with <CR><LF>.<CR><LF>
Subject: Test
Some text blah blah blah...
.
250 Ok: queued as CBDC764C1
quit
221 Bye
Connection closed by foreign host.
$
-- 

Don't know if it's looking for the subject line, but it's a thought...

 - Tony


zatharus at ncn.net said:
> I am trying to get Postfix 2.0.18 and Amavis-new-20030314 to work
> together on a RH9 system and having difficulty.  For those not
> familiar, here's a brief overview of how it is supposed to work:
>
> Postfix accepts mail on port 25
> Postfix forwards messages to amavis via localhost:10024
> Amavis opens attachements and runs them through a separate virus
> scanner.
> Amavis forwards mail accepted for delievery back to postfix via
> localhost:10025
> Postfix delivers mail to /home/Maildir/new
>
> I can get postfix to answer and deliver messages correctly from port
> 10025.
> However, when I test amavis on port 10024 I have problems:
>
> telnet 127.0.0.1 10024
>>connected to 127.0.0.1
>>Escape character is '^]'
>>220 [127.0.0.1] ESMTP amavisd-new service ready
> mail from:test at domain.com
>>250 2.1.0 Sender test at domain.com OK
> rcpt to:test at domain.com
>>250 2.1.5 Recipient test at domain.com OK
> data
>>354 End data with <CR><LF>.<CR><LF>
> testing 123.
> .
>
> The message is not delivered and the telnet session hangs.
>
> Here is the error message from /var/log/maillog
>
> warning - MIME::Parser error: ServeredHead: unexpected end of header;
> EOSToken: EOF; EOSType: EOF; Header:; testing 123.; error: BadHead:
> couldn't parse header; ProblemNear:; testing 123.
>
> Anyone else familiar with this that could help point me in the right
> direction/
>
> Thanks!
>
> Sean Johnson
>
>