Re: policyd-spf and temperrors

2017-03-19 Thread Alex JOST
Am 18.03.2017 um 13:42 schrieb Scott Kitterman: On March 18, 2017 6:13:15 AM EDT, Alex JOST wrote: Am 17.03.2017 um 22:38 schrieb James B. Byrne: The host system runs under CentOS-6. Other than Postfix itself all the packages on this system are either from CentOS

Re: policyd-spf and temperrors

2017-03-18 Thread Scott Kitterman
On March 18, 2017 6:13:15 AM EDT, Alex JOST wrote: >Am 17.03.2017 um 22:38 schrieb James B. Byrne: >> The host system runs under CentOS-6. Other than Postfix itself all >> the packages on this system are either from CentOS or EPEL. Python >> was last updated in

Re: policyd-spf and temperrors

2017-03-18 Thread Alex JOST
Am 17.03.2017 um 22:38 schrieb James B. Byrne: The host system runs under CentOS-6. Other than Postfix itself all the packages on this system are either from CentOS or EPEL. Python was last updated in September 2016. pypolicd-spf was last updated January 2017. These problems only evidenced

Re: policyd-spf and temperrors

2017-03-17 Thread James B. Byrne
On Fri, March 17, 2017 12:57, Thomas Leuxner wrote: > * James B. Byrne 2017.03.17 17:44: > >> Mar 17 12:31:22 inet08 postfix/spawn[14598]: warning: command >> /usr/libexec/postfix/policyd-spf exit status 1 > > It is spawned per mail in my configuration: > > $ postconf -nf

Re: policyd-spf and temperrors

2017-03-17 Thread James B. Byrne
On Fri, March 17, 2017 16:49, Scott Kitterman wrote: > > > On March 17, 2017 12:20:11 PM EDT, "James B. Byrne" > wrote: >>I have just noticed this error. I suspect this points to the root of >>our problems. What does it mean? >> >> >>Mar 17 12:16:58 inet08

Re: policyd-spf and temperrors

2017-03-17 Thread Scott Kitterman
On March 17, 2017 12:20:11 PM EDT, "James B. Byrne" wrote: >I have just noticed this error. I suspect this points to the root of >our problems. What does it mean? > > >Mar 17 12:16:58 inet08 postfix-p25/smtpd[14495]: connect from

Re: policyd-spf and temperrors

2017-03-17 Thread Noel Jones
On 3/17/2017 1:09 PM, Wietse Venema wrote: > Thomas Leuxner: > > Checking application/pgp-signature: FAILURE > -- Start of PGP signed section. >> * James B. Byrne 2017.03.17 17:20: >> >>> Mar 17 12:16:58 inet08 postfix-p25/smtpd[14495]: connect from >>>

Re: policyd-spf and temperrors

2017-03-17 Thread Wietse Venema
Thomas Leuxner: Checking application/pgp-signature: FAILURE -- Start of PGP signed section. > * James B. Byrne 2017.03.17 17:20: > > > Mar 17 12:16:58 inet08 postfix-p25/smtpd[14495]: connect from > > russian-caravan.cloud9.net[168.100.1.4] > > Mar 17 12:16:59 inet08

Re: policyd-spf and temperrors

2017-03-17 Thread Viktor Dukhovni
> On Mar 17, 2017, at 12:20 PM, James B. Byrne wrote: > > I have just noticed this error. I suspect this points to the root of > our problems. Not the cause, but a related symptom... > What does it mean? DNS lookups in policyd-spf are sufficient slow to not keep up

Re: policyd-spf and temperrors

2017-03-17 Thread Thomas Leuxner
* James B. Byrne 2017.03.17 17:44: > Mar 17 12:31:22 inet08 postfix/spawn[14598]: warning: command > /usr/libexec/postfix/policyd-spf exit status 1 It is spawned per mail in my configuration: $ postconf -nf | grep -A1 private/policyd check_policy_service {

Re: policyd-spf and temperrors

2017-03-17 Thread James B. Byrne
I have also seen this: Mar 17 12:31:22 inet08 postfix/spawn[14598]: warning: command /usr/libexec/postfix/policyd-spf exit status 1 However, these message only began to appear yesterday evening. This is the first occurrence found in logs going back to February 12: var/log/maillog:Mar 16

Re: policyd-spf and temperrors

2017-03-17 Thread Thomas Leuxner
* James B. Byrne 2017.03.17 17:20: > Mar 17 12:16:58 inet08 postfix-p25/smtpd[14495]: connect from > russian-caravan.cloud9.net[168.100.1.4] > Mar 17 12:16:59 inet08 postfix-p25/smtpd[14529]: warning: problem > talking to server private/policyd-spf: Connection timed out

Re: policyd-spf and temperrors

2017-03-17 Thread James B. Byrne
I have just noticed this error. I suspect this points to the root of our problems. What does it mean? Mar 17 12:16:58 inet08 postfix-p25/smtpd[14495]: connect from russian-caravan.cloud9.net[168.100.1.4] Mar 17 12:16:59 inet08 postfix-p25/smtpd[14529]: warning: problem talking to server

Re: policyd-spf and temperrors

2017-03-17 Thread Viktor Dukhovni
> On Mar 17, 2017, at 12:08 PM, James B. Byrne wrote: > > Mar 17 11:39:47 inet08 policyd-spf[13505]: Temperror; identity=helo; > client-ip=69.89.30.42; helo=gproxy3-pub.mail.unifiedlayer.com; > envelope-from=p...@thecargosolutionscanada.com; > receiver=b...@harte-lyne.ca

Re: policyd-spf and temperrors

2017-03-17 Thread James B. Byrne
On Fri, March 17, 2017 11:41, Viktor Dukhovni wrote: > >> On Mar 17, 2017, at 11:31 AM, James B. Byrne >> wrote: >> >> mohawkglobalta.com. 1476IN TXT "v=spf1 >> include:spf.protection.outlook.com ip4:208.33.203.70/31 -all" > > Don't forget the lookups

Re: policyd-spf and temperrors

2017-03-17 Thread Viktor Dukhovni
> On Mar 17, 2017, at 11:31 AM, James B. Byrne wrote: > > mohawkglobalta.com. 1476IN TXT "v=spf1 > include:spf.protection.outlook.com ip4:208.33.203.70/31 -all" Don't forget the lookups needed to process the "include:" clause, and the fact that DNS

policyd-spf and temperrors

2017-03-17 Thread James B. Byrne
OS=CentOS-6.8 (Linux) postconf -d | grep mail_version # version mail_version = 2.11.1 milter_macro_v = $mail_name $mail_version We are currently experiencing an outage at a remote site that happens to provide two of our four DNS services. We have also recently, I am tempted to write