Paul wrote:
> Unless you missed some assp entries, that
> message was delayed by ASSP and never sent
> again. Did you grep on porcupine ?
>
Pasted from Postfix list:
The response "503 .. nested MAIL command" means that ASSP messed up
its conversation with Postfix.
Like this:
Client X connects
ASSP forwards MAIL FROM from client X to Postfix
ASSP replies 4xx to RCPT TO from client X
Client Y connects
ASSP forwards MAIL FROM from client Y to Postfix
Postfix replies with 503 .. nested MAIL command
In other words, ASSP does not reset the connection after the MAIL
FROM from client X, so that Postfix is still in MAIL FROM state
when ASSP forwards the MAIL FROM from client Y.
> Your other assp log entries (at 11:54), appear
> to be delaying a probe of some sort (double-
> [EMAIL PROTECTED]).
>
> I don't know postfix, but your postfix entries
> (11:54, 12:14, 12:48) appear to be attempts to
> send something to porcupine, but they were
> rejected by the receiver because porcupine's
> call-out verification of the sender was
> delayed by your server. Strange, because
> there are no assp entries to support that.
> (That reminds me how flawed are call-outs can
> be.)
>
There were a few factors involved here. I know Wietse uses sender
address verification - I did as well. It also appears both of us were
greylisting. So the address verification probes were getting rejected
by the greylist - made things messy. I have since disabled sender
address verification.
> As to the initial error that was sent by your
> postfix server, what happens when postfix is
> delayed by assp? In my MTA logs I usually see
> a rset and quit before the connection is
> dropped, but it's possible that postfix may
> try again with the same connection.
>
I haven't seen any delays between ASSP and my local Postfix - but I do
see a number of sequences like:
May 27 00:18:28 foxy postfix/smtpd[26983]: connect from
amfes.com[66.55.57.2]
May 27 00:18:28 foxy postfix/smtpd[26983]: lost connection after CONNECT
from amfes.com[66.55.57.2]
May 27 00:18:28 foxy postfix/smtpd[26983]: disconnect from
amfes.com[66.55.57.2]
don't know if that's a normal result of ASSP seeing a client, connecting
to Postfix to process - and then dropping the client due to some
nefarious intent of the sender.
--
Daniel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user
