Hi Adrian, The error is from Exim. You should be able to switch on pipelining for the IP that ASSP uses. I think the setting is "pipelining_advertise_hosts = 1.1.1.1" but check with the docs.
I do reckon that ASSP should have been aware that the MTA did not advertise pipelining and therefore not attempt to use it though. Maybe there is a potential improvement for future there. All the best, Colin Waring Lantern Hosting Services. On 04/07/2012 11:55, Adrian Stoica wrote: > Hello, > > I have this in mta (exim) log, that is a strange behavior to me: > > Jul 4 13:13:41 mail exim[15791]: 2012-07-04 13:13:41 SMTP protocol > synchronization error (next input sent too soon: pipelining was not > advertised): rejected "" H=firewall (ASSP.nospam) [192.168.0.1] > I=[192.168.0.101]:25 next input=".\r\n" > > > This is normal ? > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
