Thomas & Dilbert,
Thanks for taking the time to correct my naivety in this matter. I'll take a look at the POP3 connectors, which is where Thomas directed me to in the first place.
Regards,
Richard
Following a suggestion I was given in another thread 'Relay only specified domains', I'm trying to use mxredir.dll.
Does anyone have it working properly? For me it half works, but I may not have the settings right. I'm testing it with two hosts, each running a copy of Mercury. Using fictional addresses and domain names:
MX records for mydomain.net and myotherdomain.net point to 1.2.3.4
HostA
1.2.3.4
Mercury on HostA has mydomain.net as a local domain, for myotherdomain.net, I'm using:
Local host or server = daemon:C:\Mercury\mxredir.dll;[5.6.7.8]
Internet name =myotherdomain.net
HostB
5.6.7.8
Has myotherdomain.net as a local domain
If I send mail to richard@myotherdomain.net, it arrives at HostA, which sends it on to HostB.
However, looking at the SMTP connection history on HostB, the RCPT TO: field has been changed to:
RCPT TO: <richard@[5.6.7.8]>
Is there any way of keeping the correct recipient?
Regards,
Richard
You're correct it's not a proper mxredir - it rewrites the To info, and replaces the just received email into the queue - so it is actually forwarding the email to another domain.
Hmmm, I only briefly tested this with a domain literal address, so I missed this, sorry.
Does it change the "To:" address as displayed in the mail client, or just the smtp envelope RCPT TO: address?
[quote user="dilberts_left_nut"]
Does it change the "To:" address as displayed in the mail client, or just the smtp envelope RCPT TO: address?
[/quote]
I don't know. It never seemed to arrive in my mailbox for me to look at that.
But, I think I've found another way to achieve what I want. Thanks for your mxredir suggestion anyway. It was interesting to play with, even though it didn't work.
Regards
Richard
[quote user="dilberts_left_nut"]What is your solution, just out of interest?
[/quote]
ok. So the problem is that I have an Exchange server hosting domains DomainB.com and DomainC.com. It's on a private address of 10.1.0.2 behind NAT, which has a public address of a.b.c.d . I wanted all the inbound mail for DomainB and DomainC to be relayed through a Mercury server at 10.1.0.3, before reaching the Exchange host, where I could take advantage of SpamHalter, the Content control and Blacklist definitions.
My solution is to run the Mercury server with DomainA as a local domain. The only accounts in DomainA the admin account and spam & nospam for SpamHalter. From the outside world, connecting to port 25 on the firewall, ie a.b.c.d:25 results in a connection to the Mercury server. Incoming SMTP connections cannot connect to the Exchange server. As far as the outside world is concerned, the MX records for all 3 domains refer to a.b.c.d . Mercury is configured to act as an open relay, but, there are Global Filtering rules to theis effect:
If the 'To' field header contains the text '@DomainA.com' Exit from rule processing.
If the 'To' field header contains the text '@DomainB.com' Exit from rule processing.
If the 'To' field header contains the text '@DomainC.com' Exit from rule processing.
If the 'To' field header contains the text '@' Delete the message.
So, the only mail that will survive, will be that that's supposed to be relayed to DomainB or DomainC. Plus, I can send corrections to spam@DomainA.com and nospam@DomainB.com.
The last bit of the setup is that the Mercury host is configured to use a DNS server on the private network which has MX records for DomainB & DomainC refering to 10.1.0.2.
The Exchange server is free to make outbound SMTP connections and can therefore deliver mail to anywhere.
It seems to do what I want, although Thomas says that the filters don't work too well. I'd be interested to know in what situations, if any, they don't work.
Regards,
Richard
[quote user="rhayward"]
open relay, but, there are Global Filtering rules to theis effect:
If the 'To' field header contains the text '@DomainA.com' Exit from rule processing.
If the 'To' field header contains the text '@DomainB.com' Exit from rule processing.
If the 'To' field header contains the text '@DomainC.com' Exit from rule processing.
If the 'To' field header contains the text '@' Delete the message.
So, the only mail that will survive, will be that that's supposed to be relayed to DomainB or DomainC. Plus, I can send corrections to spam@DomainA.com and nospam@DomainB.com.
It seems to do what I want, although Thomas says that the filters don't work too well. I'd be interested to know in what situations, if any, they don't work.
Regards,
Richard[/quote]
This will miss (and delete) any CC'd or BCC'd mail or mail lists etc that don't put the intended recipient in the To: address of the mail headers.
Unfortunately the RCPT TO: envelope header cannot be tested for in filtering rules.
You might be better off using domain mailboxes (set DomainB & C as local to mercury).
Mail that gets through the filters (without being MOVED) and is delivered by core will get an 'X-Envelope-To:' header with the original recipient.
Then you would need the pop connector for Exchange to pull the mail from the domain mailboxes.
The filters do not work when the actual domain is not in the RFC 2822 message headers. In addition, you are only looking at the To: field and the Cc; of Bcc: field may have the address with the domain of interest. For example, mail from the PMail list has the senders email address in the From: field and the PMail list address in the To: field, the receivers address is not in any of the address fields. My domain shows up nowhere in the message except for the X-Envelope-To: added when the mail message is written to the user mailbox and X-Recipient: header added by POPFileD. In this case the RCPT TO: address support@tstephenson.com (and domain) is only available for filtering in the POPFileD added header.
If you were to use Mercury/32 domain mailboxes for the two Exchange server domains then you could have Exchange pull the mail from the Mercury/32 host using one of the many POP3 connectors available to download and deliver the mail to the users. In this case the X-Envelope-To: headers will contain the original RCPT TO: address. I did a Yahoo search on "exchange server POP3 connector" and came up with quite a few. Maybe the latest Exchange server comes with one as well. If the POP3 connector could use this header for delivery the system could do away with all of the filtering .
