Re: [Last-Call] Last Call: <draft-billon-expires-06.txt> (Updated Use of the Expires Message Header Field) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It appears that George Michaelson  <ggm@xxxxxxxxxxxx> said:
>If a message had an EXPIRES-BY header, semantically past it's "due"
>date, and an intermediate store-and-forward SMTP MTA decided to look
>in its queue, would it be "wrong" for it to return to sender rather
>than deliver? If the header could be shown to be origin specified, and
>not arbitrarily added?

That seems wrong to me for too many reasons to count.

We have been trying for ages to get rid relays that inspect and modify
relayed messages. MIME down-encoding is I hope gone, and the only
plausible excuse these days is malware scanning.

Also, there is no reason to assume that the origin's intentions
were benign when it added the header, and I do not want to do
any second guessing.  The next rev of the draft will take out
all the advice about deleting messages automatically.

R's,
John

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux