profile antispam-action
Use this command to configure antispam action profiles.
Syntax
config profile antispam-action
edit <profile_name>
set alternate-host {<relay_fqdn> | <relay_ipv4>}
set alternate-host-status {enable | disable}
set archive-account <account_name>
set archive-status {enable | disable}
set bcc-addr <recipient_email>
set bcc-env-from-addr <message_str>
set bcc-env-from-status {enable | disable}
set bcc-status {enable | disable}
set defer-delivery {enable | disable}
set deliver-to-original-host {enable | disable}
set disclaimer-insertion {enable | disable}
set disclaimer-insertion-content <message_name>
set disclaimer-insertion-location {beginning | end}
set fortiguard-antispam-outbreak {enable | disable}
set header-insertion-name <name_str>
set header-insertion-status {enable | disable}
set header-insertion-value <header_str>
set notification-profile <profile_name>
set notification-status {enable | disable}
set rewrite-rcpt-local-type {none | prefix | replace | suffix}
set rewrite-rcpt-local-value <value_str>
set rewrite-rcpt-domain-type {none-prefix | replace | suffix}
set rewrite-rcpt-domain-value <value_str>
end
Variable |
Description |
Default |
Enter the name of an antispam action profile. |
|
|
action {discard | domain-quarantine | none | personal-quarantine | reject | rewrite-rcpt | system-quarantine} |
Enter an action for the profile.
If you enter this option, also configure rewrite-rcpt-local-type {none | prefix | replace | suffix}, rewrite-rcpt-local-value <value_str>, rewrite-rcpt-domain-type {none-prefix | replace | suffix}, and rewrite-rcpt-domain-value <value_str>. |
none |
Type the fully qualified domain name (FQDN) or IP address of the alternate relay or SMTP server. This field applies only if |
|
|
Enable to route the email to a specific SMTP server or relay. Also configure alternate-host {<relay_fqdn> | <relay_ipv4>}. Note: If you enable this setting, for all email that matches the profile, the FortiMail unit will use this destination and ignore mailsetting relay-host-list and the protected domain’s tp-use-domain-mta {yes | no}. |
disable |
|
Type the email archive account name where you want to archive the spam. Enable archive-status {enable | disable} to make this function work. For more information about archive accounts, see antispam url-fgas-exempt-list. |
|
|
Enable to allow the archive-account <account_name> function to work. |
disable |
|
Type the blind carbon copy (BCC) recipient email address. This field applies only if |
|
|
Specify an envelope from BCC address. In the case that email is not deliverable and bounced back, the email is returned to the specified envelope from address instead of the original sender. This is helpful when you want to use a specific email to collect bounce notifications. This field applies only if |
|
|
Enable to specify an envelope from address. |
disable |
|
Enable to send a BCC of the email. Also configure bcc-addr <recipient_email>. |
disable |
|
Enable to defer delivery of emails that may be resource intensive and reduce performance of the mail server, such as large email messages, or lower priority email from certain senders (for example, marketing campaign email and mass mailing). |
disable |
|
Enable to deliver the message to the original host. |
disable |
|
Enable to insert disclaimer. |
disable |
|
Specify the content name to be inserted. |
default |
|
Insert the disclaimer at the |
beginning |
|
Enable to manually defer emails and place email in the spam defer queue. Note: The Spam outbreak protection option under System > FortiGuard > AntiSpam does not affect this feature. |
disable |
|
Enter the message header key. The FortiMail unit will add this text to the message header of the email before forwarding it to the recipient. Many email clients can sort incoming email messages into separate mailboxes, including a spam mailbox, based on text appearing in various parts of email messages, including the message header. For details, see the documentation for your email client. Message header lines are composed of two parts: a key and a value, which are separated by a colon. For example, you might enter:
If you enter a header line that does not include a colon, the FortiMail unit will automatically append a colon, causing the entire text that you enter to be the key. Note: Do not enter spaces in the key portion of the header line, as these are forbidden by RFC 2822. |
|
|
Enable to add a message header to detected spam. |
disable |
|
Enter the message header value. Message header lines are composed of two parts: a key and a value, which are separated by a colon. For example, you might enter:
If you enter a header line that does not include a colon, the FortiMail unit will automatically append a colon, causing the entire text that you enter to be the key. Note: Do not enter spaces in the key portion of the header line, as these are forbidden by RFC 2822. |
|
|
Type the name of the notification profile used for sending notifications. |
|
|
Enable sending notifications using a notification profile. |
disable |
|
Change the local part (the portion of the email address before the '@' symbol, typically a user name) of the recipient address of any email message detected as spam.
|
none |
|
Enter the text for the option (except |
|
|
Change the domain part (the portion of the email address after the '@' symbol) of the recipient address of any email message detected as spam.
|
none |
|
Enter the text for the option (except |
|