> On Jul 29, 2016, at 10:42 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 29.07.2016 um 19:26 schrieb Shawn Bakhtiar: >> >>> On Jul 29, 2016, at 10:12 AM, @lbutlr <krem...@kreme.com> wrote: >>> >>> On 29 Jul 2016, at 09:20, sha...@shanew.net wrote: >>>> I would generalize that even more to say that greylisting should come >>>> before any other content-based filtering (virus scanners, defanging, >>>> etc.). >>> >>> Greylisting is a great idea, in theory. In practice there are so many large >>> emailers who can’t do email properly that is causes more trouble than it >>> prevents. >>> >> >> I second that. I've tried gray listing a couple of times, and all I got from >> my users (and as the logs end up showing) is that some emails systems do not >> re-attempt delivery in an adequate enough time to be relevant to our >> business processes. When purchasing is waiting for confirmation of a hot >> rush delivery from a new vendor, gray listing can more than cause a few >> calls to the IT department. > > that's why you don't do *unconditional* greylisting
There is no way for me to know when a new vendor is setup and what their email system is setup to do. We purchase raw materials from all over the world, especially when the lab is trying out new formulations. Not sure how I could create a system that conditionally would deal with that. We purchase form mom and pop shops all the way up to multi national conglomerates. Invariably you will run into problems with gray listing, that has simply been my experience, and to avoid those problems, you are now suggestion I setup even more systemic processes (conditional gray listing) to deal with it, how many more percentage points of accuracy do I get for all that? well not enough to make it worth the effort. SA blocks A LOT. RBLs help A LOT, gray listing .... well just a little bit better, but with A LOT of headache. not worth it. > >> I also have to agree with John Hardin. At what point does the advice not >> become worth the slap in the face it comes with. >> >> As much as your advice has its merits Harald, it is also, very narrow sighted > > see next part of response too..... > > "narrow sighted" is really nonsense when one played around with all sorts of > configurations and orderings for months until making decisions how to setup > the systems > >> The reality is most of us (the other 99%) are not dedicated mail admins > > and hence that ones should listen was dedicated sysadmins spent thousands of > hours in rock stable system are explaining > >> I for one am a software engineer > > well, in fact i once was hired as software engineer before it took over the > CTO and sysadmin *additionally* and so i am not a *dedicated* mail admin > since there is database, voip, http and other services besides my development > job, but that don't change the fact that i spent counted 1200 hours alsone in > 2014 for the inbound MX where SA is only a small part of it after being > mailadmin over nearly 10 years anyways > > so i pretend taht i know what i am talking about without being only mailadmin > and nothing else >
