* on the Mon, Feb 16, 2015 at 03:50:24PM +, Viktor Dukhovni wrote:
On Mon, Feb 16, 2015 at 12:57:26PM +, Mike Cardwell wrote:
On an old Exim box, I used to do something similar to this with the following
two line bit of config:
deny condition = ${if !match{$message_body}{-BEGIN
On Mon, Feb 16, 2015 at 12:57:26PM +, Mike Cardwell wrote:
On an old Exim box, I used to do something similar to this with the following
two line bit of config:
deny condition = ${if !match{$message_body}{-BEGIN PGP MESSAGE-}}
message = Unencrypted message. Encrypt then
Le 16/02/2015 14:09, Michael Ströder a écrit :
LuKreme wrote:
I’d assume there would be something in the headers to indicate the message
was encrypted. Probably some sort of milter running on your submission port
would be able to check this?
I'd implement a milter or similar which looks at
Erwan David wrote:
Le 16/02/2015 14:09, Michael Ströder a écrit :
LuKreme wrote:
I’d assume there would be something in the headers to indicate the message
was encrypted. Probably some sort of milter running on your submission port
would be able to check this?
I'd implement a milter or
Mike Cardwell:
On an old Exim box, I used to do something similar to this with the following
two line bit of config:
deny condition = ${if !match{$message_body}{-BEGIN PGP MESSAGE-}}
message = Unencrypted message. Encrypt then retry.
Is there really no equivalent way of
My thanks everybody for their input.
It looks as though trying to reliably determine if effective encryption
is being will be difficult.
Plus, as somebody pointed out there is the additional problem of
acquiring the correspondents encryption keys, assuming they have one.
Having discussed this
* on the Mon, Feb 16, 2015 at 11:39:22AM +0100, lst_ho...@kwsoft.de wrote:
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the conclusion that in order
to avoid
LuKreme wrote:
I’d assume there would be something in the headers to indicate the message
was encrypted. Probably some sort of milter running on your submission port
would be able to check this?
I'd implement a milter or similar which looks at the Content-Type header.
Typically it looks like
Zitat von John j...@klam.ca:
A couple of the servers I support are medical offices, and for
patient confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the conclusion that in
order to avoid accidentally sending confidential data
On 2015-02-15 John wrote:
A couple of the servers I support are medical offices, and for
patient confidentiality reasons they need to send email out
encrypted.
After a lot of discussion they have come to the conclusion that in
order to avoid accidentally sending confidential data
On Sun, Feb 15, 2015 at 9:12 AM, John j...@klam.ca wrote:
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the conclusion that in order to
avoid accidentally
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the conclusion that in order
to avoid accidentally sending confidential data unencrypted, all email
must be
On 2/15/2015 9:40 AM, Mauricio Tavares wrote:
On Sun, Feb 15, 2015 at 9:12 AM, John j...@klam.ca wrote:
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the
On 15 Feb 2015, at 07:56 , John j...@klam.ca wrote:
On 2/15/2015 9:40 AM, Mauricio Tavares wrote:
On Sun, Feb 15, 2015 at 9:12 AM, John j...@klam.ca wrote:
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
14 matches
Mail list logo
