Your message dated Wed, 24 Nov 2021 16:04:55 -0500
with message-id <1882343.B6BLmTvM3o@localhost>
and subject line Re: Bug
has caused the Debian Bug report #947355,
regarding postfix-policyd-spf-python: command /usr/bin/policyd-spf exit status
120
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
947355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947355
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postfix-policyd-spf-python
Version: 2.9.1-0+deb10u1
Severity: important
Dear Maintainer,
I am using Postfix with policyd-spf. It always worked until I did a
fresh install of Buster, taking configuration files from Stretch, where
it all worked without problems.
Now however, it fails and Postfix returns a Temperror when receiving
email.
Excerpt from /var/log/mail.log:
Dec 22 00:27:03 efatsum postfix/smtpd[17265]: connect from
mailgate1.deutschebahn.com[46.18.62.69]
Dec 22 00:27:03 efatsum postfix/smtpd[17265]: Anonymous TLS connection
established from mailgate1.deutschebahn.com[46.18.62.69]: TLSv1.2 with cipher
ECDHE-RSA-AES256-GCM-SHA 384 (256/256 bits)
Dec 22 00:28:44 efatsum postfix/smtpd[17265]: warning: problem talking to
server private/policy-spf: Connection timed out
Dec 22 00:30:25 efatsum postfix/smtpd[17265]: warning: problem talking to
server private/policy-spf: Connection timed out
Dec 22 00:30:25 efatsum postfix/smtpd[17265]: NOQUEUE: reject: RCPT from
mailgate1.deutschebahn.com[46.18.62.69]: 451 4.3.5 <[email protected]>:
Recipient address rejected: Server configuration problem;
from=<[email protected]>to=<[email protected]>
proto=ESMTP helo=<mailgate1.deutschebahn.com>
Dec 22 00:30:30 efatsum postfix/smtpd[17265]: disconnect from
mailgate1.deutschebahn.com[46.18.62.69] ehlo=2 starttls=1 mail=1 rcpt=0/1
rset=1 quit=1 commands=6/7
Dec 22 00:31:25 efatsum policyd-spf[17268]: prepend Received-SPF:Temperror
(mailfrom) identity=mailfrom;
client-ip=46.18.62.69;helo=mailgate1.deutschebahn.com;
[email protected]; receiver=<UNKNOWN>
Dec 22 00:31:25 efatsum policyd-spf[17268]: Traceback (most recent calllast):
Dec 22 00:31:25 efatsum policyd-spf[17268]: File"/usr/bin/policyd-spf", line
11, in <module>#012load_entry_point('spf-engine==2.9.1', 'console_scripts',
'policyd-spf')()
Dec 22 00:31:25 efatsum policyd-spf[17268]:
File"/usr/lib/python3/dist-packages/spf_engine/policyd_spf.py", line 169,
inmain#012 sys.stdout.flush()
Dec 22 00:31:25 efatsum policyd-spf[17268]: BrokenPipeError: [Errno 32]Broken
pipe
Dec 22 00:31:25 efatsum postfix/spawn[17267]: warning:
command/usr/bin/policyd-spf exit status 120
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages postfix-policyd-spf-python depends on:
ii adduser 3.118
pn postfix <none>
ii python3 3.7.3-1
pn python3-authres <none>
ii python3-pkg-resources 40.8.0-1
pn python3-spf <none>
pn python3-spf-engine <none>
postfix-policyd-spf-python recommends no packages.
postfix-policyd-spf-python suggests no packages.
--- End Message ---
--- Begin Message ---
On Mon, 06 Jan 2020 02:15:19 -0500 Scott Kitterman <[email protected]>
wrote:
> I've done some additional investigation and I'm confident that the exist
status
> 120 was due to postfix closing the connection to the policy server before the
> DNS timed out. I don't know why. I've run tests with a stop watch to
verify
> the timeout behaviour of the policy server and I don't see anything in your
> postfix configuration that would cause it to terminate the connection early,
so
> I'm mystified.
>
> I guess if it's working now, there's not much more to do.
I think it's been long enough we can close this.
Scott K
--- End Message ---
