>: 5.7.1 Unable to relayThis is due to your Exchange server configuration.  My guess is that your Exchange won't allow the email to be sent without authentication--and your osTicket sending email authentication required setting is set to 'No'In my case, I could not get my osTicket to authenticate in a manner that made my Exchange 2013 server happy, regardless of the authentication required setting. Rather than continue to fight with it, I added a transport rule on my Exchange server to permit relaying from my osTicket VM (and only from my osTicket VM's IP number).

Strange because I set up a receive connector in Exchange for the OS ticket ip address of the server. Would you have an article I can go off just to make sure my settings are correct in Exchange 2010? 

@[deleted] > In my case, I could not get my osTicket to authenticate in a manner that

made my Exchange 2013 server happy, regardless of the authentication

required setting. Rather than continue to fight with it, I added a

transport rule on my Exchange server to permit relaying from my osTicket

VM (and only from my osTicket VM's IP number).We actually did the same thing. :)

I have a receive connector setup but autoresponse is still not working. I can even sent an email through telnet from the os ticket linux server. 

>...my settings are correct in Exchange 2010 Sorry, no.  2010 is different enough from 2013 (5 transport roles vs 2) that I don't know what to tell you.However, (code: 550, response: 5.7.1 Unable to relay) is definitely coming from the mail server not osTicket, so it is a matter of convincing the server to accept the email. When you tried your telnet test, did you send the email to  vmnotify@voicemail1.shoretelsky.com, or to something on svcfin.com?  Exchange (at least my 2013 version) treats messages differently based on which transport they are going through.  Before I added the transport rule for osTicket, my server had no problem accepting emails with no authentication that were destined for internal recipients, but anything going outside that role was rejected due to relaying.  

I tried it from my email to test.user@svcfin.com and it worked fine and the email was received on test.user's email account. I created a receive connector with the ip of the os ticket server and allow anonymous users. Still no autoresponse when I send in a test email to support@svcfin.com but I get a new ticket alert sent to my email. 

Does your osTicket log show a mailer error for that most recent attempt?  The one you pasted before had "Failed to add recipient: vmnotify@voicemail1.shoretelsky.com" as part of the error. Since svcfin and shoretelsky are different domains, Exchange could be treating them differently (no idea really, depends on how your Exchange server is configured).  You sent it from your email, but I don't know what your email actually is.  Maybe osTicket is smart enough to not send an autoresponse and new ticket alert to the same recipient?

I'll try and send in an email outside the domain from my gmail account and let you know what happens. 

As of this morning and last night, there are no more mailer errors. I tried from my gmail account, a ticket was created, I received a new ticket alert on my email as an agent but still no autoresponse to the gmail account or the testuser account within the network. I am stumped at this point. 

I've asked the devs to take a look at this thread.

Thanks very much Neil! (hope I spelled your name right!) :) 

Found the issue with support's help, I had autoresponse disabled under the help topic section. Thanks for everyone's help though! I've got the cron job running too! - Richard

LOL thanks for your help Neil and others. :) 

Oooh..... I didn't even know about that setting.  Thanks for posting your solution back here.

Write a Reply...