E-Mail Forwarders and MailFoundry

J

justadollar

Verified User
Joined
Dec 8, 2004
Messages
21
This may be a bit of an odd question, but I hope somebody can give me a hand.

I have an old domain (well call it olddomain.com for kicks) that I am no longer using. I do however still receive the odd mail or two that I wish to keep on it.

I also have a new domain (newdomain.com) that I have began protecting with mailfoundry.

Now in an effort to get some protection on my old domain, I have forwarded all e-mail from olddomain.com to newdomain.com from DirectAdmin. More to the point I have forwarded it to my mail e-mail account on newdomain.com

olddomain.com is on my admin account, so I have done this via a catchall for olddomain.com forwarded to my main account on newdomain.com as well as a seperate forwarder for [email protected]

The mail is forwarded no problem; however, it appears that it is not being run through mailfoundry. I have contacted them and they say the issue is most likely that the e-mail is being forwarded directly to the account within the server.

My question (after that longwinded post) is:

When a forwarder is setup on DA, does the mailserver send the e-mail directly to the account (i.e. stays just within the server), or does it send the e-mail as anybody else would (looking up the MX records for the domain and sending it along there).

Thanks in advance.
 
They're right. The way to resolve the problem:

First make sure the user has DNS control.

Second look for the MX Records link on the DirectAdmin main screen for newdomain, and follow the instructions there to turn off mail on the server for the newdomain account.

Jeff
 
Hey Jeff,

Thanks for the quick reply. I gave turning off the mail server for newdomain.com a try; however, that doesn't work. The way mailfoundry is setup (I should probably have mentioned this in my first e-mail) is that all mail is still hosted on your machine.

You change your mx records to point to mailfoundry's machines (which I have done), and as such mail sent to your domain is then forwarded over to the mailfoundry machines. After it goes through their tests, it is then sent to your server.

I did a few quick tests with gmail after unchecking "Use this server to handle my emails." and this was the resulting message:

Code: 
Unable to deliver message to: <[email protected]>
Delivery failed for the following reason:
Server mail.newdomain.com[123.123.123.123] failed with: 550 authentication required


This has been a permanent failure.  No further delivery attempts will be made.

newdomain.com is being filtered just fine through mailfoundry. I've been looking over the exim.conf file for a while now trying to find out how to make it treat all forwared e-mail as non-local mail even when it is local (or at least in the instance of olddomain.com).
 
Just another quick tidbit, it appears that when I had the checkbox unchecked (preventing the server from handing the mail for newdomain.com) that it did indeed work as I had intended.

I have a spare VPS and I think I may just move the domain over to it and then forward all e-mail over to newdomain.com from there.
 
Gave soemthing else a try. Popped open exim.conf and tried a custom router:

Code: 
mfoundry
   drive = dnslookup
   domains = olddomain.com
   transport = remote_smtp

That sadly didn't work. I got the "lowest numbered MX record points to local host" error as the mx record for oldodmain.com is indeed the localhost (or rather an IP on the machine).

/me keeps digging
 
And just to add a final solution, be it an ugly one:

Forward all mail from olddomain.com to a gmail account
Forward all mail from gmail account to newdomain.com
That mail gets passed through MailFoundry
It then gets fowarded to newdomain.com all clean
 
Exim just looks for any domain that is local. If so, there is no need to look for a mx record...
 
You must log in or register to reply here.
Back
Top