Jiwa

We are getting an issue with Jiwa's email system when we use the smtp plugin whith TLS where if the user is not in the Administrators group we are getting an error about the name of the mail server not being able to be resolved.

If the user is in the administrators group everything works as expected which leads me to believe its a permissions issue, has anyone come across something like this before?

By the way nslookup resolves the name of the mail server with no issue.

Is that the JIWA or Windows Administrators group?

Put in a System.Diagnostics.Debugger.Break() at the start of EmailSendBefore() in the plugin and have a look at the values you are getting. You could also wrap the contents of that function in a try catch to see if it is tripping out at some point.

Hi Ryan

Windows administrator group, the Jiwa user doesn't matter.

Thanks Scott a screen shot of the error is here

does

Code: Select all

nslookup smtp.sendgrid.net

work for non-admin users?

Also, if you have a telnet client on the PC (Window Feature option), you can try

Code: Select all

telnet smtp.sendgrid.net 25

(or whatever your TLS port is). You can just disconnect straight away, but it might also help diagnose the problem.

Try using a normal email client to test the environment.

pricerc wrote:Also, if you have a telnet client on the PC (Window Feature option), you can try

Code: Select all

telnet smtp.sendgrid.net 25

(or whatever your TLS port is). You can just disconnect straight away, but it might also help diagnose the problem.

+1 to this, and also Scott's suggestion if Telnet yields nothing useful to try an email client.

If the DNS resolves, but the connection cannot be established then either something is blocking the outbound (firewall perhaps) or the inbound at the other end (IP blacklisted by the sendgrid network for instance).

SPF, DNSSec and friends probably aren't your issue (would have thought if SPF or DNSSec was a factor you'd get a different sort of error - we just report what the .NET SMTP client throws) - but those might also be a factor - with services like Sendgrid they might be doing something funky outside the RFC standards for SMTP which occurs at the connection level and may explain connection issues also.

EDIT: But given members of the Administrators windows group don't have the issue, then it must be a policy or something on the machine sending - firewall rules should be your first line of inquiry.

Hi Guys

Thanks for all the suggestions unfortunately we are now not able to replicate the issue, which leads me to believe it may have been caused by a networking issue.

We are waiting to see if the original user who reported the issue is still getting it.