The EuroUnion is something else. We have a monetary union (Euro), passport union (Schengen) and the European Community (EC).

The EC doesn't legislate, it is the job of each nation. The EC Council issues directorates, that the countries adopt (to different degrees).

I haven't investigated if the logs are sufficient, but as I recall it they do not. I will meet with Rolf L. to discuss if we can pull the connecting information in a more timely fashion. Since David also said he would re-work the logs I've put this on hold for a more thorough discussion among the testers.

Edit: But in any case, within the EC only ISPs (defined as anyone providing a service for anyone else, in this case an email service for a domain they do not own themselves), have to store this information for x nbr of months.

The Federal Rules of Civil Procedure  in the US now requires that schools and other organizations maintain an archive of electronic messages to be available as part of civil lawsuits for use in information discovery and other things.  We had been doing the email archive another way, but have found out we may not have been fully compliant with the requirement.  We now have a system (datacove) that can archive every email message and make those messages searchable and sortable etc.  The problem is that we are using a very old (and VERY reliable) version of Mercury Mail as our mail server.  We are running a Novell 4.11 server (Yup - if it is not broken - don't fix it) with Novell NLM versions of Mercury running on it.

• Mercury Transport System, NDS Mode Core Delivery Module Version 1.48
• Mercury Transport System, SMTP server module V1.48
• Mercury Transport System, POP server module V1.48
• Mercury Transport System, SMTP Client  module V1.48

The basic system stores a copy of each message in the user's home directory (in a PMail folder) and the most users use Pegasus mail to retreive their mail.  It has worked great for over 12 years.

HERE IS THE ISSUE - we need to change the system at the server level so EVERY message, every reply, every forward, every local mail etc. gets forwarded to an email address which can be used by the Datacove to retreive the messages, and store, and organize those messages.  Many of the posts I have read mention Filters and rules, but it seems like they are talking about the Windows (Merc / 32) version of the software and not the old Netware Lodable Modules (NLM's) that we are using.

How do I set up this configuration to copy out every email?  I am guessing it might be a domain mailbox but it looks like that is only available for MercuryD which is not available for the NLM version - right?.

PS - Talk to me like a 6th grader on this.  I have not really touched the email server other than to create users and maybe remove a few using NConfig.exe.  I have had no reason to play with it or make any changes to the email system.  I did a set it and forget it years ago.

Thanks in advance!

How do I set up this configuration to copy out every email?

Mercury.NLM has no filtering at all.  There is no easy way to archive all mail going through this system.  However since all mail sent is going through a relay host the relay host might be able to do this. Same thing with the inbound mail if it is going through a gateway.

That said, I would recommend converting from Mercury to Mercury/32.  Mercury/32 has an always filter that is capable of forwarding a copy of all mail, both inbound and outbound to a separate email address for the purposes of archiving.  You in fact do not even have to shutdown the current Mercury system until the mercury/32 system is up and in place.  Once you know it is working you just swap the hostnames and IP addresses of the Netware and Mercury/32 system to implement the change.

PS - Talk to me like a 6th grader on this.  I have not really touched

the email server other than to create users and maybe remove a few

using NConfig.exe.  I have had no reason to play with it or make any

changes to the email system.  I did a set it and forget it years ago.

That's really why i still run a Netware v3.2 server here at home.   As long as I do not lose power longer than the UPS can keep it on line I just forget it.  I do run a Mercury/32 system though as the gateway host.

We have an upcoming law on this in Europe that require all ISPs to store all the headers including available connecting information on all open ports. We're not allowed to store the actual message contents. How to solve this with Mercury/32 is still an issue for us.

We have an upcoming law on this in Europe that require all ISPs to

store all the headers including available connecting information on all

open ports. We're not allowed to store the actual message contents. How

to solve this with Mercury/32 is still an issue for us.

I know we went through this one before but could you point to this requirement in English again.  I've again had people in the EuroUnion say that this can be satisfied by maintaining the MercuryS, MercuryI and MercuryP logs with the SMTP mail headers and the user connecting info.  I suspect though that, as always, the actual implementation is going to be national rather than EuroUnion.