*To:* qmailtoaster-list@qmailtoaster.com
*Subject:* [qmailtoaster] Re: RE; spamdyke ?
On 05/02/2011 12:51 PM, Joel Eddy wrote:
I'm seeing this in my smtp logs on this account. I've tried to find the
answer but so far no luck. Has anyone else had this problem?
2011-05-02 13:52:06.345475500.s
@qmailtoaster.com
Subject: [qmailtoaster] Re: RE; spamdyke ?
It could be that scanning is taking longer than your timeout setting.
What value do you have for idle-timeout-secs in spamdyke.conf?
FWIW, I have 180 presently.
It could also be that scanning is taking longer than the sending server
is willing
*Subject:* [qmailtoaster] Re: RE; spamdyke ?
It could be that scanning is taking longer than your timeout setting.
What value do you have for idle-timeout-secs in spamdyke.conf?
FWIW, I have 180 presently.
It could also be that scanning is taking longer than the sending server
is willing to wait
NOTE: I have seen this behavior when SSL connections are made and there
is not enough RAM allocated for the SSL libraries. The result is that
the SMTP (actually the qmail-smtp service) hangs (bad memory alloc), and
so never returns
On 5/3/2011 11:14 AM, Eric Shubert wrote:
This looks hunky
The fix is to edit your SSL-capable run files in /var/qmail/supervise/*/run
Depending on what you've got configured, you may need to modify:
*smtp*, *submission*, *smtp-ssl*, *pop-ssl*, *imap-ssl*.
The last line in each of those run files is the exec that spawns the
actual program -- and the
On 05/02/2011 12:51 PM, Joel Eddy wrote:
I'm seeing this in my smtp logs on this account. I've tried to find the
answer but so far no luck. Has anyone else had this problem?
2011-05-02 13:52:06.345475500.s:@40004dbef6ef166a7104 spamdyke[31592]:
TIMEOUT from: lcgrap...@iowatelecom.net to:
: Monday, May 02, 2011 3:35 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] Re: RE; spamdyke ?
On 05/02/2011 12:51 PM, Joel Eddy wrote:
I'm seeing this in my smtp logs on this account. I've tried to find the
answer but so far no luck. Has anyone else had this problem?
2011-05-02
On 11/19/2010 08:51 AM, Tony White wrote:
Hi folks,
Thank you for making me use spamdyke it certainly does
make a huge difference.
I have tried to use the blacklists but they do not appear to
work.
I have blocked an entire domain in blacklist_recipients
and whitelisted those to accept in that
Hi Eric,
What is happening is the mail server is seeing addresses for
one or more of my domains that are not real and accepting
delivery of them.
My thought was to deny all then only accept valid addresses.
Also seeing From Address ie @rolex.com and this is in the
blacklist but not being
The simplest way to deal with this is to change your catchall
configuration. In qmailadmin (web app), user accounts, click either the
set catchall deleted or set catchall bounce link. That controls what
happens to email for which there's no user account.
Deleting misaddressed email is not
10 matches
Mail list logo
