Catch all overrides virtual domain alias to external account

Lord Neckbeard · 13th June 2012, 09:05 AM

I have a business account at Fastmail and one virtual domain (targetdomain.com) is giving me The Troubles. I need to "split" targetdomain.com so messages for some aliases go to Google Apps, but also have a catch all that should go to biff@maindomain.com (this is the main domain using Fastmail).

For example, hoss@targetdomain.com should go to hoss@apps.targetdomain.com, and *@targetdomain.com should go to biff@maindomain.com. This works fine with another virtual domain that does not use a catch all. However, when the catch all is active it receives messages for hoss@targetdomain.com and sends them to biff@maindomain.com instead of hoss@apps.targetdomain.com.

How can I get this to work?

The header shows some interesting info:

Code:

X-Resolved-to: biff+hoss@maindomain.com
X-Delivered-to: hoss@targetdomain.com

I am not using any plus addressing in my aliases. The rest of the header looks normal, but I can supply it if needed.

My DNS info for targetdomain.com:

Code:

targetdomain.com     86400     A           <web server ip address>
webmail.targetdomain.com     CNAME           ghs.google.com
www.targetdomain.com         CNAME           targetdomain.com
targetdomain.com                 MX     priority: 10     in1-smtp.messagingengine.com
targetdomain.com                  MX     priority: 20     in2-smtp.messagingengine.com
apps.targetdomain.com         MX     priority: 20     alt1.aspmx.l.google.com
apps.targetdomain.com         MX     priority: 20     alt2.aspmx.l.google.com
apps.targetdomain.com         MX     priority: 10     aspmx.l.google.com
apps.targetdomain.com         MX     priority: 30     aspmx2.googlemail.com
apps.targetdomain.com         MX     priority: 30     aspmx3.googlemail.com
apps.targetdomain.com         MX     priority: 30     aspmx4.googlemail.com
apps.targetdomain.com         MX     priority: 30     aspmx5.googlemail.com
targetdomain.com         TXT           v=spf1 a include:spf.messagingengine.com include:_spf.google.com ~all
targetdomain.com         NS           ns1.geodns.net
targetdomain.com         NS           ns2.geodns.net

This is all because one co-worker wants a catch all for his personal domain and his family members want to stay with Google Apps.

n5bb · 13th June 2012, 12:31 PM

Welcome to the EMD Forums!

The Virtual Domains screen controls how messages sent to aliases at your own domain are delivered.

Specific aliases can be set to target your Fastmail Inbox (normal address), a Fastmail folder (using plus addressing) or an external account. If you use multiple addresses, separate them with a comma.
It appears to me that you don't have your Virual Domain screen alias targets set up correctly,
Please note that when you create a new Virtual Domain alias, a warning is displayed at the top of the screen that states that there may be a 15 minute delay before your changes are made active.
Below the alias list you should see your domain listed with several columns. The DNS column should display US, which indicates that your domain MX records are properly pointing to the Fastmail receiving servers.

Bill

Lord Neckbeard · 14th June 2012, 07:16 AM

Quote:

Originally Posted by n5bb

Welcome to the EMD Forums!

Thank you for the reply.

Quote:

Originally Posted by n5bb

It appears to me that you don't have your Virual Domain screen alias targets set up correctly,

Here are the aliases:

Code:

name	domain			target
cletus	@targetdomain.com	cletus@hotmail.com
daisy	@targetdomain.com	daisy@hotmail.com
info	@targetdomain.com	daisy@hotmail.com
hoss	@targetdomain.com	hoss@apps.targetdomain.com
darlene	@targetdomain.com	darlene@apps.targetdomain.com
*	@targetdomain.com	biff@maindomain.com

Quote:

Originally Posted by n5bb

Please note that when you create a new Virtual Domain alias, a warning is displayed at the top of the screen that states that there may be a 15 minute delay before your changes are made active.

Good to mention, but I did see this.

Quote:

Originally Posted by n5bb

Below the alias list you should see your domain listed with several columns. The DNS column should display US, which indicates that your domain MX records are properly pointing to the Fastmail receiving servers.

Yes, these are indicated as US.

lane · 14th June 2012, 10:19 AM

I have had a little trouble in this situation as well, though at least I was getting redirection OK to Google Apps.

Where Bill mentions "Below the alias list you should see your domain (targetdomain.com) listed with several columns," be sure that the column marked "Routing" is set to "Force Ext". When this is set correctly, and email is sent to targetdomain.com or apps.targetdomain.com, Fastmail looks up the current MX server for targetdomain.com or apps.targetdomain.com respectively using the official nameservers (in your case, external ones), and will see that targetdomain.com resolves to Fastmail and apps.targetdomain.com resolves to Google Apps. This is exactly what I did for a while (except I called it ga.targetdomain.com, for ga="Google Apps").

I did find one problem with this - the SRS rewrite of the envelope sender did not occur when forwarding to Google Apps. See discussion in this thread, starting with my 3 June post, and its resolution. In the end, I used an entirely separate domain to point to Google Apps, rather than a subdomain like apps.targetdomain.com, just to get SRS working correctly. I happened to have one handly, not used at the moment for another purpose. But if you don't care about SRS, your approach be able to be made to work.

-- Lane

Lord Neckbeard · 30th June 2012, 05:44 AM

Thank you for the insight. What fixed this issue for me was changing "Subdomain? a@b.dom as" from "Yes, swap: b+a@dom" to "No, reject". Leaving "Routing" as "Auto (Int)" seems to work fine.

13th June 2012, 09:05 AM	#1
Lord Neckbeard Junior Member Join Date: Jun 2012 Posts: 3	[SOLVED] Catch all overrides virtual domain alias to external account I have a business account at Fastmail and one virtual domain (targetdomain.com) is giving me The Troubles. I need to "split" targetdomain.com so messages for some aliases go to Google Apps, but also have a catch all that should go to biff@maindomain.com (this is the main domain using Fastmail). For example, hoss@targetdomain.com should go to hoss@apps.targetdomain.com, and @targetdomain.com should go to biff@maindomain.com. This works fine with another virtual domain that does not use a catch all. However, when the catch all is active it receives messages for hoss@targetdomain.com* and sends them to biff@maindomain.com instead of hoss@apps.targetdomain.com. How can I get this to work? The header shows some interesting info: Code: X-Resolved-to: biff+hoss@maindomain.com X-Delivered-to: hoss@targetdomain.com I am not using any plus addressing in my aliases. The rest of the header looks normal, but I can supply it if needed. My DNS info for targetdomain.com: Code: targetdomain.com 86400 A <web server ip address> webmail.targetdomain.com CNAME ghs.google.com www.targetdomain.com CNAME targetdomain.com targetdomain.com MX priority: 10 in1-smtp.messagingengine.com targetdomain.com MX priority: 20 in2-smtp.messagingengine.com apps.targetdomain.com MX priority: 20 alt1.aspmx.l.google.com apps.targetdomain.com MX priority: 20 alt2.aspmx.l.google.com apps.targetdomain.com MX priority: 10 aspmx.l.google.com apps.targetdomain.com MX priority: 30 aspmx2.googlemail.com apps.targetdomain.com MX priority: 30 aspmx3.googlemail.com apps.targetdomain.com MX priority: 30 aspmx4.googlemail.com apps.targetdomain.com MX priority: 30 aspmx5.googlemail.com targetdomain.com TXT v=spf1 a include:spf.messagingengine.com include:_spf.google.com ~all targetdomain.com NS ns1.geodns.net targetdomain.com NS ns2.geodns.net This is all because one co-worker wants a catch all for his personal domain and his family members want to stay with Google Apps. Last edited by Lord Neckbeard : 30th June 2012 at 05:44 AM.

13th June 2012, 12:31 PM	#2
n5bb Intergalactic Postmaster Join Date: May 2004 Location: Irving, Texas Posts: 6,025	Welcome to the EMD Forums! The Virtual Domains screen controls how messages sent to aliases at your own domain are delivered. Specific aliases can be set to target your Fastmail Inbox (normal address), a Fastmail folder (using plus addressing) or an external account. If you use multiple addresses, separate them with a comma. It appears to me that you don't have your Virual Domain screen alias targets set up correctly, Please note that when you create a new Virtual Domain alias, a warning is displayed at the top of the screen that states that there may be a 15 minute delay before your changes are made active. Below the alias list you should see your domain listed with several columns. The DNS column should display US, which indicates that your domain MX records are properly pointing to the Fastmail receiving servers. Bill

14th June 2012, 10:19 AM	#4
lane Cornerstone of the Community Join Date: Dec 2005 Location: Kars, NB, Canada Posts: 547	I have had a little trouble in this situation as well, though at least I was getting redirection OK to Google Apps. Where Bill mentions "Below the alias list you should see your domain (targetdomain.com) listed with several columns," be sure that the column marked "Routing" is set to "Force Ext". When this is set correctly, and email is sent to targetdomain.com or apps.targetdomain.com, Fastmail looks up the current MX server for targetdomain.com or apps.targetdomain.com respectively using the official nameservers (in your case, external ones), and will see that targetdomain.com resolves to Fastmail and apps.targetdomain.com resolves to Google Apps. This is exactly what I did for a while (except I called it ga.targetdomain.com, for ga="Google Apps"). I did find one problem with this - the SRS rewrite of the envelope sender did not occur when forwarding to Google Apps. See discussion in this thread, starting with my 3 June post, and its resolution. In the end, I used an entirely separate domain to point to Google Apps, rather than a subdomain like apps.targetdomain.com, just to get SRS working correctly. I happened to have one handly, not used at the moment for another purpose. But if you don't care about SRS, your approach be able to be made to work. -- Lane

30th June 2012, 05:44 AM	#5
Lord Neckbeard Junior Member Join Date: Jun 2012 Posts: 3	Thank you for the insight. What fixed this issue for me was changing "Subdomain? a@b.dom as" from "Yes, swap: b+a@dom" to "No, reject". Leaving "Routing" as "Auto (Int)" seems to work fine.