Community Discussions and Support
Mercury/32 SMTP to internal server?

Found a workable solution!

 

Ended up using the daemon MercuryForward by Petr Jaklin - has been running like a champ for three different domains.  

<p>Found a workable solution!</p><p> </p><p>Ended up using the daemon MercuryForward by Petr Jaklin - has been running like a champ for three different domains.  </p>

I use MercuryS & MercuryE currently but found I need to forward messages to another internal mail server. Can this be done with a rule or is there a means of using Mercury's SMTP to accomplish this?

I use MercuryS & MercuryE currently but found I need to forward messages to another internal mail server. Can this be done with a rule or is there a means of using Mercury's SMTP to accomplish this?

Yes, but the devil is in the details (which you should provide :) )

Rules can be used to select messages to forward via SMTP

What is the network topography?

Do you have a local DNS server?

 

<p>Yes, but the devil is in the details (which you should provide :) )</p><p>Rules can be used to select messages to forward via SMTP </p><p>What is the network topography?</p><p>Do you have a local DNS server?</p><p> </p>

Mixed environment network (NetWare, M$, Linux), all servers on same subnet. Local DNS, DHCP, LDAP, etc. Just looking for a way to forward selected messages to an internal SMTP server.

Mixed environment network (NetWare, M$, Linux), all servers on same subnet. Local DNS, DHCP, LDAP, etc. Just looking for a way to forward selected messages to an internal SMTP server.

the separate smtp server needs to have it's own domain/mx, then you can forward via rules selected messages.

If you're looking at more advanced forwarding, you have to use mxredir daemon, that can be used for a single user as their rule. The to header is then re-written to that domain, and the message is routed off host via MercuryE.

I'd use the first option if that is possible.

<P>the separate smtp server needs to have it's own domain/mx, then you can forward via rules selected messages.</P> <P>If you're looking at more advanced forwarding, you have to use mxredir daemon, that can be used for a single user as their rule. The to header is then re-written to that domain, and the message is routed off host via MercuryE.</P> <P>I'd use the first option if that is possible.</P>

Thanks Peter -

 

If these were serving mail for different domains, your solutions might have worked. I think I will have to go with something like  http://www.novell.com/coolsolutions/feature/7180.html unfortunately...

 

Maybe I can set up a "dummy" domain on the GW box to test a Mercury/32 based solution. I want to keep Mercury going for the same reasons that are listed in another thread http://community.pmail.gen.nz/forums/thread/6759.aspx - but based on the recommendations, a POP solution for the second server is the better way to go.

 

 

<p>Thanks Peter - </p><p> </p><p>If these were serving mail for different domains, your solutions might have worked. I think I will have to go with something like  <a href="http://www.novell.com/coolsolutions/feature/7180.html" title="POP-Forwarding Agent" target="_blank" mce_href="http://www.novell.com/coolsolutions/feature/7180.html">http://www.novell.com/coolsolutions/feature/7180.html</a> unfortunately...</p><p> </p><p>Maybe I can set up a "dummy" domain on the GW box to test a Mercury/32 based solution. I want to keep Mercury going for the same reasons that are listed in another thread <a href="http://community.pmail.gen.nz/forums/thread/6759.aspx" title=" mxredir.dll" target="_blank" mce_href="http://community.pmail.gen.nz/forums/thread/6759.aspx">http://community.pmail.gen.nz/forums/thread/6759.aspx</a> - but based on the recommendations, a POP solution for the second server is the better way to go.</p><p> </p><p> </p>

How about just doing a user@[192.168.x.x] type forwarding to the other host via a rule.  You need no DNS when using literal addressing. 

FWIW, I run Mercury/32 as a gateway for three separate domains served by both Linux and Novell mercury installations.  I use domain account and one server pulls the mail via MercuryD and the other i push via a batch file and simple BASIC program.

<p>How about just doing a user@[192.168.x.x] type forwarding to the other host via a rule.  You need no DNS when using literal addressing.  </p><p>FWIW, I run Mercury/32 as a gateway for three separate domains served by both Linux and Novell mercury installations.  I use domain account and one server pulls the mail via MercuryD and the other i push via a batch file and simple BASIC program. </p>

I tried that, Thomas - it kept failing delivery on me. I don't have a user account set up on the GW box - maybe that is my problem.

 

Tried again with a user account on the GW box - MercuryE gives me a Permanent Error 110001 (non-existent host or domain) resolving X.X.X.X

I have MercuryE performing DNS lookups on my internal DNS server (as its primary). I can telnet from Mercury/32 to port 25 on the GW server and get a 220 ready response...

 

I had to set up an MX record for the GW box (and set the exchanger to the GW IP address) and my forward was set to username@GWservername.local.domain.

 

...Find that everything works as I hoped EXCEPT for BCC do not forward (probably because they are not in the headers of the inbound message).

How could you forward the BCCs as well?

 

 

<p>I tried that, Thomas - it kept failing delivery on me. I don't have a user account set up on the GW box - maybe that is my problem.</p><p> </p><p>Tried again with a user account on the GW box - MercuryE gives me a Permanent Error 110001 (non-existent host or domain) resolving X.X.X.X</p><p>I have MercuryE performing DNS lookups on my internal DNS server (as its primary). I can telnet from Mercury/32 to port 25 on the GW server and get a 220 ready response... </p><p> </p><p>I had to set up an MX record for the GW box (and set the exchanger to the GW IP address) and my forward was set to username@GWservername.local.domain.</p><p> </p><p>...Find that everything works as I hoped EXCEPT for BCC do not forward (probably because they are not in the headers of the inbound message). </p><p>How could you forward the BCCs as well? </p><p> </p><p> </p>

...Find that everything works as I hoped EXCEPT for BCC do not

forward (probably because they are not in the headers of the inbound

message).

How could you forward the BCCs as well?

Can't unless the Bcc: SMTP address is in the header someplace.  If you are receiving the mail via SMTP then in many cases you can use an alias for the SMTP RCPT TO:  email address and point it to the other server.  If receiving from a POP3 "domain" type account the ISP may have added a header showing the original RCPT TO: address that you can use.  You can't use the X-Delivered-To: header added by mercury/32 though.

 

<blockquote><p>...Find that everything works as I hoped EXCEPT for BCC do not forward (probably because they are not in the headers of the inbound message). </p></blockquote><blockquote>How could you forward the BCCs as well?</blockquote><p>Can't unless the Bcc: SMTP address is in the header someplace.  If you are receiving the mail via SMTP then in many cases you can use an alias for the SMTP RCPT TO:  email address and point it to the other server.  If receiving from a POP3 "domain" type account the ISP may have added a header showing the original RCPT TO: address that you can use.  You can't use the X-Delivered-To: header added by mercury/32 though. </p><p> </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft