Am 29.07.2016 um 20:06 schrieb John Hardin: > On Fri, 29 Jul 2016, Reindl Harald wrote: > >> >> >> Am 29.07.2016 um 18:15 schrieb John Hardin: >>> On Fri, 29 Jul 2016, Reindl Harald wrote: >>> >>> > Am 29.07.2016 um 03:30 schrieb Ryan Coleman: >>> > > > On Jul 28, 2016, at 2:49 PM, Reindl Harald >>> > > <h.rei...@thelounge.net> > wrote: >>> > > > > Am 28.07.2016 um 21:36 schrieb Ryan Coleman: >>> > > > > I have eliminated postgrey from the installation and things >>> are >>> > > back > > to “normal” >>> > > > > in other words you burried a problem by remove something >>> instead >>> > > fix the > reason while on every sane setup greylisting comes long >>> > > before any > content scanner >>> > > > > No, asshole. I fixed it by removing postgrey from the >>> equation. >>> > > asshole? >>> > just look in your mirror! >>> >>> *SIGH* >>> >>> Harald, please try to be more polite, and cut your fuse longer >> >> seriously - i find it interesting that you tell that me instead the >> creature which starts calling others names > > I was considering the entire exchange, not just your final response. > Your comment about removing postgrey was abusive. The conversation past > that point predictably deteriorated. > > You *don't have* to respond to name-calling. Ryan bears blame for > engaging in name-calling, but you generate a lot more traffic (and heat) > here than he does. >
the subject Using Postfix and Postgrey - not scanning after hold does not match spamassassin list theme however no need to flame in any case if done right postgrey can be used with any postfix setup, best do it selective with dynips after postscreen and rbls also use serveral milters opendmarc , openkim , clamav-milter spamass-milter or amavis framework. Note: in many countries in the EU its forbidden to silent discard spam so milters as pre queue filter mostly match this perfectly, so its wise to use them, there are also many milter frameworks that have greylisting already included. as many bots have perfect smtp code these days greylisting has lost his effectiveness widly, so depending on your server it makes no sense to use it anymore content filter like spamassassin are "expensive" always "try" to get them at a very last stage in you filter chain best practise configs can be found via google, the rest is looking at your logs and fix stuff in your filter chain when needed Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
