Re: Very strange DNS Problem; MX not found

2017-05-08 Thread Georg Sotsas
Hello and thanks for your answers, allowing TCP queries to our internal resolver fixed the problem. Kind regards 2017-05-05 22:41 GMT+02:00 Jörg Backschues : > On 05.05.2017 at 14:48h Georg Sotsas wrote: > > The mails sent to .x...@guilford.com >> remain in t

Re: Different LMTP configuration for different clients

2017-05-08 Thread Angel L. Mateo
El 06/05/17 a las 03:12, Peter escribió: On 04/05/17 18:13, Angel L. Mateo wrote: My problem is that I can't classify by recipient. I should do it by client IP. Is this possible in a transport map? No, instead use smtpd_client_restrictions with check_client_access and a FILTER result point

multiple actions, SPF to skip greylist

2017-05-08 Thread Andreas Schamanek
Hi there, I am open to suggestions but for now I am running Postfix 2.11.3 (Debian Stable), Postgrey 1.35 and postfix-policyd-spf-python 2.0.1, joined together with smtpd_recipient_restrictions = (...) reject_unauth_destination check_policy_service unix:private/policyd-spf # postg

Re: multiple actions, SPF to skip greylist

2017-05-08 Thread Wietse Venema
Andreas Schamanek: > I found a thread from 2014 by Wietse re. [Idea: multiple actions in > access/header_checks/policy results][1]. It seems this is what I am > looking for, but it hasn't been hacked into Postfix, or have I just > missed the respective documentation? > > [1]: > http://postfi

Re: multiple actions, SPF to skip greylist

2017-05-08 Thread Scott Kitterman
On Monday, May 08, 2017 08:09:45 PM Andreas Schamanek wrote: > Hi there, > > I am open to suggestions but for now I am running Postfix 2.11.3 > (Debian Stable), Postgrey 1.35 and postfix-policyd-spf-python 2.0.1, > joined together with > > smtpd_recipient_restrictions = (...) > reject_unaut