DomainPOP: Understanding parsing notification failure emails the postmaster receives

DomainPOP: Understanding parsing notification failure emails the postmaster receives

These emails are generated as a result of your ISP having a catchall mailbox that MDaemon’s DomainPOP (Setup -> Server Setting -> DomainPOP) collects from. As your ISP accepts <anything>@yourdomain.com and routes it into this mailbox, when MDaemon collects this mail it finds no local users to distribute these emails to. It therefore passes it to the postmaster alias as a “parsing notification failure” so that they can manually be checked to see if this message was mis-addressed.

As these emails have already been accepted by your ISP you can’t reliably bounce them. However, you can tell MDaemon to route them differently and ultimately delete them as follows…

  1. In Setup -> Server Settings -> DomainPOP -> Processing, untick “Ignore unknown local addresses parsed from messages”:
  2. In Setup -> Server Settings -> Servers & Delivery -> Unknown Mail, only tick “…sent to the bad message folder”:



3. Optionally, in Setup -> Preferences -> Disk -> Disk Cleanup and Backup tick set and suitable value in “Delete bad queue files older than this many days” (this will mean there is no way to review these messages if they’ve been mis-addressed and are not reviewed before the number of days you specify):




Please note: Although this will prevent this email reaching the postmaster address, we would strongly recommend switching from DomainPOP mail collection to direct SMTP delivery so that sender mail servers deliver email directly to MDaemon. This ensures it is MDaemon that determines if the email being sent is addressed to a valid local address and it will actively refuse to accept those which aren’t. This means the sender would receive a bounce back and is therefore aware the email was not accepted and delivered to the intended recipient.

This article details how you can switch from DomainPOP to SMTP.
    • Related Articles

    • DomainPOP: Processing BCC Email

      BCC stands for Blind Carbon Copy. The BCC header in email is never created by the sender mail client because the message should not display that it was sent to anyone in the BCC field. The way that BCC mail is routed is via the SMTP envelope ...
    • DomainPOP / MultiPOP: Score incoming emails using Outbreak Protection

      If external email arrives via DomainPOP (or MultiPOP), then the Outbreak Protection feature can be applied in addition to the standard spam filter scoring once the email has been downloaded from the ISP’s mailbox. However, Outbreak Protection scoring ...
    • Switching from DomainPOP to SMTP delivery in MDaemon

      In order to migrate to a direct SMTP delivery configuration you need to initially ensure that the following 2 points apply to your network: The public IP address assigned by your ISP must be a static one (one that doesn’t change everytime you connect ...
    • DomainPOP: Configure how often MDaemon checks the ISP mailbox for new mail.

      MDaemon will check the ISP mailbox you’ve configured at Setup -> Server Settings -> DomainPOP every 5 minutes on a default installation. You can change this frequency via Setup -> Event Scheduling -> Mail Scheduling -> Mail Sending & Collecting, by ...
    • How to track an email through the MDaemon logs

      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 ...