Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

CLI Reference

antispam greylist exempt

Use this command to configure the greylist exempt list.

Greylist scanning blocks spam based on the behavior of the sending server, rather than the content of the messages. When receiving an email from an unknown server, the FortiMail unit will temporarily reject the message. If the mail is legitimate, the originating server will try to send it again later (RFC 2821), at which time the FortiMail unit will accept it. Spam senders rarely attempt a retry.

Syntax

config antispam greylist exempt

edit <entry_index>

set recipient-pattern <recipient_pattern>

set recipient-pattern-regexp {enable | disable}

set reverse-dns-pattern <reverse-dns_pattern>

set reverse-dns-pattern-regexp {enable | disable}

set sender-ip <client_ipv4/mask>

set sender-pattern <sender_pattern>

set sender-pattern-regexp {enable | disable}

next

end

Variable

Description

Default

<entry_index>

Greylist exempt rule ID.

recipient-pattern <recipient_pattern>

Enter a pattern that defines recipient email addresses which match this rule, surrounded in slashes and single quotes (such as \'*\' ).

recipient-pattern-regexp {enable | disable}

Enter enable if you used regular expression syntax to define the pattern.

Enter disable if you did not use regular expression syntax to define the pattern (that is, you entered a complete email address, or you entered a pattern using simple wild card characters * or ?).

disable

reverse-dns-pattern <reverse-dns_pattern>

Enter a pattern that defines reverse DNS query responses which match this rule, surrounded in slashes and single quotes (such as \'*\' ).

reverse-dns-pattern-regexp {enable | disable}

Enter enable if you used regular expression syntax to define the pattern.

Enter disable if you did not use regular expression syntax to define the pattern (that is, you entered a complete email address, or you entered a pattern using simple wild card characters * or ?).

disable

sender-ip <client_ipv4/mask>

Enter the IP address and netmask of the SMTP client.

To match SMTP sessions from any SMTP client, enter 0.0.0.0/0.

sender-pattern <sender_pattern>

Enter a pattern that defines sender email addresses which match this rule, surrounded in slashes and single quotes (such as \'*@example.com\' ).

sender-pattern-regexp {enable | disable}

Enter enable if you used regular expression syntax to define the pattern.

Enter disable if you did not use regular expression syntax to define the pattern (that is, you entered a complete email address, or you entered a pattern using simple wild card characters * or ?).

disable

Related topics

antispam bounce-verification

antispam deepheader-analysis

antispam quarantine-report

antispam settings

antispam trusted

antispam greylist exempt

Use this command to configure the greylist exempt list.

Greylist scanning blocks spam based on the behavior of the sending server, rather than the content of the messages. When receiving an email from an unknown server, the FortiMail unit will temporarily reject the message. If the mail is legitimate, the originating server will try to send it again later (RFC 2821), at which time the FortiMail unit will accept it. Spam senders rarely attempt a retry.

Syntax

config antispam greylist exempt

edit <entry_index>

set recipient-pattern <recipient_pattern>

set recipient-pattern-regexp {enable | disable}

set reverse-dns-pattern <reverse-dns_pattern>

set reverse-dns-pattern-regexp {enable | disable}

set sender-ip <client_ipv4/mask>

set sender-pattern <sender_pattern>

set sender-pattern-regexp {enable | disable}

next

end

Variable

Description

Default

<entry_index>

Greylist exempt rule ID.

recipient-pattern <recipient_pattern>

Enter a pattern that defines recipient email addresses which match this rule, surrounded in slashes and single quotes (such as \'*\' ).

recipient-pattern-regexp {enable | disable}

Enter enable if you used regular expression syntax to define the pattern.

Enter disable if you did not use regular expression syntax to define the pattern (that is, you entered a complete email address, or you entered a pattern using simple wild card characters * or ?).

disable

reverse-dns-pattern <reverse-dns_pattern>

Enter a pattern that defines reverse DNS query responses which match this rule, surrounded in slashes and single quotes (such as \'*\' ).

reverse-dns-pattern-regexp {enable | disable}

Enter enable if you used regular expression syntax to define the pattern.

Enter disable if you did not use regular expression syntax to define the pattern (that is, you entered a complete email address, or you entered a pattern using simple wild card characters * or ?).

disable

sender-ip <client_ipv4/mask>

Enter the IP address and netmask of the SMTP client.

To match SMTP sessions from any SMTP client, enter 0.0.0.0/0.

sender-pattern <sender_pattern>

Enter a pattern that defines sender email addresses which match this rule, surrounded in slashes and single quotes (such as \'*@example.com\' ).

sender-pattern-regexp {enable | disable}

Enter enable if you used regular expression syntax to define the pattern.

Enter disable if you did not use regular expression syntax to define the pattern (that is, you entered a complete email address, or you entered a pattern using simple wild card characters * or ?).

disable

Related topics

antispam bounce-verification

antispam deepheader-analysis

antispam quarantine-report

antispam settings

antispam trusted