Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Goldberg <david.goldberg6@verizon.net>
Subject: address parsing problem in latest CVS
Date: Wed, 06 Sep 2006 23:28:32 -0400	[thread overview]
Message-ID: <x7lkow5p9b.fsf@davestoy.homelinux.org> (raw)

I'm back from a couple week's vacation and at work did a CVS update
before getting into email with Gnus.  I've found that the patches from
9/1 with the following ChangeLog entry have resulted in broken
addresses being passed to smtpmail:

2006-09-01  Katsumi Yamaoka  <yamaoka@jpl.org>

        * gnus-art.el (gnus-decode-address-function): New variable.
        (article-decode-encoded-words): Use it to decode headers which are
        assumed to contain addresses.
        (gnus-mime-delete-part): Remove useless `or'.

        * gnus-sum.el (gnus-decode-encoded-address-function): New variable.
        (gnus-summary-from-or-to-or-newsgroups): Use it to decode To header.
        (gnus-nov-parse-line): Use it to decode From header.
        (gnus-get-newsgroup-headers): Ditto.
        (gnus-summary-enter-digest-group): Use it to decode `to-address'.

        * mail-parse.el (mail-decode-encoded-address-region): New alias.
        (mail-decode-encoded-address-string): New alias.

        * rfc2047.el (rfc2047-quote-special-characters-in-quoted-strings):
        New function.
        (rfc2047-encode-message-header, rfc2047-encode-region): Use it.
        (rfc2047-strip-backslashes-in-quoted-strings): New fnction.
        (rfc2047-decode-region): Use it; add optional argument `address-mime'.
        (rfc2047-decode-string): Ditto.
        (rfc2047-decode-address-region): New function.
        (rfc2047-decode-address-string): New function.

The symptom looks like this (addresses sanitized):

220 exchange.work.ORG Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at  Wed, 6 Sep 2006 15:57:54 -0400 
EHLO my-PC.work.ORG.work.org
250-exchange.work.ORG Hello [10.0.0.73]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
MAIL FROM: <me@work.org> SIZE=3565
250 2.1.0 me@work.org....Sender OK
RCPT TO: <someone@yahoo.com>
250 2.1.5 someone@yahoo.com 
RCPT TO: <"\\_^_<someoneelse\\@work.org\\>\\")>
501 5.5.4 Invalid Address
QUIT
221 Closing connection. Good bye.

Process SMTP exited abnormally with code 256

The address in question is always the first on the CC line.  Most of
my addresses are of the form "Real Name" <user@whatever.com>.
Manually stripping the addresses is a workaround but became too
frustrating so I simply backed out to the immediately previous
versions of rfc2047.el, gnus-sum.el, gnus-art.el and mail-parse.el for
now.  Because I'm just back I did not have time to investigate any
further than that but am willing to do so after I get caught up a bit
at work.   I am more than happy to test patches too :-)

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net




             reply	other threads:[~2006-09-07  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07  3:28 Dave Goldberg [this message]
2006-09-07  4:47 ` Katsumi Yamaoka
2006-09-07  9:54   ` Katsumi Yamaoka
2006-09-07 10:08     ` Katsumi Yamaoka
2006-09-07 12:01       ` Katsumi Yamaoka
2006-09-07 13:09         ` Dave Goldberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x7lkow5p9b.fsf@davestoy.homelinux.org \
    --to=david.goldberg6@verizon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).