Spam and Quarantine FAQs
How do I stop sending daily Quarantine Digests?
Use the Send Daily Quarantine Digest Emails at Config > Email > Quarantine.
Why are users not receiving a Quarantine Daily Digest?
Verify your email configuration at Config > Email - make sure they receive the test email. If they do not, you can check the mailer log on the NG Firewall to see if there was an error, the file is /var/log/exim4/mainlog.
Why can't my off-site users get their Quarantine Digests?
The most common reason is that the Quarantine Digest has a URL with a private IP while they need a URL with a public IP. You'll need to verify a few settings:
- Under Config > Administration, make sure that Enable Outside HTTPS Administration is checked.
- Under Config > Administration > Public Address, choose Use Hostname or Use Manually Specified IP as appropriate.
- If using Use Hostname, make sure your hostname is properly configured and publicly resolvable at Config > Networking > Hostname. If you're using a Dynamic IP, it's recommended to set up Dynamic DNS on the same page.
What happens to email when the recipient is not on the quarantinable address list?
If you removed the wildcard and manually created a quarantinable address list, the Spam Blocker passes but marks the email as [Spam] for those that are not on the list.
What will happen if my rules are set to quarantine but the receiver's address cannot be quarantined?
The Quarantinable Addresses rules take precedence over the actions for email rules. In this situation, the email would be marked rather than quarantined.
Can I have NG Firewall drop mail that is not to valid users?
No as NG Firewall does not have a list of valid emails for your site. It is suggested that your configure your email server to not accept mail for invalid users. This is the default for almost all mail servers except Microsoft Exchange - the links below are instructions on how to configure your email server.
Why is mail not passing between my Exchange servers?
The Untangle Server forces Extended SMTP (ESMTP) to fall back to SMTP so that the transmitting emails may be scanned. When two Exchange servers are setup such that they require ESMTP communication, all communications will fail. This is enforced by transparent rewriting of the "EHLO" command to "HELO" and appropriate keywords are also stripped.
This can be fixed by adding a Bypass Rule for communication between the servers.