SMTP traffic filtering allows you to:
Route only emails that should have a Letsignit signature
Exclude technical or automated emails (scans, no-reply, alerts, etc.)
Optimize overall email processing and ensure a better quality of service
How do I exclude certain addresses from the SMTP traffic?
Google Workspace allows you to manage exclusions through address lists.
Steps to add exclusions:
In the routing rule, click on Show options
Enable:
Use address lists to control the application of this rule
Select:
Do not apply this rule to senders matching this list
Click Create or edit an address list
Create a dedicated list (e.g.: SMTP Exclusions)
Add the addresses or prefixes to exclude
This method is officially supported by Google and is recommended over complex filters or regular expressions.
What types of addresses should be excluded?
It is advisable to exclude technical or automated addresses, for example:
no-reply@ / noreply@ (e.g. no-reply@domain.com, noreply@domain.com)
scan@ (scan@domain.com)
printer@ (printer@domain.com)
monitoring@ (monitoring@domain.com)
supervision@ (supervision@domain.com)
alert@ / alerts@ (alert@domain.com, alerts@domain.com)
root@ (root@domain.com)
centreon-engine@ (centreon-engine@domain.com)
paloalto@ (paloalto@domain.com)
notification@ / notifications@ (notification@domain.com)
zabbix@ (zabbix@domain.com)
report@ / reports@ (report@domain.com)
ne-pas-repondre@ (ne-pas-repondre@domain.com)
admin@ (admin@domain.com)
automatisme@ / automatismes@ (automatisme@domain.com)
copieur.canon@ (copieur.canon@domain.com)
gitlab@ (gitlab@domain.com)
These emails are not intended to have a signature.
What happens to excluded emails?
Excluded emails do not pass through the Letsignit SMTP traffic
They continue to be sent normally through Gmail
Only relevant emails are processed by Letsignit
This allows you to:
avoid any unnecessary or inappropriate processing
optimize email traffic handling
ensure a better overall quality of service