Gnus development mailing list
 help / color / mirror / Atom feed
From: "Bjørn Mork" <bmork@dod.no>
To: ding@gnus.org
Subject: Re: Disposition-Notification-To acks
Date: Fri, 16 Nov 2007 11:03:35 +0100	[thread overview]
Message-ID: <87abpejymg.fsf@obelix.mork.no> (raw)
In-Reply-To: <87hcjmmzfi.fsf@newton.gmurray.org.uk>

Graham Murray <graham@gmurray.org.uk> writes:
> jidanni@jidanni.org writes:
>
>> Gentlemen, the Taiwan Power Company has turned off my e-bill account
>> because gnus doesn't acknowledge the Disposition-Notification-To
>> headers they send.
>
> Is it gnus' job to respond to them? I believe that it is the
> responsibility of the MTA making the local delivery (ie the one from
> which gnus fetches mail) to respond to Disposition-Notification-To
> headers. 

Nope, it's a MUA thing.  Quote from RFC3798:

<quote>
2.1.  The Disposition-Notification-To Header

   A request for the receiving user agent to issue message disposition
   notifications is made by placing a Disposition-Notification-To header
   into the message.
</quote>

However, the bug in this case is cleary on the Taiwan Power Company
side, since the quoted section continues

<quote>
   The presence of a Disposition-Notification-To header in a message is
   merely a request for an MDN.  The recipients' user agents are always
   free to silently ignore such a request.
</quote>

So Gnus is behaving correct by default.



Bjørn
-- 
Don't you realise that you think that I was the Pope in a previous
life




  reply	other threads:[~2007-11-16 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  1:13 jidanni
2007-11-16  7:17 ` Graham Murray
2007-11-16 10:03   ` Bjørn Mork [this message]
2007-11-17 12:11 ` Reiner Steib
2007-11-17 14:23 ` Miles Bader
2007-11-17 16:06   ` Reiner Steib
2007-11-17 18:55   ` jidanni

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=87abpejymg.fsf@obelix.mork.no \
    --to=bmork@dod.no \
    --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).