• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

yet another qmail/spamdyke post

S

StigJ

Guest
Hello my fellow plesk users!
First of all, I'm not a real linuxwiz but ever since I first installed spamdyke
the qmail seems to be abit "unstable", and sometimes the "mail service" just stop working completely, but a server reboot usually fix that.

BUT now it is dead... and i cant seem to get it started again nomatter what i do, I also noticed that
noting ever gets logged (not even before spamdyke) in the maillog and whenever i enable spamdyke in the smtp.conf plesk says that smtp is not running, and i cant start it untill i remove the two spamdyke entries from the smtp.conf file.

And I don't know if this is related, but I can't get mailman to run either, with or without spamdyke, it just says that "smtp service is not running".

Please help


Stigge
 
It is normal for Plesk to report that the smtp service is down when you have spamdyke installed. It isn't a problem, just ignore it.

As for the rest of your problems....try asking on the spamdyke mailing list, as you'll get a better response there. I've not come accross any issues with spamdyke ever, except when it is incorrectly configured. So it might be as simple as a line in your config that needs looking at. Spamdyke includes comprehensive test scripts to help you here:

http://www.spamdyke.org/documentation/README.html#CONFIGURATION_TEST

Remember that the maillog is at /usr/local/psa/maillog and not /var/log/maillog

If you get nothing logged then it is possible that syslogd isn't being run at startup (try ntsysv to see if it is).
 
Thank you Faris... this helped alot :) the world of Linux is mostly a jungle for me, and you just handed me a knife.
You were right, the syslog was not running (/me bangs his head against the keyboard)
 
Back
Top