regenerated it now and everything seems to work perfectly, thx for all
input...
On Mon, Nov 9, 2009 at 6:01 AM, Eric Shubert e...@shubes.net wrote:
You've whitelisted locahost in spamdyke, so spamdyke's allowing it. CHKUSER
is rejecting this one. What's in your tcp.smtp file? (and did you
You've whitelisted locahost in spamdyke, so spamdyke's allowing it.
CHKUSER is rejecting this one. What's in your tcp.smtp file? (and did
you regenerate the cdb after changing it?)
Kjetil Paulsen wrote:
Guess so, here are the log entry from trying to send from squirrelmail:
Guess so, here are the log entry from trying to send from squirrelmail:
@40004af52e171ed800f4 tcpserver: status: 1/100
@40004af52e171edc332c tcpserver: pid 5743 from 127.0.0.1
@40004af52e171edc3714 tcpserver: ok 5743 blue:127.0.0.1:25 :127.0.0.1:
:32941
@40004af52e171f093e6c
Had the same problem a year ago and then it was spamdyke... however, turned
that off then... I'll try recordio and see if that can give some hints,
thx!
/K
On Tue, Nov 3, 2009 at 4:11 PM, Eric Shubert e...@shubes.net wrote:
If you're using spamdyke, turn on detailed logging. It'll show you the
I don't know what problem you might have had with spamdyke, but it's
very solid now. I'd try it again. The detailed logging is a breeze
compared to recordio. (It's extremely effective with spam too!)
Kjetil Paulsen wrote:
Had the same problem a year ago and then it was spamdyke... however,
If you're using spamdyke, turn on detailed logging. It'll show you the
details of the incoming smtp session. It's slick because each session
gets logged in its own file.
Otherwise, you can use recordio, which logs all details into the smtp
log. Search the list archives for how to set that up.
