Re: Mutt not following RFC821 strictly?

On Mon, Jul 10, 2000 at 03:37:11PM +0200, Magnus Bodin wrote: > On Mon, Jul 10, 2000 at 03:00:12PM +0200, Michael Tatge wrote: > > Magnus Bodin muttered: > > > > > > As of RFC 821 the local part of an e-mail address > > > can consist of other characters than a-z0-9 and sh

Re: Mutt not following RFC821 strictly?

On Mon, Jul 10, 2000 at 11:21:42AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: > On Mon, Jul 10, 2000 at 01:23:10AM -0400, Rich Lafferty wrote: > > On Mon, Jul 10, 2000 at 07:05:05AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: > > > > > > It seems though, that the mutt client does not supp

Re: Mutt not following RFC821 strictly?

On Mon, Jul 10, 2000 at 03:00:12PM +0200, Michael Tatge wrote: > Magnus Bodin muttered: > > > > As of RFC 821 the local part of an e-mail address > > can consist of other characters than a-z0-9 and should then be quoted (see > > local-part and quoted-string). > > > > It

Re: Mutt not following RFC821 strictly?

Magnus Bodin muttered: > > As of RFC 821 the local part of an e-mail address > can consist of other characters than a-z0-9 and should then be quoted (see > local-part and quoted-string). > > It seems though, that the mutt client does not support the use of an address > l

Re: Mutt not following RFC821 strictly?

On Mon, Jul 10, 2000 at 01:23:10AM -0400, Rich Lafferty wrote: > On Mon, Jul 10, 2000 at 07:05:05AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: > > > > As of RFC 821 the local part of an e-mail address > > can consist of other characters than a-z0-9 and should then be

Re: Mutt not following RFC821 strictly?

On Mon, Jul 10, 2000 at 07:05:05AM +0200, Magnus Bodin ([EMAIL PROTECTED]) wrote: > > As of RFC 821 the local part of an e-mail address > can consist of other characters than a-z0-9 and should then be quoted (see > local-part and quoted-string). > > It seems though, that

Re: Mutt not following RFC821 strictly?

Magnus Bodin proclaimed on mutt-users that: >' should be " according to the RFC. ah thanks ... so, I did three things ... 1. Talked raw smtp : rcpt to:"suresh test"@kcircle.com Result - Works. 2. Sent using mutt to "suresh test"@kcircle.com and then sent to <"suresh test"@kcircle.com> just i

Re: Mutt not following RFC821 strictly?

* Suresh Ramasubramanian <[EMAIL PROTECTED]>: > Magnus Bodin proclaimed on mutt-users that: > > >As of RFC 821 the local part of an e-mail address > >can consist of other characters than a-z0-9 and should then be quoted (see > >local-part and quoted-string). > > >It seem

Re: Mutt not following RFC821 strictly?

On Mon, Jul 10, 2000 at 11:30:14AM +0530, Suresh Ramasubramanian wrote: > Magnus Bodin proclaimed on mutt-users that: > > >As of RFC 821 the local part of an e-mail address > >can consist of other characters than a-z0-9 and should then be quoted (see > >local-part and quo

Re: Mutt not following RFC821 strictly?

Magnus Bodin proclaimed on mutt-users that: >As of RFC 821 the local part of an e-mail address >can consist of other characters than a-z0-9 and should then be quoted (see >local-part and quoted-string). >It seems though, that the mutt client does not support the use of a

Mutt not following RFC821 strictly?

As of RFC 821 the local part of an e-mail address can consist of other characters than a-z0-9 and should then be quoted (see local-part and quoted-string). It seems though, that the mutt client does not support the use of an address like "address with spaces"@x42.com whi