<Repeated below mistakenly posted as Anonymous earlier>

Hi again,

Just to confirm that I have tested your setup and as expected it doesn't work. Telnetting the port or emailing the server returns Xeams Server Temporarily out of service (you cant proxy if your primary xeams is down).

I think there is a misunderstanding. Let me further clarify;

TTL = 0 [mx1.test.com - xxx.xxx.xxx.xxx] -----> Primary Xeams in firewall mode -------> to Exchange

Now if the entire primary "site" is down which includes the internet connection, the BELOW applies AND WORKS;

TTL = 10 [mx2.test.com - yyy.yyy.yyy.yyy]  ----> Secondary Xeams (email stored in User folder AND outbound queue)

WHEN Primary Site is back up the BELOW applies;

Secondary Server attempts connection to Primary site every 5 minutes (Outbound Queue setting) ---> Primary Xeams in firewall mode back online ---> Proxy to Exchange

The above setup works Perfectly however when the email comes into the secondary server it is stored twice, once in the outbound queue waiting to be pushed to the Primary Firewall mode.
Storing the email in the user folder that is created to measure licensing AND the outbound queue is useless as the user never access the secondary SMTP.  The user access the Exchange name space only and will never see the secondary Xeams server. The only reason a user has an account on the Secondary server is purely for licensing as there is no way to cross check with AD in the Primary site since it is down. So Firewall mode on both servers will simply not work.

What my objective is for the email to arrive at the secondary site (which it does), keep the email in its outbound repository (which it does) WITHOUT storing it in the users folder.
I can understand you will need to create the same users on the Secondary Xeams server for licensing and for the correct accepting of email and have no issues with that.
Its a trivial yet extremely versatile and redundant setup.

I can ask the devs to keep running a nightly script to flush the inbox file but it's a dirty solution to a simple problem - we just either;

a) No storing of the email in user folders and just to keep a copy in the outbound queue after scanning for junk since users will never access the second Xeams machine.
b) Some sort of user retention policy that we can set to delete all email in user folders once the email is successfully passed onto the Primary Xeams server when it is back up.

I hope that makes things clearer.  Thanks!

James