Feature Requests

Your search for "recipient validation" returned 6 results:

DONE Reject Emails Sent to Disabled Recipient Addresses

| Last activity: 1 year ago
Currently, the Active Directory-based Recipient Validation of ORF blacklists emails sent to non-existent recipients in the Active Directory. By implementing this feature, ORF would reject incoming emails for existent, but disabled recipient addresses as well.
34

Validate Sender Address using Recipient Validation

| Last activity: 7 years ago
Validate sender email addresses using the same valid email address source as the Recipient Validation test if it claims to be from any of the local domains. For instance, if the sender is [email protected] and example.com is my domain, check if [email protected] is a valid email address.
21

Recipient Validation Test Generic LDAP Support

| Last activity: more than 10 years ago
Support non-Exchange LDAP directories (such as Novell NDS, OpenLDAP, etc.) and schemas for the Recipient Validation Test. This would allow ORF users with non-Exchange servers to take advantage of the Recipient Validation test without importing the valid recipient addresses into an SQL database or text file.
24

Recipient Validation to Support Multiple LDAP Paths

| Last activity: 6 years ago
Currently, only a single LDAP path could be set for the Active Directory-based Recipient Validation feature, so ORF can query the valid recipient list from a single Active Directory only. This improvement would allow ORF users with multiple Active Directories to take advantage of the Recipient Validation test without importing the valid recipient addresses into an SQL database or text file from each Active Directory periodically.
30
hnp1 | hnp2