Yuuichi Kagaguchi reports on 13 Dec 2010: 2. When a (long) header line is continue to the next line, it is not correctly encoded with MIME. Spaces at the head of the second line are encoded with MIME (=20), and then `smtpmail.el' recognizes the line as incorrect, which will cause an error.
I received, for example, an e-mail with header lines as (Fig .1): BEGIN--BEGIN Subject: Re: =?UTF-8?B?W+Wtpuihk+aMr+iIiOWnlOWToeS8ml0g57SA6KaB5oqV56i/6KaP?= =?UTF-8?B?56iL562J44Gu5pS56KiCKOahiCk=?= Date: Fri, 17 Dec 2010 12:30:29 +0900 END---END (Fig. 1) The first line continues to the second line. According to the header rule (in RFC?), there is a white space at the beginnig. In replying to this with a VM's `R' key, VM encodes those lines into (Fig. 2): BEGIN--BEGIN Subject: Re: =?utf-8?Q?[=E5=AD=A6=E8=A1=93=E6=8C=AF=E8=88=88=E5=A7=94=E5=93=A1=E4=BC=9A]_=E7=B4=80=E8=A6=81=E6=8A=95=E7=A8=BF=E8=A6=8F Date: 月, 20 12月 2010 181020 JST _=E7=A8=8B=E7=AD=89=E3=81=AE=E6=94=B9=E8=A8=82(=E6=A1=88)?= END---END (Fig. 2) --------------------------------------- This problem was fixed in this bugfix by encoding entire sequences of words that need encoding so that mail-mode cannot break them in the middle of the header line. This is not really a fix, but a workaround for mail-mode. This should be fixed eventually by moving to message-mode which breaks the header lines correctly. -- You received this bug notification because you are a member of Registry Administrators, which is the registrant for Debian. https://bugs.launchpad.net/bugs/490021 Title: vm: vm-mime-encode-headers may mess up recipient addresses _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : [email protected] Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
