[Reportbug-maint] Bug#614880: python-reportbug: forces the envelope-from address of the sent message when using the MTA

Francesco Poli (wintermute) invernomuto at paranoici.org
Wed Feb 23 22:54:06 UTC 2011


Package: python-reportbug
Version: 4.12.6
Severity: normal

Hi!

Many thanks for maintaining my favorite bug reporting tool!  :-)


I've recently changed some things in my mail setup and noticed
a little issue with reportbug.

My current situation is as follows: my main public e-mail address
is the one I configured in the EMAIL and DEBEMAIL environment
variables (see below). Its domain (paranoici.org) has a strict SPF.
On the other hand, I send mail through exim4 on my box, which,
in its turn, is configured to use my ISP's SMTP server as smarthost.
In order to avoid bounces from those recipients that check SPF,
I cannot use my main public address in the Envelope-From field,
but only in the From field.
So I put the address I have at my ISP in /etc/email-addresses:
this way, the Envelope-From field is set to my address at my ISP,
while the From field is set to my main public address.

This seems to work well, when sending mail with Sylpheed, Mutt,
and presumably any MUA that sends mail by invoking something like
/usr/sbin/sendmail -t -i

Unfortunately, reportbug seems to force the Envelope-From field to
be equal to the From field.
This means that, when I use reportbug and send a message to
submit at b.d.o through my local exim4 MTA and my ISP's SMTP server,
the Envelope-From is set to my main public address.
I am afraid that this will generate bounces, as soon as
bugs.debian.org begins to check SPF (which I think it doesn't,
currently).

If I understand correctly, this behavior is due to the -f option
in /usr/share/pyshared/reportbug/submit.py:347

        pipe = os.popen('%s -f %s -oi -oem %s' % (
            mta, commands.mkarg(faddr), jalist), 'w')

Would it be possible to drop this option, so that (if I understand
correctly) the decision on how the Envelope-From should be set is
left to the MTA ?

Are there any alternative solutions?

Thanks for your time.


** Environment settings:
DEBEMAIL="invernomuto at paranoici.org"
EMAIL="invernomuto at paranoici.org"
DEBFULLNAME="Francesco Poli (wintermute)"
INTERFACE="text"

** /home/frx/.reportbugrc:
mode standard
ui text


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-reportbug depends on:
ii  apt                     0.8.10.3         Advanced front-end for dpkg
ii  python                  2.6.6-3+squeeze5 interactive high-level object-orie
ii  python-support          1.0.11           automated rebuilding support for P

python-reportbug recommends no packages.

Versions of packages python-reportbug suggests:
ii  reportbug                     4.12.6     reports bugs in the Debian distrib

-- no debconf information





More information about the Reportbug-maint mailing list