|Published (Last):||6 May 2014|
|PDF File Size:||10.13 Mb|
|ePub File Size:||16.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
The critical point of AMaViS configuration is to decide what action should be taken when an undesirable message is found. If a quarantine is configured, a copy of the mail will go there, if not, at least the recipient received the mail. A non-delivery notification bounce will be created and sent to the sender. If a quarantine is configured, a copy of the mail will go there, if not eMail message will be lost, but if the mail was legitimate, the sender should receive notification of the disposition of the message.
If a quarantine is configured, a copy of the mail will go there, if not eMail message will be lost, but the sender should be notified their message was rejected.
If a quarantine is configured, a copy of the mail will go there, if not eMail message will be lost. Typically it is up to the system administrator to review what is in this mailbox, and either forward the message to the recipient, or delete the message.
This copy can be examined by the administrator and a determination made whether there should be any further action to prevent similar email from entering the system. Malformed headers, while annoying, are typically not a security risk. Usually a score of 5. In other words, these two spam settings are parallel to the settings of the other three types of undesirable mail. Setting this to undef or means every message that is considered local will have these informative headers added, SPAM or not.
This is done for mail that once again is considered local and will actually reach a recipient. A copy of the mail will go to the email address configured. This setting allows to discard quarantined spam at this level and above.
Oh no! Some styles failed to load. 😵
Amavis - 'Blocked BANNED'
Postfix Amavis - MTA - BLOCKED