Hi,

Thanks for getting back to me.

There seems to be a slight misunderstanding. Let me clarify a little bit more;

1) The Primary Xeams server is in SMTP proxy / Firewall mode - this is because Exchange sits behind it and users connect to Exchange for outbound sending [smart hosts is not an option]
2) The secondary Xeams server is already in SMTP server mode with the Spam firewall enabled however; This server isn't in the same location as the primary server. So;

When email doesn't get through to the Primary server because of an mx timeout on the connection, it will immediately try the second mx which is the Xeams server at the remote site.
The other Xeams server receives the email and filters it fine and the settings used are Server Mode = SMTP / Server Type = Firewall and Domain = the Primary Xeams server IP.

However;
I have changed the outbound queue time to 5 minutes so the secondary Xeams server is constantly trying to push it to the primary site. From what I understand I will need to create the same users that exist on the Exchange server at Secondary Xeams SMTP server for licensing and rejection of unknown users as accepting all users would cause licensing issues and obviously AD cannot be reached as the Primary site is down etc. So I have done this.

The issue is when you look at the user folders on the secondary Xeams server you will find that every time an email arrives for that user the inbox.hdr or .xdt (I cant remember) grows a little
A filtered copy is also stored in the outbound queue waiting to be pushed back to the Primary server. I have set this to 5 minutes so that's no issue.

The objective is that when emails arrive at the Secondary site, they are not copied once to the user folder and once to the outbound queue - they only need to go to the outbound queue as those folders (inbox, sent, junk, etc.) will never be accessed. Users ONLY connect to the local exchange server on the primary site. The Secondary Xeams server also never connects to Exchange either. It simply forwards email to the Primary Xeams server. The Secondary Xeams server cannot connect to the Exchange server anyway because the NAT connection and FW rules can only forward port 25 to ONE device which happens to be the Primary Xeams server, so the Primary Xeams server MUST be the first point in for all other remote Xeams installations anywhere in the world which then forwards to the Exchange server.

I could be wrong here but maybe the user folders automatically get emptied after a given time?

I hope that makes it a little clearer.   Many many thanks.

James