email notification broken

[Xavier]

Hello,

the emails stopped arriving when check ins are done and item changes are done (This Fortress client is version 1.1.4.18402). I'm unsure if it appeared since the upgrade or nor (it fails for 10 days).
I've tried both auth SMTP and no authentication (though it seems to remember the auth user/password), none works. I've been through the debug logs, but cannot see e-mail notification (only loading email settings when I go the fortress setup page).

I've read in another post that debug logs could help: I do not see how.

Emails failed to arrive when first installed. I do not why it started working. And Why it now fails.

I'm wathcing the $ node. After a checking :

----22/12/2008 13:32:41 --()-- Exception in plugin thread : Impossible de se connecter au serveur distant
----22/12/2008 13:32:41 --()-- Exiting plugin thread

(Faild to connect to remote server).

I'm afraid there is a password issue/Auth mode or not (I've tried a non authenticated server, but it doesn't seem to take into account the fact that the server is not authenticated - as the SMPT user with password is displayed after saving them with empty text).

We do not have the server in our office, how can I check that ?

[Xavier]

Hello

I've found JBMail that helped me check the parameters. I can send e-mails with the authenticated server and non-authenticated server.

How can I fix the mail settings of the server ? Have more info on what exactly fails ?

[Beth]

Go into your Vault client and look in the email configuration tab at the bottom. Is that still configured correctly?

Is no one receiving emails?

What account is sending the emails? Is it a valid email address also?

[Xavier]

No one receive e-mails (since the upgrade from 1.1.3 to 1.1.4 but it's very difficult to be sure it took some time to notice).

The email address (the sender) was not valid, but never has been : It helps detect when it's an e-mail from fortress.

This is major change from the former version. A notice would have been welcome. Moreover the logs are very surprising : Failed to connect to remote server !

Could you please confirm that is why it failed. I find it surprising and this is very important for us to be sure that the problem is fixed as we use it to be informed of customer's bugs report.

Thanks for your help

[Beth]

It's not a change. My experience has been that real from addresses are more likely to get through, which is why I made the suggestion.

Being that it was working before, you could take a look at your Event Viewer logs on your Vault server and Vault client. That might give more clue as to why your email notifications are failing.

[Xavier]

The change might then be from our mail provider...
Many thanks for the hint.

[Xavier]

more feedback:

The

'Exception in plugin thread: Cannot connect to remote server

' is still here even when the mail arrives. How can I know where this error comes from ? (After a check in)
I also have

----24/12/2008 12:31:18 --www.routerlogin.com(192.168.0.1)--SSL Enabled AuthTokenHash matched, but couldn't get the userid

from time to time.

I've created a dummy mail account with the right address, but it now fails. The logs are the same, and can connect to the server send/receive mails with this account. Could you please help me figure what is wrong. Using a different account is really better for filtering.

I've tried to change only SMTP Auth User or FromAddress, but it fails all the time as soon as I change one of the parameter. Is it possible there is some conflict elsewhere ?

[Xavier]

OK, this is our mail host that fails. The mails I sent to test worked because they were sent to the sender.. bad luck.

However , could you have a look at those 2 errors that seems unrelated:

'Exception in plugin thread: Cannot connect to remote server

' is still here even when the mail arrives. How can I know where this error comes from ?
I also have

----24/12/2008 12:31:18 --www.routerlogin.com(192.168.0.1)--SSL Enabled AuthTokenHash matched, but couldn't get the userid

from time to time.

[Beth]

I had accidentally broken my own as well on one of my test machines. How I fixed it was I removed all the email settings in the admin page except for the port and the server URL. I saved it that way and performed an iisreset by going to Start - Run and typing iisreset. That made it clear those settings entirely out of the cache on the server. Then I returned and set it up again.

After that, I went to my client and did the same on the email tab. I removed my settings, saved it, closed Vault, then reopened and set it up again.

Give that a try.