Oh if it wasn't working before, or if they changed to use the vrfy command then this would make sense, we can add a setting to allow vrfy if that's what you want.

    ChrisP.

For our SurgeMail domains our ISP broadband subscriber management system creates the accounts on the EdgeWave.  That was the approached configured to us by our ISP subscriber management system vendor, and it’s worked well.

 

Frank

 

From: surgemail-support [mailto:surgemail-support@netwinsite.com]
Sent: Friday, October 28, 2016 6:26 AM
To: surgemail-list@netwinsite.com
Subject: Re: [SurgeMail List] Mailbox discovery fails between Edgewave and surgemail server

 

That is the normal response from surgemail to a vrfy command, since  it has always responded that way so I don't think that could be the cause of the problem.  I suggest asking your supplier of edgewave how it's supposed to work maybe.

 

ChrisP.

 

 

On 28/10/2016 8:23 p.m., project722 wrote:

We are using an Edgewave Red Condor email security appliance in front of our surgemail 6.3d-71 server on Linux. Noticed today that mailbox discovery stopped working and any new accounts created in surgemail did not propogate over to the Edgewave. Here is what I am seeing in the logs when I try to manually verify from the Edgewave. Logs are from Surgemail.

28 01:48:18.00:-1276654672: smtp:[1.1.1.1] In: starttls
28 01:48:18.00:-1276654672: smtp:[1.1.1.1] Out: 500 Sorry SSL/TLS not allowed from (1.1.1.1)
28 01:48:19.00:-1276654672: smtp:[1.1.1.1] In: noop
28 01:48:19.00:-1276654672: smtp:[1.1.1.1] Out: 250 Command NOOP OK
28 01:48:19.00:-1276654672: smtp:[1.1.1.1] In: vrfy user@domain.com
28 01:48:19.00:-1276654672: smtp:[1.1.1.1] Out: 252 Cannot verify user but will try to deliver
28 01:48:19.00:-1276654672: smtp: Closing connection 1.1.1.1 task took 1 seconds

Anyone know what could be the problem?