Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: auth-source patch for secure logging
Date: Thu, 16 Jul 2009 11:21:43 -0500	[thread overview]
Message-ID: <873a8wppig.fsf@lifelogs.com> (raw)
In-Reply-To: <33120.130.55.118.19.1247759723.squirrel@webmail.lanl.gov>

On Thu, 16 Jul 2009 08:55:23 -0700 (PDT) "Davis Herring" <herring@lanl.gov> wrote: 

TZ> Attached is a patch to auth-source.el that:
>> 
>> Of course, the actual patch file is optional on the first message.

DH> In fact, the grammar in RFC 2045 explicitly forbids a MIME boundary within
DH> any message whose body contains the words "attached", "attachment", or
DH> "attaching" (in any case) on a line that does not begin with a >, so as to
DH> avoid confusing pre-MIME MTAs that would mistake it for the beginning of a
DH> new, non-textual message in the DECnet style (much like the common problem
DH> of ">From" in mbox files).  Some modern MUAs can be configured to ignore
DH> this restriction since it's so rarely relevant now, but very few users
DH> know about those (non-compliant) features.

DH> So it's really not your fault.

DH> Davis

DH> PS - I hear that Google is actively flouting the RFC with their GMail
DH> service by explicitly asking the user if they meant to attach files when
DH> they request to send a compliant message.  Fortunately it's still an
DH> experimental ("Labs") feature, and the IETF has been notified.

DH> PPS - If replying to this message, be sure to use the > quotation style if
DH> you desire to attach any files; the body of this message (and this very
DH> postpostscript) include the words called out in the RFC.

This made my day, thanks Davis.

Ted




  reply	other threads:[~2009-07-16 16:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 14:23 Ted Zlatanov
2009-07-16 14:33 ` Ted Zlatanov
2009-07-16 15:55   ` Davis Herring
2009-07-16 16:21     ` Ted Zlatanov [this message]
2009-07-16 15:32 ` Chong Yidong
2009-07-16 16:15   ` Ted Zlatanov
2009-07-16 18:09     ` Ted Zlatanov
2009-07-17 17:31   ` Glenn Morris
2009-07-17 17:53   ` Ted Zlatanov
2009-07-17 18:01     ` Glenn Morris
2009-07-17 18:09       ` Ted Zlatanov
2009-07-17 18:35         ` Chong Yidong
2009-07-18 17:21           ` Chong Yidong
2009-07-17 19:42         ` Sven Joachim

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=873a8wppig.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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).