copy all inbound mail to another server on internet lan

posted Oct 29 '10 at 11:00 pm

> Could I have a second Mercury install, that POPs a domain mailbox from my original Mercury?
>
> And then have this second Mercury forward with mercuryE to the server I'm trying to reach internally?

Sure but you might be able to do the same thing with WSMTPEx without the second instance.

The program WSMTPEx.exe (SMTPEX.NLM for Netware) and this a separate program that takes mail for a email account and forwards it to any port and any hostname/IP address. I use this with my domains to forward the mail to a Linux system (must use high ports as non-root) and to a second instance of Mercury/32 running on my system (can't share port 25) Here's a sample of the ini file I use for forwarding all mail to Mercury/32 running on Ubuntu and Wine.

# You can rename this tool, but name of following section must remain [WSMTPEx]
[WSMTPEx]
Version=0.10
# TCP port, on which SMTP server listens
Port=8025
# Number of seconds to delay between searches for emails
LoopDelay=30
# Folder, under which is most of user's mailboxes
UserFolder=
Domains=1
# Users mail address domain part
Domain1=linux-tstephenson.com
LogName=c:\Mercury\WSMTPEx.log
SMTPServer=192.168.1.4
MailBoxes=1
Badmails=c:\pmail\mail\BadMail

[linux-tstephenson.com]
# When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file
Mb1addr=dm:ubunto
Mb1dir=c:\pmail\mail\ubunto

This takes all the mail in the domain account "UBUNTO" and sends it to port 8025 on
192.168.1.4 to be received by MercuryS. The directory BADMAIL I have specified
must exist. You can run multiple instances of this tool and and it can be run as a
service. If run as a service and running multiple instances the name of the program
should be changed. I use WSE-UBUNTO to rename the program and ini file for this
one.

Many thanks to Petr Jaklin for the development of these tools. You can get these
tools at the community download areas or directly from Petr Jaklin's site
http://www.3net.cz/software/softe.htm

&gt; Could I have a second Mercury install, that POPs a domain mailbox from my original Mercury? &gt; &gt; &nbsp;And then have this second Mercury forward with mercuryE to the server I'm trying to reach internally? Sure but you might be able to do the same thing with WSMTPEx without the second instance. The program WSMTPEx.exe (SMTPEX.NLM for Netware)&nbsp; and this a separate program that takes mail for a email account and forwards it to any port and any hostname/IP address.&nbsp; I use this with my domains to forward the mail to a Linux system (must use high ports as non-root) and to a second instance of Mercury/32 running on my system (can't share port 25)&nbsp; Here's a sample of the ini file I use for forwarding all mail to Mercury/32 running on Ubuntu and Wine.&nbsp; &nbsp; &nbsp;#&nbsp; You can rename this tool, but name of following section must remain [WSMTPEx] [WSMTPEx] Version=0.10 #&nbsp; TCP port, on which SMTP server listens Port=8025 #&nbsp; Number of seconds to delay between searches for emails LoopDelay=30 #&nbsp; Folder, under which is most of user's mailboxes UserFolder= Domains=1 # Users mail address domain part Domain1=linux-tstephenson.com LogName=c:\Mercury\WSMTPEx.log SMTPServer=192.168.1.4 MailBoxes=1 Badmails=c:\pmail\mail\BadMail [linux-tstephenson.com] # When user name start with "DM:", WSMTPEx will try to find SMTP envelope address in mail file Mb1addr=dm:ubunto Mb1dir=c:\pmail\mail\ubunto This takes all the mail in the domain account "UBUNTO"&nbsp; and sends it to port 8025 on 192.168.1.4 to be received by MercuryS.&nbsp; The directory BADMAIL I have specified must exist.&nbsp; You can run multiple instances of this tool and and it can be run as a service.&nbsp; If run as a service and running multiple instances the name of the program should be changed.&nbsp; I use WSE-UBUNTO to rename the program and ini file for this one. &nbsp; Many thanks to Petr Jaklin for the development of these tools.&nbsp; You can get these tools at the community download areas or directly from Petr Jaklin's site http://www.3net.cz/software/softe.htm &nbsp;

jbrowne

posted Oct 26 '10 at 8:01 pm

I am currently using (live) an install of Mercury 4.52

with modules: MercuryS, MercuryC, MercuryP, MercuryI

we use MercuryC to send outbound mail to "MessageLabs" who handles our mail relaying.

I want my users to continue getting / sending their mail with Pegasus POP3/SMTP & this Mercury install.

I also want a COPY of all inbound mail (from outside the local lan) to go to another mail server I am testing.

searching the forums, I did find this: http://community.pmail.com/forums/thread/17837.aspx

but, 1) I do not want to forward only or move, i want to copy

2) I tried sending mail through mercury user@IP but it only tried to deliver through MercuryC and onto our mail relayer, instead of sending it locally.

-jason

I am currently using (live) an install of Mercury 4.52with modules: MercuryS, MercuryC, MercuryP, MercuryI&nbsp;we use MercuryC to send outbound mail to "MessageLabs" who handles our mail relaying.&nbsp;I want my users to continue getting / sending their mail with Pegasus POP3/SMTP &amp; this Mercury install.&nbsp;I also want a COPY of all inbound mail (from outside the local lan) to go to another mail server I am testing.&nbsp;searching the forums, I did find this: http://community.pmail.com/forums/thread/17837.aspxbut, 1) I do not want to forward only or move, i want to copy2) I tried sending mail through mercury user@IP but it only tried to deliver through MercuryC and onto our mail relayer, instead of sending it locally.&nbsp;-jason

Rolf Lindby

posted Oct 27 '10 at 12:32 am

1. If the other server can collect mail from a POP3 mailbox you could use a global filtering rule to do this. The tricky part will be to decide which messages originate externally, but you could perhaps simply check if header Sender contains the name of your domain. If not then copy message to a mailbox where it can be retrieved by the other server. Other than that it would of course be possible to do it with a daemon, but that will require some programming.

2. Two things: did you remember the brackets (user @[IPaddress])? And did you include the IP address in local domains in Mercury core configuration (again with brackets)?

/Rolf

1. If the other server can collect mail from a POP3 mailbox you could use a global filtering rule to do this. The tricky part will be to decide which messages originate externally, but you could perhaps simply check if header Sender contains the name of your domain. If not then copy message to a mailbox where it can be retrieved by the other server. Other than that it would of course be possible to do it with a daemon, but that will require some programming.2. Two things: did you remember the brackets (user @[IPaddress])? And did you include the IP address in local domains in Mercury core configuration (again with brackets)?/Rolf

jbrowne

posted Oct 27 '10 at 7:02 pm

I did try with and without the brackets, but I did NOT include the IP address in local domains in Mercury core.

should I put it in like this:

Local Host or server Internet Name

----------------------------                                     ---------------------
domain1                                                     domain1
domain1                                                     domain1.com
domain1                                                     mail.domain1.com
domain2                                                     [192.168.x.x]

I did try with and without the brackets, but I did NOT include the IP address in local domains in Mercury core.&nbsp;should I put it in like this:Local Host or server&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Internet Name ----------------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--------------------- domain1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;domain1 domain1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; domain1.com domain1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mail.domain1.com domain2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [192.168.x.x] &nbsp;

jbrowne

posted Oct 27 '10 at 9:57 pm

that did not work -because MercuryC still tries to deliver the message.

that did not work -because MercuryC still tries to deliver the message.&nbsp;&nbsp;

Rolf Lindby

posted Oct 28 '10 at 12:04 am

A local domain change will probably require a restart of Mercury. If it still doesn't work, please post the relevant part of the core log.

Unless you are in a Netware environment the left part of the local domain definition should always be the same (it's actually ignored otherwise, but to avoid confusion it's usually better to just use one name).

/Rolf

A local domain change will probably require a restart of Mercury. If it still doesn't work, please post the relevant part of the core log.Unless you are in a Netware environment the left part of the local domain definition should always be the same (it's actually ignored otherwise, but to avoid confusion it's usually better to just use one name)./Rolf

jbrowne

posted Oct 29 '10 at 9:48 pm

Could I do this?

Could I have a second Mercury install, that POPs a domain mailbox from my original Mercury?

And then have this second Mercury forward with mercuryE to the server I'm trying to reach internally?

Could I do this?&nbsp;Could I have a second Mercury install, that POPs a domain mailbox from my original Mercury?&nbsp;And then have this second Mercury forward with mercuryE to the server I'm trying to reach internally?&nbsp;&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history