You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be helpful to introduce a new configuration option to allow suspicious macros depending on recipient, so that special destination e-mail addresses/mailboxes still can receive e-mails with suspicious macros. A typical scenario that comes to my mind is abuse@… or postmaster@….
In order to be flexible, the suggestion is to make the configuration option something like an array of strings with regular expression support. If I run example.net and would like to ensure that somebody can send suspicious macros to [email protected], that's one case (= string). However, if I (or my users) would like to be able to report such suspicious macros, including to remote abuse teams of foreign domains, something like ^(abuse|postmaster)@ (= regular expressions) could get important, too.
The text was updated successfully, but these errors were encountered:
I think it would be helpful to introduce a new configuration option to allow suspicious macros depending on recipient, so that special destination e-mail addresses/mailboxes still can receive e-mails with suspicious macros. A typical scenario that comes to my mind is
abuse@…
orpostmaster@…
.In order to be flexible, the suggestion is to make the configuration option something like an array of strings with regular expression support. If I run
example.net
and would like to ensure that somebody can send suspicious macros to[email protected]
, that's one case (= string). However, if I (or my users) would like to be able to report such suspicious macros, including to remote abuse teams of foreign domains, something like^(abuse|postmaster)@
(= regular expressions) could get important, too.The text was updated successfully, but these errors were encountered: