• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Qmail: No traffic or comon log

V

VIB-host

Guest
Hi someone please help me out here

I have Plesk 7.5.3 Up to date (Writen time) whit the following components from 4psa.com:

  • 4PSA Clean Server
  • 4PSA Client Backup
  • 4PSA Spam Guardian

This is running on a FreeBSD 4.9-RELEASE

The rest is standart setup.

The problem is now, that i can't find any kind of lock files for Qmail nor inside plesk see any mail traffic statistic.

I would really like to be able to see the Qmail log file, so I can set up spamtraps.

And It would be nice to see how much traffik the difrent clients generate by mail traffik.

Anybody who know what to do?

PS: Don't forget to tell me the answer like a 2 year old kid :)
 
The given file came out whit this:

mail.* -/usr/local/psa/var/log/maillog
*.err;kern.debug;auth.notice;mail.crit /dev/console
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
security.* /var/log/security
auth.info;authpriv.info /var/log/auth.log
#mail.info /var/log/maillog
lpr.info /var/log/lpd-errs
cron.* /var/log/cron
*.emerg *
# uncomment this to log all writes to /dev/console to /var/log/console.log
#console.info /var/log/console.log
# uncomment this to enable logging of all log messages to /var/log/all.log
# touch /var/log/all.log and chmod it to mode 600 before it will work
#*.* /var/log/all.log
# uncomment this to enable logging to a remote loghost named loghost
#*.* @loghost
# uncomment these if you're running inn
# news.crit /var/log/news/news.crit
# news.err /var/log/news/news.err
# news.notice /var/log/news/news.notice
!startslip
*.* /var/log/slip.log
!ppp
*.* /var/log/ppp.log


However the /usr/local/psa/var/log/maillog file is emty
 
line with this:
mail.* -/usr/local/psa/var/log/maillog
need change to this:
mail.* /usr/local/psa/var/log/maillog
 
Originally posted by Flintus
line with this:
mail.* -/usr/local/psa/var/log/maillog
need change to this:
mail.* /usr/local/psa/var/log/maillog

Thanks, I had that in mind, but I like to be sure before doing something I'm not use to mees whit. Then the last question, how do I reload/restart/reload /etc/syslog.conf (syslogd) whitout rebooting the system. and If you know what is the common command to reload objects insite /etc/ I will be happy
 
under root permission
run this command:
killall -1 syslogd
 
Back
Top