Submitted on behalf of a customer:
The requests
I would like to submit for Pure Message could be:
I would like to submit for Pure Message could be:
- about
"suspicious attachments": why can I create a "white list" (senders and
recipients) for spam, but not for "suspicious attachments" (senders and
recipients) ?
"suspicious attachments": why can I create a "white list" (senders and
recipients) for spam, but not for "suspicious attachments" (senders and
recipients) ?
- about smtp
receivers (in my Exchange 2003 they were called "connectors", on newer Exchange
I don't remember): I have more than one receiver (each one on different port),
and I'd like to enable Pure Message only on one of them. Instead, pure message
checks them all. To resolve the problem, I have to install multiple exchange
servers, one with pure message, the others without.
receivers (in my Exchange 2003 they were called "connectors", on newer Exchange
I don't remember): I have more than one receiver (each one on different port),
and I'd like to enable Pure Message only on one of them. Instead, pure message
checks them all. To resolve the problem, I have to install multiple exchange
servers, one with pure message, the others without.
- about "double extension
detection": right now it is unusable, since attachments like "document version
x.y.doc" are considered "double extension". A real double extension contains
ONLY 3 charachters between the last two dots, or, in the worst case, 4
charachters, one of which is UNDERSCORE (es:
sample.pdf_.exe)
detection": right now it is unusable, since attachments like "document version
x.y.doc" are considered "double extension". A real double extension contains
ONLY 3 charachters between the last two dots, or, in the worst case, 4
charachters, one of which is UNDERSCORE (es:
sample.pdf_.exe)
- about "offensive
language" : base-64 encoded attachments (or
base-64 encoded part of a mail) doesn't have to be scanned for bad words:
base-64 can contain all kind of alphabet combinations, including bad words (As I
can confirm).
language" : base-64 encoded attachments (or
base-64 encoded part of a mail) doesn't have to be scanned for bad words:
base-64 can contain all kind of alphabet combinations, including bad words (As I
can confirm).
I know new
release of Pure Message is not Exchange 2003 compatible .... but I
hope.
release of Pure Message is not Exchange 2003 compatible .... but I
hope.
This thread was automatically locked due to age.
