Open plutocrat opened 5 years ago
I'm not familiar with exim, but this sounds like an MTA issue vs. an issue with postgrey. If you are submitting all messages processed by exim regardless of if they are incoming our outgoing, you could perhaps use postgrey's whitelist feature to skip your internal IP address blocks. Otherwise, I would recommend looking into how to keep exim from submitting outgoing messages to postgrey completely.
Yeah, I was looking at the whitelisting approach, but the host IP will change, so I'd have to add it to the whitelist each time that happened.
I've been looking around at other approaches. The one on the Exim wiki uses this line to accept all authenticated users. That might be a useful addition to this acl?
accept authenticated = *
Hi, Having used postgrey before when I was using postfix, I wanted to try to get it going on a client's exim-based server. I followed the instructions here. https://github.com/schweikert/postgrey/blob/master/README.exim
First of all, a suggestion. On my server the postgrey installation used a URL+port socket. The correct way to represent this in exim is readsocket{inet:127.0.0.1:10023}. Might be handy to mention this.
OK, so now, having got the config working, I left my server running overnight and saw all the expected greylist entries in /var/log/exim4/mainlog. Great. However, when I tried to send out an email from my email client, using the server as my SMTP server, I found out it was greylisting outgoing emails! My email would be rejected with a greylisting message in Thunderbird, then allowed when I tried again a few minutes later. This process was repeated each time I had a different recipient.
So obviously this isn't the intended behaviour. Greylisting should only happen on incoming emails, surely? Any way of making this happen? I initially thought I could use the Whitelist file, but the host 123.45.56.67 is my external IP address, which changes every so often, not the IP address of the mail server running exim.