Gnus development mailing list
 help / color / mirror / Atom feed
From: David Maslen <david.maslen@iname.com>
Cc: ding@gnus.org
Subject: Re: Postfix or Gnus problem in to: header?
Date: 19 Jan 2000 17:36:22 +1100	[thread overview]
Message-ID: <87snzumuu1.fsf@iname.com> (raw)
In-Reply-To: David Maslen's message of "10 Nov 1999 00:17:18 +1100"

David Maslen <david.maslen@iname.com> writes:
> 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.

To summarise, mail in the format 'address (Name)' was bouncing. The
gnus bug report system uses this format.

To follow this up myself, it was neither postfix or gnus.
The culprit was the ssmtp package from the debian gnu/linux distribution.
Gnus was calling ssmtp as the sendmail program.

The solution in case anyone else is interested is to

(setq message-send-mail-function smtpmail-send-it)






      parent reply	other threads:[~2000-01-19  6:36 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
1999-11-09 16:36     ` Kai Großjohann
1999-11-09 17:51     ` Rene H. Larsen
2000-01-19  6:36     ` David Maslen [this message]

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=87snzumuu1.fsf@iname.com \
    --to=david.maslen@iname.com \
    --cc=ding@gnus.org \
    /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).