Facebook
TwitterI have a Plesk VPS, hosting 2 Domains. I am looking to be able to access the Mail Logs, for a specific Mail Box. Any ideas on where such access Logs would be stored? Ideally, I would like to access them via the VPS Interface; just like you would for the the 'Log' entries.
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
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.
Thanks for your reply. I had downloaded the maillog file, from /var/log but the Logs only contain the activities from the present month. Are there settings I would need to change, in order for the maillog to contain the activities from beyond the present month?
I am not sure if this affects anything but there are similarly named files, such as 'maillog.processed' and 'maillog.processed.1.gz'.
I am not sure if this affects anything but there are similarly named files, such as 'maillog.processed' and 'maillog.processed.1.gz'.
Unpack the .gz files with for example
# gunzip maillog.processed.1.gz
Then look into them like
# less maillog.processed.1
and find older data in them. You can tell when the last entry in such a log file was made by checking the file date like
# ll maillog.processed.1.gz
The log retention time can be changed, if you want to collect more data:
Check /etc/logrotate.conf and /etc/logrotate.d/syslog and make the changes that you need there.
But it is not possible to restore older data that has long been rotated/deleted by a configuration change. Only for the future you can change the log rotation settings.
# gunzip maillog.processed.1.gz
Then look into them like
# less maillog.processed.1
and find older data in them. You can tell when the last entry in such a log file was made by checking the file date like
# ll maillog.processed.1.gz
The log retention time can be changed, if you want to collect more data:
Check /etc/logrotate.conf and /etc/logrotate.d/syslog and make the changes that you need there.
But it is not possible to restore older data that has long been rotated/deleted by a configuration change. Only for the future you can change the log rotation settings.
Similar threads
