Atomicorp

Hmmm... a very quick and dirty solution would be to set pop-before relay to 1 min or something?

Which OS are you using?

Hang on (sorry -- I should edit my posts rather than create new ones)....

Spamdyke does not support pop-before-relay.

THAT's what's different between your setup and mine.

Just switch it off.

Problem will be solved.

Faris.

That's true, spamdyke doesn't support pop before relay. Stupid question, how do I set it off?

florinc wrote:That's true, spamdyke doesn't support pop before relay. Stupid question, how do I set it off?

AH, I feel so stupid. It really wasn't the time to spend so many hours on this issue. I found the option, and ofcourse, it's working.

Just to save a bit of my honor

I replaced rblsmtpd with a bash scripts, that invokes spamdyke. This way I can still disable/enable rblsmtpd from the admin interface.

Thanks for the fast solution faris!

That's excellent news. I was being dim by not realising what the problem was much sooner, especially since pop before relay (aka pop before smtp) was the only thing I had highlighted as being a potential drawback for using spamdyke.

Faris.

Hello All,

I plunged in, and decided to give spamdyke a go yesterday.
well right out of the box, nice and easy.

Ran well through the night dumped plenty of mail with no RDNS.
I then decided to work with graylist while i sat and monitored.
Got that working, with minor issues (mainly permissions)

I then did a few tests from an alternate server, to make sure it was in fact working on a per domain basis.

This is when I found that all mail sent to a certain domain were simply skipped by spamdyke.

I have recompiled spamdyke, started from scratch and still the same issue?

Anybody have some suggestions?

I have been checking the logs and i found the following from the time i implemented graylisting:

Dec 11 11:23:31 server spamdyke[822]: DENIED_GRAYLISTED from: mark.brindley@trigger.co.za to: mark@oakfield.co.za origin_ip: 64.182.94.229 origin_rdns: back.trigger.co.za auth: (unknown)

I now receive mail from that server and email address but spamdyke skips it completely.

spamassassin does tho ..

Dec 11 16:11:50 server spamd[2306]: spamd: using default config for mark@2large.co.za: /var/qmail/mailnames/2large.co.za/mark/user_prefs
Dec 11 16:11:50 server spamd[2306]: spamd: processing message <000901c83bff$c0c22f70$42468e50$@brindley@trigger.co.za> for mark@2large.co.za:110
Dec 11 16:11:51 server spamd[2306]: spamd: clean message (0.4/8.0) for mark@2large.co.za:110 in 1.4 seconds, 4956 bytes.

[edit] Sorry... I didn't see the end of your message....

Check the IP isn't in a spamdyke whitelist?

Faris.

Hello Faris,

the sending server 64.182.94.229 is not in the whitelist
The ADSL IP range I am sending from on LAN is.

I removed all entries from the file /var/qmail/spamdyke/whitelist_ip
Restart ...

Still the same thing.

If i send from the same LAN, directly to the server from that domain it logs just fine.

I have also just noticed that IP's in the file /var/qmail/spamdyke/blacklist_ip are also not been denied with msg

My conf looks like this.
The only things i see in the logs are

DENIED_OTHER
DENIED_RDNS_MISSING
DENIED_SENDER_NO_MX

--------------------------
log-level=3
local-domains-file=/var/qmail/control/rcpthosts
max-recipients=50
idle-timeout-secs=300
greeting-delay-secs = 3
#sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
reject-missing-sender-mx
reject-empty-rdns
#rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
policy-url=http://www.2large.co.za/policy
hostname=server.kbpsaccess.co.za

----------------------------------------

Trying my little heart out!
One domain been SMASHED by 78000 spam mails

Very strange!

Have you tried using the config test thing in the command line? That might give some clues. I might all be down to more permissions things.

Also you will probably get better help from the spamdyke mailing list/forum than from little old me. I'm just guessing at things here

Faris.

Hello faris,


Thanks for the efforts!

What permissions do you have set?

Well, I have all my config files in /etc so for example /etc/spamdyke/spamdyke.conf and are owned by root:root like all the others. Perms are 644 on the files.

For my graylist directory structure, I have them in /var/qmail/graylist owned by qmaild:root

BUT....there's a new version out. 3.1.2. It mentions that it fixes a bug where the sending SMTP server sends data too fast and spamdyke does not log the connection though it does process it.

So just in case this is the problem (ignore the no blacklist for now) I would update to 3.1.2 to see if your connection gets logged.

Also have a look in the tests directory that you'll find under spamdyke-3.1.1 (or 3.1.2 now) which seems to have a load of test scripts. The documentation folder may have some additional info on those.

Faris.

Hiya Faris.

Out of the blue my CPU is running 100%
I had one my guys do some updates on the server, killed a load of stuff!
Now I am trying to fix

Can you confirm your perms & owner for the following files in /var/qmail/bin/

qmail-queue

Can you also show /usr/local/bin/

spamdyke

qmail-queue is qmailq:qmail

The spamdyke binary in /usr/local/bin/ is root:root

I would downgrade to an earlier release of spamdyke. I'm not sure the very latest one is 100% and it might be that this is what's causing your problem.

Also check what you have in resolv.conf and make sure 127.0.0.1 is the first one listed. It may be that DNS lookups are failing. Check to make sure named is running. Also try it without 127.0.0.1 in resolv.conf

Faris.

Hi Scott!

Awsome man, perms were all correct!
Downgrading to 3.1.0 did the job.
Running like a dream now ~