ajosephson
asked on
Intercept then deliver email
For security/compliance reasons I need to come up with a way to intercept, save locally then deliver any email destined for a specific external domain Eg all email sent to usatoday.com.
Notes 6.5 - journaling is not practically.
Notes 6.5 - journaling is not practically.
specifically
Setting up the Mail Journaling database
Setting up the Mail Journaling database
ASKER
Notes 6.5 - journaling is not practical – it is already turned on for all email; retrieving specific emails from amongst the thousands is tedious; the email is encrypted which further complicates the process plus it is an after the fact, proactive process
Ideally all Emil destined for a specific domain should be copied to a database which authorized users can access, then the email is delivered to its destination.
I’m surprised this seemingly straightforward request is relatively difficult to accomplish with domino.
Ideally all Emil destined for a specific domain should be copied to a database which authorized users can access, then the email is delivered to its destination.
I’m surprised this seemingly straightforward request is relatively difficult to accomplish with domino.
You can set up rules for what is journaled, thus making it much easier.
I know this is available in R7, not positive about R 6.5
I know this is available in R7, not positive about R 6.5
ASKER
Notes 6.5 - journaling is not practical – **** it is already turned on for all email *** as company policy I cannot create routing rules to filter.
OK, then you would need to write an agent in your mail inboxes that can send a copy of the specific emails to another mail DB, before sending them out.
Not a suggested practice.
Other options are to use the Notes API to access the Router and do it that way.
Also not fun.
Not a suggested practice.
Other options are to use the Notes API to access the Router and do it that way.
Also not fun.
ASKER
Great news - however I need a definitive solution; can you pls provide the code and process to put in place your suggestions?
AJ
AJ
Sorry, the first one you can try yourself and needs to be tested, since stuff like anti-virus and content filters may also be trying to grab email , and the second is a lot of work, and you are going to have to implement it.
Unless someone else has already done something similar and has tested code,
I think that this may beyond the scope of EE, but I could be mistaken.
Unless someone else has already done something similar and has tested code,
I think that this may beyond the scope of EE, but I could be mistaken.
Hmm... if you are archiving mail for compliance, and journeling is not an option, then any home-built remedy is not for the faint of heart (as sysExpert says). :)
There are other third party solutions that meet this requirement such as: http://www.sherpasoftware.com/ArchiveDocsAtt.shtml
http://www.opentext.com/2/sol-products/sol-pro-email/pro-ll-emailarchiving-lotusnotes-email.htm
------
But trying to create a solution that does this is somewhat like reinventing the wheel, since port 25 routing comes into play, and you have to decide when you want to "grab" email, along with the consequences of what you grab when you make that decision.. for example, if you grab everything before the spam and virus filters, then you end up archiving everything, along with potentially dangerous email.
There are other third party solutions that meet this requirement such as: http://www.sherpasoftware.com/ArchiveDocsAtt.shtml
http://www.opentext.com/2/sol-products/sol-pro-email/pro-ll-emailarchiving-lotusnotes-email.htm
------
But trying to create a solution that does this is somewhat like reinventing the wheel, since port 25 routing comes into play, and you have to decide when you want to "grab" email, along with the consequences of what you grab when you make that decision.. for example, if you grab everything before the spam and virus filters, then you end up archiving everything, along with potentially dangerous email.
ASKER
Ok, fair enough.
What if I setup a bogus MX record in DNS to resolve the host of interest to another - stand-alone - internal Domino server with Journaling? The server will journal then use another DNS to resolve the actual MX to send.
The only email passing through that server would be for the particular domain.
Or perhaps configure a ‘foreign domain’.
Your comments?
I did that with all smtp mail at my last location. One server that collected all incoming and outgoing smtp mail. The public address book resolved the name delivery, so all you had to do was create the SMTP route to that server.
This was pre-R6, but I did this for performance reasons.. all the spam and heavy hitting virus filters were on that server, leaving the email servers to run without impact.
This was pre-R6, but I did this for performance reasons.. all the spam and heavy hitting virus filters were on that server, leaving the email servers to run without impact.
If you have the resources to set up another dedicated server just for this, then that should be OK.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
True. Kspam: if you turn on the filter in test mode will copy all to the mailgood.nsf, and send spam to mailbad.nsf.
See the journal option in the Notes Admin Client help.
I hope this helps !