Package: rss2email
Version: 1:3.8-1~exp1
Severity: minor
When I set “encodings = UTF-8” in my rss2email.cfg, then some of the
From headers ended up doubly-encoded. For example, from the feed
<http://prawo.vagla.pl/node/feed> I got e-mail with this header:
From:
=?utf-8?b?PT91dGYtOD9xP3ByYXdvXz03Q19WYUdsYT0yRXBsX1ByYXdvX2lfSW50ZXJuZXRf?=
=?utf-8?b?LV9wcmF3bmVfYXNwZWt0eV89MjJzcG89QzU9ODJlY3plPUM1PTg0c3R3YV9pbmZv?=
=?utf-8?b?cm1hY3lqbmVnbz0yMj0zQV9WYUdsYT89?= <user@rss2email.invalid>
This is what you get when you decode the B-encoded part:
=?utf-8?q?prawo_=7C_VaGla=2Epl_Prawo_i_Internet_-_prawne_aspekty_=22spo=C5=82ecze=C5=84stwa_informacyjnego=22=3A_VaGla?=
And you'd need to decode it again to get the actual feed title and author:
prawo | VaGla.pl Prawo i Internet - prawne aspekty "społeczeństwa
informacyjnego": VaGla
Now, apparently this doesn't happen if US-ASCII is included as the first
encoding, and admittedly removing it from the list wasn't the smartest
thing to do on my side. But still, I would prefer if rss2email wouldn't
let me shoot myself in the foot this way. :)
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64
Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rss2email depends on:
ii python2.7 2.7.6-7
ii python3-feedparser 5.1.3-2
ii python3-html2text 3.200.3-2
pn python3:any <none>
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
