* Chris <xchris...@googlemail.com>: > Hello Postfix Users :) > > I noticed: > > http://www.postfix.org/POSTSCREEN_README.html#after_220 > > > When a good client passes the deep protocol tests, postscreen(8) adds > > the client to the temporary whitelist but it cannot hand off the > > "live" connection to a Postfix SMTP server process in the middle of > > the session. Instead, postscreen(8) defers mail delivery attempts with > > a 4XX status, logs the helo/sender/recipient information, and waits > > for the client to disconnect. > > This is greylisting...and i hate greylisting... Is it possible to > disable this postscreen greylisting function? In my point of view this > is not RFC compliant. Greylisting delays mail traffic.
Technically not possible. > If I have five incoming mx records running postfix with postscreen... > and each time the sender receives a 4xx error ... This is > unacceptable. If you let the MX share one memcache instance, the second MX to receive a connection will immediately accept it. Works like a charm here. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
