From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: gnus is ruining my chances of a long line base64 romance
Date: Fri, 20 May 2011 19:34:20 +0100 [thread overview]
Message-ID: <87oc2x8bmb.fsf@ucl.ac.uk> (raw)
In-Reply-To: <gk1uztmlcb.fsf@news.eternal-september.org> (Richard Riley's message of "Fri, 20 May 2011 17:40:36 +0200")
Richard Riley <rileyrg@googlemail.com> writes:
> asjo@koldfront.dk (Adam Sjøgren) writes:
>
>> On Fri, 20 May 2011 00:28:16 +0800, jidanni@jidanni.org wrote:
>>
>>> And gnus cannot deal with my potential dates mail.
>>
>> The email you included has line lengths of 800 and 190 chars every other
>> line of encoded content.
>>
>> RFC 2045 specifies a maximum line length of MIME Content-Transfer-Encoding:
>> base64 of 76 chars.
>>
>> Please fix it.
>>
>> Best regards,
>
> Since the chance of thousands of sites that send email even being aware
> of "RFC 2045" it seems more intelligent and professional to cover the
> likely scenario that its not met .. in the client.
But if you are going to use a specific MIME encoding, doesn't it make
sense to follow the rules...? Encouraging bad behaviour is not
necessarily the best option.
In any case, the response from OP was rather rude, IMO.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.18
next prev parent reply other threads:[~2011-05-20 18:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 16:28 jidanni
2011-05-19 22:27 ` Adam Sjøgren
2011-05-20 15:40 ` Richard Riley
2011-05-20 18:34 ` Eric S Fraga [this message]
2011-05-20 0:01 ` Katsumi Yamaoka
2011-05-20 0:57 ` jidanni
2011-05-20 2:37 ` Katsumi Yamaoka
2011-05-20 14:47 ` Ted Zlatanov
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=87oc2x8bmb.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).