Happening twice a week with an update to PureMessage the users stop receiving external emails. Looking through the application log I see PME warnings. Run the exchange command to stop using the pure message transport and the mail starts flowing again. This has happened on 3 separate sites today, anyone else seeing this issue becoming a regular occurrence?
Magnus
Hi Magnus,
From what you are describing your best bet is to open a support case and run the SDU tool on one (or all) of your SBS's .. This will collect debug information for a support case. If your also able to submit those warnings to your case that will help with your case.
The forums can offer some help but for this case were going to need to see and get a pile of logs that should not be posted in a public forum.
I know I had PME running on 2011 SBS at one point in time and I did not have any issues.. My immediate thought is some sort of update issue or permissions / ad issue.. these should be fairly apparent with that SDU logging tool.
Hi Magnus,
From what you are describing your best bet is to open a support case and run the SDU tool on one (or all) of your SBS's .. This will collect debug information for a support case. If your also able to submit those warnings to your case that will help with your case.
The forums can offer some help but for this case were going to need to see and get a pile of logs that should not be posted in a public forum.
I know I had PME running on 2011 SBS at one point in time and I did not have any issues.. My immediate thought is some sort of update issue or permissions / ad issue.. these should be fairly apparent with that SDU logging tool.
We had an case opened for the same issue on SBS2011 for two customers. No real help came out of it.
Stopping SMTP Scan in PureMessage seems to have stopped the issues on one server, while on another the mailflow now stops with event 1009 MSExchangeMailSubmission from time to time.
Best greetings from Germany
Olaf
Hi Olaf
This may have been caused by a MS update.. You may want to check and see if this monthly roll-out was applied to the server. https://support.microsoft.com/en-ca/help/4338818/windows-7-update-kb4338818 pertains to your case.
ensure you have a complete backup before trying any of the following.
#1 check and see if the roll-out was installed (or if there is a "server" version of it) if it was, remove it and re-test.
#2 Check out the registry and make sure the associated package is installed?
#3 You could try also try un-installing and reinstalling puremessage.
#4 another thing you could try is enabling protocol logging (I have NOT tested this.. I'm a UNIX guy more so than a windows guy) but this looks like it may be useful to try
https://docs.microsoft.com/en-us/exchange/mail-flow/connectors/configure-protocol-logging There may be other debug logs you can enable on widows servers as well.
#5 if the server is in this state, you could also try some relay and telnet tests as well .. for example relay an eicar antivirus string and see if the message reaches the quarantine, or what smtp codes you get when trying to relay mail.
hopefully with enhanced debugging and an active sdu log you should be able to get enough information to see whats going on.
Im seeing this at least once a month on our SBS2011 servers. (4 separate clients). Their Outlook crashes, email stuck in the outbox and no incoming email. Only fix is to set Puremessege services to disabled and reboot the server. Then leave for a day until new updates for Pure Messege comes out. Not ideal and clients losing faith in the product.
Magnus
Hum,
I've never herd of behavior like that. I have seen instances where puremesasage and the transport service will not cooperate. But that has never been consistently regular and certainly would not require a reboot + a day of recovery.. That seems very odd at best.
Were any of these servers upgraded from 2003/8 to 2011?
The weird part here is that puremessage is only a filter.. It in no way impacts wither a message is delivered or not (unless its quarantined/deleted) The transport service and networking infrastructure is responsible with accepting/delivering all mail to and from clients and exchange. Filters can only affect messages that are delivered.
one thing you can do if this happens again is relay a message via telnet and see what happens . (ie is the connection made? is it rejected? or can you relay a message) if so is it internal to internal or intern to external etc ect.
something like:
Telnet address 25
Helo localhost
Mail from: myaccount@test.com
Rcpt to: youraccount@test.com
DATA
Subject: test from workstaion
From: test@test.com
ENTER MESSAGE
(blank line)
.
shift+}
Your best bet is to enable that verbose logging combined with the SDU and transport logs then open a case with support. I would also include your account manager and let him/her know your concerns/difficulties. (your license probably includes the virtual email appliance, ask them about an activation code and details.. perhaps the SEA will be a better solution for your environment)
Yes servers were upgraded from SBS2003. Happening Once a week now and client has asked for alternative software as cant afford downtime.
Symptoms:
Users email crashes, takes 15minutes to get email sent. Server has PureMessage just completed an update and IIS services stuck on stopping. Have to set PureMessage services to disabled and reboot server, mail flow then working as normal.
Magnus
