Cris70
I don’t think this is a bug but a setup issue. I’d need to review your whole setup to confirm though.
Cheers.
Thank you. Do you want me to send something to you? Screenshots or anything?
You can start with screenshots of the emails you have configured and screenshots of the filter. Then show the full raw email headers of an email that’s triggering the filter/errors.
I just noticed you said you are using v1.18. Try upgrading to v1.18.1 and retest to make sure it's not actually a bug like you said. With the latest this should not occur. If it does still occur then it does really seem like a setup issue.
Hi KevinTheJedi I upgraded my osTicket installation to v1.18.1 and tested the filter again. I still do not get the email when a new ticket is created (but only if the filter is triggered). Looking at the log, I see that now the first error ("Mail Fetcher - Excessive errors...") is gone. The second error however is still there: Unable to email via SMTP: tickets@domain_amended (ssl://smtps.aruba.it:465/SMTP) 5.2.0 fGjMr5mnNoGOvfGjMrRT2o - Mittente non consentito / Sender not allowed ( header-from ) . As I told you before, the sender is the same wether or not the filter is triggered, so I find it very strange. Another strange thing: now I get 4 "Mailer error" log messages for every time the filter is triggered:
Very weird.
Thanks. I'm going to upgrade and then I'll get back to you.
Cris
What do your system email names look like? Any with special characters?
Nope:
What's you System Default Email, Default Alert Email, and Default MTA (all under Admin Panel > Emails > Settings)?
Also, what are the Outgoing Email and Autoresponse Email settings for the Department that's throwing the errors?
KevinTheJedi What's you System Default Email, Default Alert Email, and Default MTA (all under Admin Panel > Emails > Settings)?
Thank you, this question helped me finally solve the problem! I was using noreply@amended_domain for both outgoing and autoresponse email, but that address is not correctly configured for sending. After changing those addresses to the correct one (tickets@amended_domain) everything is working correctly. However, why was the error message indicating tickets@amended_domain?
I’m not certain at this stage. Maybe it was trying to use the tickets email as a backup and that failed for some reason?
