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 hanging on color

This is curious enough to investigate... * Suresh Ramasubramanian <[EMAIL PROTECTED]>: > Wari Wahab proclaimed on mutt-users that: > > ># SCREAMING TEXT (often used in spam) > >color body brightyellow default" \([-A-Z']{2,}[ ,]*\)+" > > Maybe your terminal doesn't understand a color calle

Re: suggestion #2

* fman <[EMAIL PROTECTED]>: > Is there plans to make enable mutt to read the news from a news server? I don't know, but I doubt it. See some of the nntp patches though: http://www.mutt.org/links.html#patch

Re: Sender rejected

* Dennis Robertson <[EMAIL PROTECTED]>: > > I can't seem to get anything to work first time with mutt. I installed > gnupg, copied the gpg.rc file to ~/ and tried to send a signed message to > myself. copy/paste gpg.rc into your .muttrc david -- One's not half two. -- e.e.cummings

Re: startup annoyance with 1.2.2i

* David Porter <[EMAIL PROTECTED]>: > > I compiled ver. 1.2.2i and now whenever I start mutt a "Press any key to > continue..." prompt appears. I figured out the problem. The system Muttrc contained bad options (pop3, which I didn't compile in). mutt -n didn't

startup annoyance with 1.2.2i

I compiled ver. 1.2.2i and now whenever I start mutt a "Press any key to continue..." prompt appears. After pressing the key, it displays my inbox. I don't know why this is. Note that in my .muttrc I have "unset wait_key". My only idea is that this has something to do with reading my .muttrc, tho