On a default installation, MDaemon will log all mail and user activity into the \MDaemon\Logs\ directory and each log file will have that days date in it’s filename in the form MDaemon-YYYY-MM-DD-<servicename>.log.
Prior to tracking an email through the logs, it’s important to check that you have the relevant logging enabled.
The below details the order in which you would track an email and the scenario. Log files can be opened in a text editor such as Notepad or Notepad++.
Incoming External email which arrives via direct SMTP:
1. MDaemon-YYYY-MM-DD-SMTP(in).log
This will show the email being accepted from the sending mail server.
2. MDaemon-YYYY-MM-DD-Routing.log
The first entry in this log will show the email being passed from the inbound queue to the local queue.
3. MDaemon-YYYY-MM-DD-AntiVirus.log
This indicates if the email was flagged as virus infected (Security -> AntiVirus).
4. MDaemon-YYYY-MM-DD-AntiSpam.log
This indicates if the email was scored as spam (Security -> Spam Filter).
5. MDaemon-YYYY-MM-DD-ContentFilter.log
This indicates if the email was flagged by a Content Filter Rule (Security -> Content Filter).
6. MDaemon-YYYY-MM-DD-Routing.log
The second entry in this log will show the email being passed from the local queue to the user’s mailbox (assuming that steps 3, 4, or 5 haven’t stopped the processing of the message).
Incoming external email which arrives via DomainPOP (Setup -> DomainPOP):
1. MDaemon-YYYY-MM-DD-DomainPOP.log
This will show the email being retrieved from the ISP’s mailbox.
2. MDaemon-YYYY-MM-DD-Routing.log
The first entry in this log will show the email being passed from the inbound queue to the local queue.
3. MDaemon-YYYY-MM-DD-AntiVirus.log
This indicates if the email was flagged as virus infected (Security -> AntiVirus).
4. MDaemon-YYYY-MM-DD-AntiSpam.log
This indicates if the email was scored as spam (Security -> Spam Filter).
5. MDaemon-YYYY-MM-DD-ContentFilter.log
This indicates if the email was flagged by a Content Filter Rule (Security -> Content Filter).
6. MDaemon-YYYY-MM-DD-Routing.log
The second entry in this log will show the email being passed from the local queue to the user’s mailbox (assuming that steps 3, 4, or 5 haven’t stopped the processing of the message).
Email sent from a local MDaemon account to a remote email address:
1. MDaemon-YYYY-MM-DD-SMTP(in).log
This will show the email being accepted from the local email client.
2. MDaemon-YYYY-MM-DD-Routing.log
This will show the email being passed from the inbound queue to the remote queue.
3. MDaemon-YYYY-MM-DD-AntiVirus.log
This indicates if the email was flagged as virus infected (Security -> AntiVirus).
4. MDaemon-YYYY-MM-DD-AntiSpam.log
This indicates if the email was scored as spam, but only if email from local users is being spam scored at Security -> Spam Filter.
5. MDaemon-YYYY-MM-DD-ContentFilter.log
This indicates if the email was flagged by a Content Filter Rule (Security -> Content Filter).
6. MDaemon-YYYY-MM-DD-SMTP(out).log
This will show the email being sent from MDaemon to the remote mail server which handles mail for this external domain name.
Email sent from an MDaemon local account to another local account:
1. MDaemon-YYYY-MM-DD-SMTP(in).log
This will show the email being accepted from the local email client.
2. MDaemon-YYYY-MM-DD-Routing.log
The first entry in this log will show the email being passed from the inbound queue to the local queue.
3. MDaemon-YYYY-MM-DD-AntiVirus.log
This indicates if the email was flagged as virus infected (Security -> AntiVirus).
4. MDaemon-YYYY-MM-DD-AntiSpam.log
This indicates if the email was scored as spam, but only if email from local users is being spam scored at Security -> Spam Filter.
5. MDaemon-YYYY-MM-DD-ContentFilter.log
This indicates if the email was flagged by a Content Filter Rule (Security -> Content Filter).
6. MDaemon-YYYY-MM-DD-Routing.log
The second entry in this log will show the email being passed from the local queue to the user’s mailbox (assuming that steps 3, 4, or 5 haven’t stopped the processing of the message).
Possible issues to note:
If an email appears to disappear when tracking it through the logs a common cause of this is a third party antivirus program performing real-time or scheduled scanning on the MDaemon folder and removing the email from MDaemon. For this reason, it is important that any third party antivirus program is set to exclude the entire MDaemon folder and any SMTP, POP or IMAP scanning it performs is also disabled. Failure to do so may cause problems like disappearing email, corrupted email or cause email to get stuck in MDaemon’s mail queues.
