I've had twice the following issue with spamdyke : no reference
to a message is found in /var/log/mail.info but i can find it in
qmail logs... Dunno whether it's syslog losing log lines or a bug
in spamdyke ? (there is no way for the message to avoid spamdyke
on this server)
have a nice day !
Hi,
I've been using spamdyke for about 2 weeks now, and I'm quite satisfied
with the results. Thanks for this great tool.
As the subject states, I'm running a Plesk 8.1 based system. Today I
upgraded from the 2.6.3 version, to the 3.1.0.
The good news is: I got everything working so far.
But
A few questions:
What version of spamdyke are you using? Older versions didn't log
every message, especially if the connection was whitelisted. Newer
versions should log everything.
Also, how busy is your server? syslogd will drop messages if the
server is overloaded; I
I have two server. One I install the latest spamdyke v3.1.1, let's call this
server A and the other server B.
Both
have spamdyke v3.1.1, using plesk. But when I send email via webmail
from server A to the server B email, some how the email cannot be
delivered.
When I check server B the log shows
I would like to report that v3.1.0 also suffer from the same issue as described
below.
So now I am back to v3.0.1, I think many mail will be missing if I continue to
test.
I believei it should be able to resolve quickly.
- Original Message
From: david boh [EMAIL PROTECTED]
To:
What version of spamdyke are you using? Older versions didn't log
every message, especially if the connection was whitelisted. Newer
versions should log everything.
3.1.1 installed this morning in place of 3.1.0
Also, how busy is your server? syslogd will drop messages if
On Tuesday 13 November 2007 15:42, Seb wrote:
What version of spamdyke are you using? Older versions didn't log
every message, especially if the connection was whitelisted. Newer
versions should log everything.
3.1.1 installed this morning in place of 3.1.0
Also, how busy is
Plesk is such a queer duck. I like its control panel but it sure does
some screwy things to the system configuration.
I see something in your spamdyke configuration file that could be
causing the SMTP AUTH problem. You have the following line commented out:
Can you send more information about your setup? Could you send the
contents of your /etc/xinetd.d/smtp_psa file and your spamdyke
configuration file (if you have one)?
-- Sam Clippinger
david boh wrote:
I would like to report that v3.1.0 also suffer from the same issue as
described below.
Wow -- 730K daily connections is a pretty busy server. What do your
load and CPU utilization numbers look like? Does syslog log to files on
the local machine or are you using a network syslog server? Most
importantly, are you seeing any other missing messages or is this issue
specific to
Hi Sam,
thank you for your very detailed answer. In fact you were right about
relaylock. I removed it during my tests and forgot to add it during the
config-test. Anyway, I gave it another shot, and I'm still stuck with
the same problem. I used loglevel 4 and got a warning saying:
WARNING:
I've been running SD3.1.1 for a little over an hour and have been
watching my smtpd logs and noticed something I didn't expect to happen
with graylisting.
I asked my wife to send me an email while I watched the logs. I saw
it connect, get the graylist message, then saw it connect to one of my
relaylock uses the TCPREMOTEIP environment variable (set by tcpserver or
tcp_env) to determine the IP address of the remote server. When
spamdyke runs its configuration tests, it sets TCPREMOTEIP to 127.0.0.1.
relaylock doesn't seem to offer SMTP AUTH to that IP address.
Try this -- set
Sure my friend.
Both server has the same smtp_psa and configure ( both server have 3.0.1 and
duplicate/mirror setting)
SMTP_PSA
{
socket_type = stream
protocol= tcp
wait= no
disable = no
user= root
14 matches
Mail list logo
