General
| Influence Axigen’s future product evolution — get early access to new features mockups, prototypes, and early previews and tell us your opinion. Join our product community newsletter |
63 results found
-
check MX record and reverse DNS
There is one more problem:
Axigen -> DNS Check
use Reject message if originator's domain has no MX entry
use Reject message if the originalting IP has no reverse DNS entryIf i use this two rules, they work as ALL conditions(not ANY conditions), that is wrong.
it is possible to make so that checked the MX record first and then checked reverse DNS,
and if MX record pass then don't checked reverse DNS.
Because not always MX record = A record in DNSThat is Reverse DNS has to be included only for entering connections or has to exclude…
1 vote -
Allow moving mailboxes between clustered nodes
When using a clustered environment it would be helpful if I could move mailboxes between servers in order to re-organize the logical location of a mailbox.
5 votes -
Introduce a DNSBL option to change the anti-spam score, beside the current default REJECT
The option to add points based on DNSBLs check result.
For example: A incoming email needs to have 10 points to be marked as
spam.Each DNSBL gets like 1,2 or 3 points. If an IP address is found on a
DNSBL, the points are added to the email. When it reaches 10, it's spam
and gets in a quarantine.If an incoming message has less than 5 points, it's clean and send to the
inbox of the user.0 votes
- Don't see your idea?