heya people :)

I just set up a osTicket v1.9.12 + Apache, on a W2k8 R2 VM, the rest as followed:

mail-sending: via SMTP, w/o authmail-fetching: via imap, port 143MySQL 5.6.26PHP 5.5.28

All went good for now, i'm receiving mails @ the osTicket webinterface, sent to the support-mail address and can see and read them w/o any problems. But when I answer/reply to an open ticket via osTicket, I'll get an "Mailer-Error" @ osTicket-Syslogs, saying:

"E-Mail-Versand über SMTP nicht möglich-exch01.auer-guss.net Failed to send data amb-exch01.auer-guss.net"

(I'm sorry for the german part; it just says something like --> "email dispatching via smtp is not working")

When I check the outgoing mails in my exchange-server, they appear as "permanentlyBlocked" and never reach their recipient.

The only, maybe useful thing, I noticed: the mail's subjects are always empty (no subject)...

Thanks in advance & best regards

"This email was rejected because it violates our security policy"I'd recommend that you speak with your email host.  I'd also recommend that you check your email templates to ensure that there is something in the subject.

Hi ntozier, thanks for your reply.Well, none of the templates has an empty subject.The thing with my mail host is: It's our own exchange, standing like 10 meters away.The mail, osTicket tries to send, wouldn't even leave the company :(

Well your mail server appears to be rejecting the email.

yes, but why?When I take the ownership of the whole mailbox, and send some mails with it - regardless of subject, content or recipient - it get's through without any problems.

The email server is reporting that it violates your security policy.

.. but only, when osTicket sends mails.

So you have other pieces of software on your webserver sending email through your mail server?Anyway... you would want to investigate on your mail server why that error is being thrown.  Which ought to tell us why its failing.

Sorry for my late reply.Thank you very much, you were absolutely right.My NoSpamProxy had a blocking rule for all inbound, internal mails, which had a specific header.Now it's working perfect =)

:)Glad to be able to point you in the right direction.

Write a Reply...