From: | James |
---|---|
Date: | 10/1/19 4:28 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
Hi Techs/ Devs, Been a long time, hope your all well. Quick one for you, I'm not too sure if it's by design or if there is an option to add to the server.properties file but I need a way to not have emails accumulate in users folders after the primary server is back up. Let me explain further; Primary Server = mx record highest priority Secondary Server = mx record lowest priority So as per the above all the emails are coming through to the primary server fine. Now if we stop the Xeams service on the primary server the second server handles mail fine - all good. Now as the downstream server is the Primary server once the Primary server comes up all emails empty from the outbound queue back into the Primary server fine so all good there too. That is as far as we need the setup to be. Presently all emails remain stored in the user folders on the secondary server even if they all get delivered to the primary server when it is back up. Is there a setting I can apply to simply delete all emails from user folders once the downstream (primary) server is back up and all the outbound queue has been flushed? Many Thanks, James |
|
Top |
From: | James |
---|---|
Date: | 10/1/19 4:34 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
Just building up on the above slightly; Primary Server is in firewall mode Clustering is not in use as it brings no real benefit or solution to the objective in question (flushing emails from secondary server). Thanks, James |
|
Top |
From: | Synametrics Support |
---|---|
Date: | 10/1/19 4:44 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
James, Something does not add up. Why is your Primary running in "Firewall" and the Secondary in "Stand alone"? Is there any other server AFTER the primary? Could please confirm if the following image is correct:
If the above flow is correct, both should be in Firewall Mode and you can set the Message Retention period to a small value (let's say 10 days). In this case, Xeams will automatically delete messages after 10 days.
|
|
Top |
From: | James |
---|---|
Date: | 10/1/19 7:12 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
Hi, Yes, the image is spot on. The Secondary only ever gets email when the primary is down due to MX records. But if the Secondary is in firewall mode how is Xeams going to accept the message in the first place if the Primary server is down since it only proxies the connection? I was under the impression that in firewall mode the secondary server (exchange) MUST be up? Hence if the Primary Xeams server is down how will the Secondary Xeams server connect to it to proxy the connection?
Many thanks.
|
|
Top |
From: | Anonymous |
---|---|
Date: | 10/1/19 7:15 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
Another thing to note; if the Secondary server is in Firewall mode, how would it check with AD to make sure the user exists? The whole Primary site is down? Do you mean by creating users in firewall mode and rejecting unknown users? I thought Firewall mode only works on a proxy basis? |
|
Top |
From: | Anonymous |
---|---|
Date: | 10/2/19 8:53 AM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
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. 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 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. I hope that makes things clearer. Thanks! |
|
Top |
From: | James |
---|---|
Date: | 10/2/19 11:47 AM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
<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. 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 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. I hope that makes things clearer. Thanks! |
|
Top |
From: | Synametrics Support |
---|---|
Date: | 10/3/19 9:57 AM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
James, From your description, I gather there is a confusion between Modes (Stand-alone, Hybrid, Firewall) and Server types (SMTP Proxy and Regular SMTP). These are two different concepts and you don't have to use the SMTP Proxy server when using Xeams in Hybrid/Firewall mode. I see you're using the SMTP Proxy server on both Primary and Secondary MX. That is the reason why you get Server Temporarily out of service when the next server is down. This is what I recommend:
This will meet both of your requirements. Additionally, I recommend you run Xeams in Clustering mode. What is the reason for not using this feature? This will have additional benefits:
|
|
Top |
From: | James |
---|---|
Date: | 10/3/19 12:24 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
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] 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. However;
James |
|
Top |
From: | Synametrics Support |
---|---|
Date: | 10/4/19 7:01 AM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
You wrote:
This will only happen when Xeams is running in Hybrid Mode. Switch it from Hybrid to Firewall mode and it won't make a copy too *.hdr or *.xdt
|
|
Top |
From: | James |
---|---|
Date: | 10/4/19 12:03 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
Ok, I will give it another try and see (although I have explained above a few times that the server is already in SMTP Server / Firewall Mode and not Hybrid mode) Many Thanks, James |
|
Top |
From: | Synametrics Support |
---|---|
Date: | 10/4/19 12:15 PM |
Topic: | Hybrid Setup |
Type: | General Discussions |
Post a follow up |
James, If you use Clustering, users will be synchronized by Xeams. However, if you don't use Clustering, you will have to create users on the secondary Xeams manually. Now since you don't have access to AD from the secondary Xeams, I recommend you create local users and NOT use AD for authentication. This way both Xeams will detach themselves from AD and they will work. |
|
Top |