[NTLUG:Discuss] Mail Problem
Bobby Sanders
ssanders at vzinet.com
Fri Nov 9 00:00:24 CST 2001
--On Thu, 8 Nov 2001 16:27:54 -0600 (CST), Richard Cobbe <cobbe at airmail.net> said:
RC> Lo, on Thursday, November 8, Bobby Sanders did write:
>> --On Wed, 07 Nov 2001 15:52:11 "Val W. Harris"
>> <vwharris at airmail.net> said:
>>
VWH> Bobby Sanders wrote:
>> VWH/BS> I use fetchmail to retrieve mail from my ISP (POP3) and
>> VM VWH/BS> 6.75 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs
>> Lucid VWH/BS> for my mail agent.
>>
>> VWH/BS> Suddenly all of my incoming messages display a "^M"
>> VWH/BS> appended to each line of the messages. Very annoying.
>> VWH/BS> .....
....
>> I finally gave up and rebooted. Everything worked fine then.
,,
RC> Since VM runs inside emacs, there are far more configuration
RC> options than we mere mortals can be expected to know.
Ain't it th' truth. Ain't it th' truth. (With apologizes to the
Cowardly Lion.)
RC> (As you can tell from my headers, I use VM 6.72 under XEmacs
RC> 21.1.10 myself.) I've not actually seen this behavior, but I
RC> think that XEmacs may somehow have gotten itself into a mode
RC> where the buffer contained CR/LF pairs but it expected only
But the CR/LF were only in the new mail received from my POP
server. Also, all of the messages showed a size of 0 in the header
list, but the message bodies were there and apparently intact.
RC> LFs---I know that FSF Emacs 20 tries to Do The Right Thing here.
RC> Unfortunately, I'm not sufficiently familiar with this
RC> particular part of emacs to know
RC> Did you try just killing and restarting your Emacs process
RC> before you rebooted? Did that help?
NO. Dang it! I wish I had. In fact, I wish I had tried
exiting/starting VM, XEmacs, XWindows and then rebooting, in that
order. I would really like to have some idea of which one of these
programs went crazy. I just got too focused on trying to complete the
immediate project. Oh well, next time - and with my clumsy fingers,
there will be a next time.
Thanks for the input
Bobby
More information about the Discuss
mailing list