Encrypted Emails

2018-04-05 Thread Robitaille, Cameron
Hi:

I opened an issue at Bitlocker as well.  I am seeing in the mail log that all 
the email being received from my Exchange server is encrypted as:

Apr  5 14:55:39 archive piler-smtp[3228]: connected from 10.1.151.109:13538 on 
descriptor 6 (active connections: 1)
Apr  5 14:55:39 archive piler-smtp[3228]: received: SVH9T4ZEEX5FXDPF, from=, 
size=6583, client=10.1.151.109
Apr  5 14:55:39 archive piler-smtp[3228]: disconnected from 10.1.151.109 on 
descriptor 6 (0 active connections)
Apr  5 14:55:40 archive piler[7748]: 3/SVH9T4ZEEX5FXDPF: discarding: archiving 
policy: 
*domain=,from=,to=,subject=,body=,size0,att.name=,att.type=,att.size0,spam=0*
Apr  5 14:55:40 archive piler[7748]: 3/SVH9T4ZEEX5FXDPF: 
40005ac6713620a49b0400b8a3edfd2d, size=6583/0, attachments=0, 
reference=<80801026-26e5-4754-a9bd-a4038cdac...@gmail.com>, 
message-id=<4f5a8a28-652c-4523-9168-9e210332e...@gmail.com>, retention=0, 
folder=0, delay=0.0033, status=discarded

I am really not sure where to check for this.  Thanks,

Cameron Robitaille
Network Administrator
Waypoint Centre for Mental Health Care
Advancing Understanding. Improving Lives.

500 Church Street
Penetanguishene ON  L9M 1G3
(705) 549-3181 ext. 4636
crobitai...@waypointcentre.ca


This electronic transmission and accompanying attachments may contain 
privileged or confidential information intended only for the use of the 
individual or organization named above.  Any distribution, copy or action taken 
in reliance of the contents of this communication by anyone other than the 
intended recipient(s) is Strictly Prohibited.  If you have received this 
communication in error, please notify the sender at the above email address and 
delete this email.



bug in piler daemon causing badly encrypted emails

2012-08-16 Thread Janos SUTO



Dear piler users,

there's a bug in the piler daemon around the HUP signal handling.
After sending a HUP signal to piler it clears and re-reads its
configuration file. However it didn't re-read the encryption key,
so it encrypted every subsequent messages with with a zeroed key.

Workaround:

do not send a HUP signal to piler

Fix:

upgrade to the latest master branch:
https://bitbucket.org/jsuto/piler/get/master.tar.gz

Note that it's possible to recover the affected messages by tweaking
the pilerget (you need the latest from the master branch) utility not
to read the encryption key. You can do it by specifying a 2nd 
commandline

argument (anything), eg.

pilerget 4000502cc87b367e6e8c2169f73c2926 nokey

If you need assistance to do so just let me know.

Janos