Hello Torsten,

On Thursday December 25 2014 01:09, you wrote to Roy Witt:


 TB> 1.) your system gets an pgp-encrypted echomail, but the public key
 TB> doesn't match. Basically, your system bounces the echomail, and it
 TB> will get lost.

Encrypted echomail does not make much sense. The idea of using encryption is
that only the intended receiver can read it. Makes no sense for echomail.

 TB> 2.) your system gets a zip-encrypted netmail via unprotect inbound
 TB> Usually this netmail will be bounced, because it comes up via
 TB> unprotect inbound. But, because of your enc-flag you've got to route
 TB> or crash the netmail to the specific exit-system.

No. The ENC flag just means that you will not treat it different from
unencrypted mail. If you do not automatically process compressed netmail from
your unsecure inbound, you do not have to process it either if it is encrypted.

The ENC flag just means that you will not refuse to route it simply because it
is encrypted. You still do not have to route mail for everyone. If you have not
agreed to route mail from A to B, than you do not have to route encrypted mail
from A to B either.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111