It's just a zip file with mxredir.txt & mxredir.dll
EDIT: Oops, that was my zip file, it's just the .dll available here (http://www.xs4all.nl/~fenke/files/mxredir.dll). The text file was a post from the mailing list. (copied below)
It seems fairly basic / beta but I tested it on 4.01b and it worked as advertised. Have not tried it on 4.5x but it should work.
Note the cautions about dropping undeliverable mail, I would suggest an 'Archive' filtering rule for that domain mail for backup purposes in case the network (or more likely Exchange [:P]) goes down.
BEGIN MXREDIR.TXT
Have you thought of using a MX type operation here using a daemon?
Mercury/32 does not yet have the capability of forwarding all mail for a domain
off to another server. That said, Frans Meijer has written a small daemon that
can do this. I've tested this and it seems to work just fine. You might want to
setup a Mercury/32 "Always" filter to send all of the mail for this domain off to
one of your local mail accounts so you'll not lose mail.
---------------------------------- quote ------------------------------------------------
A first version - for testing, not production use - is at
http://www.xs4all.nl/~fenke/files/
The actual daemon to use is mxredir.dll the rest are the sources to build it, for
which you also need daemon.h from the Mercury distribution and Borlands free
C++ compiler (should not be hard to port to other compilers though - mind the
alignment issues).
Put the dll in a convenient directory, for instance the Mercury directory, assume
C:\Mercury for the remaining text and 192.168.2.3 is the ip address of the
receiving MTA.
In Mercury Core config, local domains tab add a new domain. In the Edit
domain entry dialog fill in the local server and internet domain:
Local host or server: daemon:C:\Mercury\mxredir.dll;[192.168.2.3]
Internet name: test.local
(You can off course another domain name and ip address)
Messages send to <any-mailbox@test.local> should now be processed by the
daemon, you can see this in the core-process window (Job ... from ... To:
daemon:C:\M ...etc...)
The daemon writes to a log file 'redirector.log' in the Mercury
directory.
Caution.
Mercury expects the domain-daemon to handle the message, it hands the job
over, then discards the original. If, for whatever reason, the daemon can not
forward the message, it is lost. A backup mechanism should be added, for
instance writing the message to a file somewhere, or dropping in a user mailbox
(though if it can't create the forward message that might be a problem to). Your
input is welcome.
I feel there should be some more validations, for instance on the parameter
passed, maybe on the rcpt addresses. Perhaps not use a logfile (another point of
failure) and certainly not abort if it can't be opened. More?
The current daemon will likely not work if the _source_ is a domain-popbox, I
don't know (yet) how the rcpt to address will look in the job-info passed to the
daemon, the daemon expects <mailbox@domain>
As said, this is not (yet) for production. If anyone gives it a test-run, let me know
how it works, problems and change requests. (post here or to reply-to or if that
fails: <frans.meijer@xs4all.nl>)
------------------------ end quote ---------------------------------------------------
END MXREDIR.TXT
