Email Winsock2 Error

[Drumcode2003]

When I try to send emails via the test button I got the following error message:

Failed to send test email message.
Error description: Invalid winsock2 socket.

Can anybody help me?

[Vitaliy S.]

Hello Sepp,

Judging by the error it seems like you've failed to connect your mail server, so could you try to telnet to the mail server using the same parameters (DNS name and port) you've specified in the application. Are you successfull with that?

Thank you!

[Drumcode2003]

Hi,

yes, of course, telnet to mailserver via port 25 works fine from veeam server.
Also with authentication the test email function doesn't work for me.
Any hints?

thx

[Gostev]

Sepp, this sounds like environment-specific issue - as this functionality works fine for all other customers. If you are using licensed version of Veeam Monitor, please feel free to open support case with us and we will be happy to troubleshoot this further for you.

[itwerx]

I've got the same problem. Can telnet to the mail server's port 25 from the Monitor machine and send a message no problem with the same From and To addresses but the Monitor test button gives that error.
Is it perhaps a restriction of the free version? Guessing not as there doesn't seem to be any mention of that and the Scheduler, (which is disabled in the Free version), pops up a nice message explaining why it's not going to work.
Anybody else seen/solved this?

[Vitaliy S.]

Hello,

There are no such restrictions in a free version of Monitor, could you tell us please if you are using Authentication while trying to send test emails?

[itwerx]

Hello,

There are no such restrictions in a free version of Monitor, could you tell us please if you are using Authentication while trying to send test emails?

Tried both with and without Authentication. (Authentication is not actually required from that subnet).

[Vitaliy S.]

I've tried to confirm your issue, but had no luck. However I've just thought as all emails are sent by the Monitor service, could the issue be related to the account stated in the logon info?