From: Karl O. P. <ko...@me...> - 2015-06-10 02:35:41
|
On Tue, 09 Jun 2015 18:18:29 -0400 Alex Regan < > >> This is on postfix-2.10. > >> > >>> Whitelisting via sqlgrey is the wong approach. > >> > >> It looks like this was auto-whitelisted, because it has seen this > >> IP/email combination previously, no? > > > > Then it must be that the email is exiting postfix and > > passing through amavis and being re-injected back > > into postfix. You'll need to make sure that amavis > > is either on a trusted network (127.0.0.1) or > > uses lmtp not smtp or has some other way of getting the mail back > > into postfix that does not get greylisted. > > All of the networks involved are on the amavis "TRUSTED" or in > @mynetworks. > > I'm not doubting what you're saying, but here's a thread that seems > to indicate it's the expected behavior: Looks like what I'm saying is wrong. The policy daemon is called for each destination address. See the postfix SMTPD_POLICY_README. > Here's another one from Lionel discussing: > > http://sourceforge.net/p/sqlgrey/mailman/sqlgrey-users/thread/42F...@bo.../ > > Could that be the solution here as well? "That" being rcpt_awl? Dunno. Looks like as of postfix 2.1 there is an "instance" variable passed to the policy daemon that could be used to keep from adding multiple header lines. It's not clear how this would work and it's not implemented in sqlgrey. Something for somebody's todo list. > > I'm going to have to use postfix to strip them because I believe it's > causing some mail to be rejected because the headers are too large. That sounds like a sensible approach. Since the policy check is smtpd you ought to be able to use header_checks = pcre:/etc/postfix/header_checks with file content of: /^X-Greylist: whitelisted by SQLgrey/ IGNORE I'd bet there's an even more clever way to "collapse" all the identical entries but haven't investigated. Regards, Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |