J.R. Oldroyd wrote: > > Great report with good logs, thanks. > > The ASSP log shows that there is no ASSP-MTA SSL. This is optional > but if the client is doing SSL to ASSP you probably also want to > enable SSL to the MTA if possible. You'll need to do that in the > MTA's configuration. Not doing so shouldn't cause a problem, > however. > > The MTA log shows the SMTP dialog. I notice two things there: > first that the "RCPT" verb should be "RCPT TO:<[email protected]>" > but it only shows "RCPT [email protected]". Nevertheless the MTA > responds OK. Second, after the DATA verb, the MTA responds with > the usual "354 OK" but no message data appears to follow. This > looks like the client just stopped talking. > > Is that client a spammer, or a real sender? > > Some spammers do just stop talking and for them the timeout is > ASSP's way of getting rid of them, coupled with penalty box score > impacts. > > -jr
ASSP and the MTA are actually on the same box, so I didn't bother with SSL between the two. Sender is legit, plus they keep retrying to send the email. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
