On 21 May 2015, at 17:36, Benny Pedersen wrote:
On May 21, 2015 11:08:28 PM "Bill Cole"
<sausers-20150...@billmail.scconsult.com> wrote:
On 21 May 2015, at 14:42, Benny Pedersen wrote:
> Note that plus addressing, users can only subscribe, is 2 + valid
in
> mailto: ?
Sure, why not? See RFC's 821, 822, 2821, 2822, 5321, and 5322 :)
There is nothing special about '+' in an email address in SMTP or in
the
email data format. It is only special to some delivery agents that
may
be configured to treat it specially.
Here my mail client replaced + with a space char so ended to a invalid
addr, why would anyone like to reply to 3rd party spammers to
unsubscribe, well nice to see that my mail client does not support
this even if its a bug in rfc
I misunderstood your original question.
The bug is in your client and to a lesser degree in Google's
construction of the 'mailto:' URIs in the various List-* headers. For
best interoperability they should be encoding '+' as '%2B' because it is
a widespread, longstanding, and well-known bug in interpreters of
mailto: URIs that they (incorrectly) decode '+' to ' ' as if they are
decoding HTTP form submission data.
