Magnus Bodin proclaimed on mutt-users that:
>As of RFC 821 <http://rfc821.x42.com/> 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 which indeed is a valid and working
I don't know ... yeah ... RFC 821 (page 29) does say this ... but let's
see what goes on.
I sent out a mail to my catchall domain kcircle.com ->
'suresh test'@kcircle.com
See the headers ...
> Received: from cs2.hyd.office.juno.com (cs2.hyd.office.juno.com
> [208.238.62.3])
> by no9.superb.net (8.9.3/8.9.3) with ESMTP id BAA12436
> for <'suresh.test'@kcircle.com>; Mon, 10 Jul 2000 01:49:48 -0400
> (EDT)
Hmmm... my sendmail 8.8.x mailserver converts spaces to dots.
> Received: from lotus ([EMAIL PROTECTED]
> [208.238.62.74])
> by cs2.hyd.office.juno.com (8.8.6.Beta0/8.8.7/juno-1.1) with ESMTP id
> LAAAA21035 for <'suresh test'@kcircle.com>; Mon, 10 Jul 2000 11:19:46
> +0530 (IST)
My mua (I used pegasus mail for 'doze for this test) sends the space quite
ok. It is a sendmail issue and not a mutt issue I suppose.
Try looking at the headers of one such post (you'll likely find it in the
root mailbox, or it'll bounce to you)
You _can_ write something that's 100% rfc compliant and won't work
anywhere ;)
--
Suresh Ramasubramanian + [EMAIL PROTECTED]
Universe, n.:
The problem.
