Your message dated Wed, 14 Mar 2012 06:32:10 +0000 with message-id <e1s7hko-0006ya...@franck.debian.org> and subject line Bug#663595: fixed in pyspf 2.0.5-2+squeeze1 has caused the Debian Bug report #663595, regarding python-spf: Gets confused by CNAMEs while parsing SPF records 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 ow...@bugs.debian.org immediately.) -- 663595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: python-spf Version: 2.0.5-2 Severity: grave Justification: causes non-serious data loss Intermediate CNAMEs encountered while parsing SPF records confuse python-spf into returning a hard error (domain has two or more type TXT spf records) when really there is no second SPF record, and the existing one is indeed valid. Discovered while manually looking at the SPF record for "support.zendesk.com" (which was in turn included by the SPF record for "dropbox.com"): $ /usr/share/pyshared/spf.py support.zendesk.com PermError: Two or more type TXT spf records found. $ host -t txt support.zendesk.com support.zendesk.com is an alias for www.shard-2.int.zendesk.com. www.shard-2.int.zendesk.com is an alias for www.pod-1.int.zendesk.com. www.pod-1.int.zendesk.com descriptive text "v=spf1 ip4:184.106.12.190 ip4:173.203.47.176 ip4:173.203.47.177 ~all" $ /usr/share/pyshared/spf.py www.pod-1.int.zendesk.com v=spf1 ip4:184.106.12.190 ip4:173.203.47.176 ip4:173.203.47.177 ~all In other words, the SPF record for www.pod-1.int.zendesk.com is valid, and so is the one for support.zendesk.com, but the (double) indirection via CNAME(s) causes an error. The consequence is some domains with valid SPF records are perceived as having faulty ones, and then depending on how SPF is used on the receiving end, email messages from the affected domains may be mis-classified as spam or outright rejected. Regards, adc -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages python-spf depends on: ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-central 0.6.16+nmu1 register and build utility for Pyt ii python-dns 2.3.4-4 DNS client module for Python python-spf recommends no packages. Versions of packages python-spf suggests: pn python-yaml <none> (no description available) -- no debconf information
--- End Message ---
--- Begin Message ---Source: pyspf Source-Version: 2.0.5-2+squeeze1 We believe that the bug you reported is fixed in the latest version of pyspf, which is due to be installed in the Debian FTP archive: pyspf_2.0.5-2+squeeze1.diff.gz to main/p/pyspf/pyspf_2.0.5-2+squeeze1.diff.gz pyspf_2.0.5-2+squeeze1.dsc to main/p/pyspf/pyspf_2.0.5-2+squeeze1.dsc python-spf_2.0.5-2+squeeze1_all.deb to main/p/pyspf/python-spf_2.0.5-2+squeeze1_all.deb spf-tools-python_2.0.5-2+squeeze1_all.deb to main/p/pyspf/spf-tools-python_2.0.5-2+squeeze1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 663...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman <sc...@kitterman.com> (supplier of updated pyspf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Tue, 13 Mar 2012 16:16:06 -0400 Source: pyspf Binary: python-spf spf-tools-python Architecture: source all Version: 2.0.5-2+squeeze1 Distribution: stable Urgency: low Maintainer: Scott Kitterman <sc...@kitterman.com> Changed-By: Scott Kitterman <sc...@kitterman.com> Description: python-spf - sender policy framework (SPF) module for Python spf-tools-python - sender policy framework (SPF) tools for Python Closes: 663595 Changes: pyspf (2.0.5-2+squeeze1) stable; urgency=low . * Backport upstream CVS commit 1.108.2.75 to correct pyspf processing with CNAMES - already fixed in 2.0.7 in Wheezy/Sid (Closes: #663595) - Changes inline due to lack of existing patch system Checksums-Sha1: 794e2715d6d50099f97c2b29f6608c743192ad02 1477 pyspf_2.0.5-2+squeeze1.dsc e37d02878744953c69284d5de9f8f2786aaf6216 10975 pyspf_2.0.5-2+squeeze1.diff.gz 8ae51870c5d10214c9482408ced45c6d8c3399a4 46024 python-spf_2.0.5-2+squeeze1_all.deb dc5292b67ff4e1b0c76691e368f2555849dde350 18808 spf-tools-python_2.0.5-2+squeeze1_all.deb Checksums-Sha256: c750191c348632a77852b394c2a690c2811559326d718f7556815e5a60510d60 1477 pyspf_2.0.5-2+squeeze1.dsc 15824b1680840a3e31bb6f87b6dcf1af841a901d74f08cab169a3c69bbada145 10975 pyspf_2.0.5-2+squeeze1.diff.gz 508e20c5051ce7d0d8c6dcb9c32d8a8bb1f5fb439a3b0125a2f11691f6c14631 46024 python-spf_2.0.5-2+squeeze1_all.deb 267c0d09a2bbada19f05fcddbe896f1214e55a0ffdda094ba3ad0f1967d96d79 18808 spf-tools-python_2.0.5-2+squeeze1_all.deb Files: e1b7e2680c7383d3e83990730a708a05 1477 python extra pyspf_2.0.5-2+squeeze1.dsc b955465c915a6c7ff4567f87df33eaed 10975 python extra pyspf_2.0.5-2+squeeze1.diff.gz 7a7bb185b89e2bc48971088d8317f004 46024 python extra python-spf_2.0.5-2+squeeze1_all.deb e4f72fa8b93997ba57b446c79a67c205 18808 python extra spf-tools-python_2.0.5-2+squeeze1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9fsygACgkQHajaM93NaGrbcwCfdvheQTTD100fR4ZeTLRjDp7G FaoAn3LHndH7ZKUEIr20kAESeDSR7G5I =qk7i -----END PGP SIGNATURE-----
--- End Message ---
