[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#539157: marked as done (direct SMTP send violates RFC1652 and sends unencoded 8-bit data)

Your message dated Sat, 24 Oct 2020 05:58:25 +0000 (UTC)
with message-id <Pine.BSM.4.64L.2010240557120.10464@herc.mirbsd.org>
and subject line Re: Bug#539157: direct SMTP send violates RFC1652 and sends unencoded 8-bit data
has caused the Debian Bug report #539157,
regarding direct SMTP send violates RFC1652 and sends unencoded 8-bit data
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 owner@bugs.debian.org
immediately.)


-- 
539157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539157
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 4.5
Severity: normal

I almost always use reportbug in direct SMTP mode, as I do not configure
a local MTA on the systems I run it on, which usually are chroots.

The bug reports get submitted to rietz.debian.org, which does not adver-
tise 8BITMIME in its EHLO response – yet reportbug fails to encode the
eMail body with quoted-printable or base64.

Then, rietz passes the messages to, for example, the *@mirbsd.org
servers, which do not advertise 8BITMIME either, but strip bit7 from
incoming mail. This is mostly a historic setup, originally intended
to “protect” the MDA and MUA. The message gets mangled badly (I’ve
seen quite some bad ones).

The mbox view on the Debian BTS clearly shows the 8bit characters,
in this case UTF-8, in the mbox (RFC822) format. While RFC2822 may
allow these things, RFC1652 (not obsoleted yet) explicitly states:

   If a server SMTP does not support the 8-bit MIME transport extension
   (either by not responding with code 250 to the EHLO command, or by
   not including the EHLO keyword value 8BITMIME in its response), then
   the client SMTP must not, under any circumstances, attempt to
   transfer a content which contains characters outside the US-ASCII
   octet range (hex 00-7F).

Thus, reportbug MUST be fixed to encode the eMail body prior to sending.

Please see ↓ as well:
‣ http://suihkulokki.blogspot.com/2009/07/cult-of-workarounds.html

Note that this bug report contains quite some 「Unicode」 characters ☺
I w̲i̲l̲l̲ send the mail as received by my MX as a follow-up to this PR.


-- Package-specific info:
** Environment settings:
EDITOR="/usr/bin/jupp"
DEBEMAIL="Thorsten Glaser <tg@mirbsd.de>"
INTERFACE="text"

** /home/tg/.reportbugrc:
reportbug_version "4.4"
mode expert
ui text
no-cc
header "X-Debbugs-CC: tg@mirbsd.de"
smtphost reportbug.debian.org

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh

Versions of packages reportbug depends on:
ii  apt                           0.7.21     Advanced front-end for dpkg
ii  python                        2.5.4-2    An interactive high-level object-o
ii  python-reportbug              4.5        Python modules for interacting wit

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  debconf-utils                 <none>     (no description available)
pn  debsums                       <none>     (no description available)
pn  dlocate                       <none>     (no description available)
ii  exim4                         4.69-11    metapackage to ease Exim MTA (v4) 
ii  exim4-daemon-light [mail-tran 4.69-11    lightweight Exim MTA (v4) daemon
ii  file                          5.03-1     Determines file type using "magic"
ii  gnupg                         1.4.9-4    GNU privacy guard - a free PGP rep
pn  python-gnome2-extras          <none>     (no description available)
pn  python-gtk2                   <none>     (no description available)
pn  python-urwid                  <none>     (no description available)
pn  python-vte                    <none>     (no description available)

-- no debconf information

--- End Message ---
--- Begin Message --- 
John Scott dixit:

>I believe reportbug has base64-encoded 
>my mails before, so perhaps this is no longer an issue?

Hmm, I don’t have one of the directly sent mails archived,
but the ones I get X-Debbugs-Cc’d now are base64 if they
aren’t plain ASCII, so I believe it to indeed work right
now.

Thanks,
//mirabilos
-- 
21:49⎜<allamoox:#sendmail> I have a question guys,
     ⎜    Can I use my PC as SMTP server, I use Windows 7 .
     ⎜    Already googled and Installed IIS
     ⎜    but Still I can't send E-mail

--- End Message ---
Reply to: