John Harmon wrote:
Jason 'XenoPhage' Frisvold wrote:
On Wed, 30 Apr 2008 13:40:31 -0600, John Harmon <[EMAIL PROTECTED]>
wrote:
Thanks for the reply. I will test that out along with the other
gentleman's suggestion on clam (for the reboot issue); however, I don't
know how to disable simscan (doesn't appear to be a normal /etc/init.d
service from what I can see). Can you tell me how?
Sure.. In your tcp.smtp file, you should have something like this :
:allow,QMAILQUEUE="/var/qmail/bin/simscan"
Change that line to this :
:allow
And then re-compile the tcp.smtp.cdb file like this :
tcprules tcp.smtp.cdb tcp.smtp.tmp < tcp.smtp
Thanks
John
Just a thought before testing all of this. How does a client talk to
the server, and through what code paths, that varies from that of a
browser? (again, as the broswer always works)???
Thanks,
John
OK. Test complete. Setting the /home/vpopmail/etc/tcp.smtp from this:
:allow,QMAILQUEUE="/var/qmail/bin/simscan"
to this:
:allow
Instantly allowed me to send the email from the client (while
experiencing the problem). I can't keep it this way, however, due to it
disabling clam and apparently spamassassin from doing their jobs.
What are the things I need to check in order to make sure clamav and/or
spamassassin is healthy? I don't really see much in the log files. Any
continued help you can provide me to help resolve the issue now that it
has been narrowed down would be much appreciated.
John
