From: David Maslen <david.maslen@iname.com>
Subject: Re: Postfix or Gnus problem in to: header?
Date: 10 Nov 1999 00:17:18 +1100 [thread overview]
Message-ID: <874sevhkip.fsf@iname.com> (raw)
In-Reply-To: Shenghuo ZHU's message of "09 Nov 1999 01:05:05 -0500"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> I am not sure what Postfix does. But there is a bug about the quoted
> comma in in XEmacs mail-lib (less than 1.24). So try again after
> removing the comma in the "To:" field.
OK, tried it.
To: "dmm dmm" <dmm@imp.taz.net.au> works
To: "dmm, dmm" <dmm@imp.taz.net.au> fails
To: "dmm dmm" (dmm@imp.taz.net.au) works
The last one puzzles me. This is the format that gnus-bug generates.
Using () instead of <> around the address. Postfix doesn't seem to be
able to handle this. Is that a postfix bug?
I accept the first is a bug in the mail-lib.
next prev parent reply other threads:[~1999-11-09 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-09 5:28 David Maslen
1999-11-09 6:05 ` Shenghuo ZHU
1999-11-09 12:18 ` Kai Großjohann
1999-11-09 13:27 ` David Maslen
1999-11-09 13:17 ` David Maslen [this message]
1999-11-09 16:36 ` Kai Großjohann
1999-11-09 17:51 ` Rene H. Larsen
2000-01-19 6:36 ` David Maslen
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=874sevhkip.fsf@iname.com \
--to=david.maslen@iname.com \
/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).