Jon,

Typically, it's the difference between UNIX and Windows. If you edited a
conf file in Windows and used binary mode to transfer it to the SA machine,
the ^M would be in the conf file. There are a couple of ways around it. The
first is to transfer in ASCII mode, the second is to run dos2unix on the
file and the third is to edit the conf file in vi on the SA machine. If you
choose the third option, open the file in vi and you should see ^M at the
end of each line. 
Type
:1,$ s/^v^m// what you will actually see is :1,$ s/^M//
and press enter. The ^V won't actually appear, but it will force vi to look
for ^M vice the ^ character followed by M.

Hope this helps.

Giff

-----Original Message-----
From: Jon D. Slater [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 27, 2006 1:01 PM
To: users@spamassassin.apache.org
Subject: prefs directories with "^M" in the name

Hi all,
 
I’ve read the FAQ and still don’t find this issue.
 
Configuration:
Spamassassin 3.0.4
OS:  Fedora Core 4
SPAMDOPTIONS=”-d -u spamassassin -x  -P
--virtual-config-dir=/usr/share/spamassassin/%u.prefs"
 
So, my prefs files are all being stored in /usr/share/spamassassin
 
Everything seems to be running fine.
 
When I cd into /usr/share/spamassassin and do an ‘ls’, I see:
 
members.prefs
members.prefs^M   (control M, not “^” and “M”)
 
If I remove the “^M” version, after some period of time, they come back.
 
What is creating these? And how do I fix it?
 
Thanks!
 
Jon




Reply via email to