otrs suddenly doesn't want to receive emails
I have an OTRS set up where it’s been working perfectly fine in a production environment for 18 months now, grabbing emails from a pop3 account. All of the sudden today, emails stopped coming in. I checked the pop3 account using a webmail client, and it shows emails in it. When I go to fetchmail in the admin section, it spends a second running, and then my browser pops up a download for a 0 byte index.pl file. It creates a new ticket for the first email in line only; also in this case, the email is an HTML file, and it spits it out as text-only in the ticket (where it used to preserve it as html), and won’t delete that email, or any others. System logs state that it complains “Can't create PID PostMasterMailbox, because it's already running (otrs.office.emediatrade/1396)!”. I’ve found people online with similar problems, and they stated to go into mysql, and run “ select * from process_id where process_name = 'PostMasterMailbox'; delete from process_id where process_name = 'PostMasterMailbox';”, and then run /opt/otrs/bin/otrs.PostMasterMailbox.pl –f 1. When I do this, it clears out the entry in mysql as expected, but when I run the pl script, it says [root@otrs log]# /opt/otrs/bin/otrs.PostMasterMailbox.pl -f 1 POP3: Message 1/13 (emtsupport@emediatrade.com/mail.ex1.secureserver.net) Couldn't send mail: 550 5.7.1 Client does not have permissions to send as this sender at /opt/otrs/Kernel/System/Email/SMTPTLS.pm line 172 An entry is created again in mysql, the logs say that it can’t create a PID, because it’s already running, and ps –ef | grep PostMasterMailbox.pl turns up nothing. If I go into the UI, and create an email ticket to myself, it successfully sends it to my inbox. I’ve tried rebooting the server, but no avail. I’m at a loss, because no email settings changes have occurred for months. Please help?? Thanks, --Mark
Client does not have permissions to send as this sender indeed. It means what it says on the box. How to fix? Well, this happens because the tickets create new ticket notifications and send via the SMTP server or sendmail and the SMTP server refuses to send because the notification sender address is not allowed to send mail, either anonymously, or under the credentials passed to the SMTP server.
"No, really, how do I fix that?"
permissions to send means the SMTP server is declining. If it's a
credential issue, check with the SMTP server authentication/allow the IP
address to send from anything without authentication. OR change your
notification sender address to something that's allowed to send.
This isn't an otrs issue. It's a message that OTRS reports from the SMTP
server.
On Thu, Jun 19, 2014 at 4:18 PM, Mark Campbell
I have an OTRS set up where it’s been working perfectly fine in a production environment for 18 months now, grabbing emails from a pop3 account. All of the sudden today, emails stopped coming in. I checked the pop3 account using a webmail client, and it shows emails in it. When I go to fetchmail in the admin section, it spends a second running, and then my browser pops up a download for a 0 byte index.pl file. It creates a new ticket for the first email in line only; also in this case, the email is an HTML file, and it spits it out as text-only in the ticket (where it used to preserve it as html), and won’t delete that email, or any others. System logs state that it complains “Can't create PID PostMasterMailbox, because it's already running (otrs.office.emediatrade/1396)!”. I’ve found people online with similar problems, and they stated to go into mysql, and run “ select * from process_id where process_name = 'PostMasterMailbox'; delete from process_id where process_name = 'PostMasterMailbox';”, and then run /opt/otrs/bin/otrs.PostMasterMailbox.pl –f 1. When I do this, it clears out the entry in mysql as expected, but when I run the pl script, it says
[root@otrs log]# /opt/otrs/bin/otrs.PostMasterMailbox.pl -f 1
POP3: Message 1/13 (emtsupport@emediatrade.com/mail.ex1.secureserver.net)
Couldn't send mail: 550 5.7.1 Client does not have permissions to send as this sender
at /opt/otrs/Kernel/System/Email/SMTPTLS.pm line 172
An entry is created again in mysql, the logs say that it can’t create a PID, because it’s already running, and ps –ef | grep PostMasterMailbox.pl turns up nothing.
If I go into the UI, and create an email ticket to myself, it successfully sends it to my inbox. I’ve tried rebooting the server, but no avail.
I’m at a loss, because no email settings changes have occurred for months.
Please help??
Thanks,
--Mark
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Yeah, I followed that path, even called my email hosting provider, and we couldn’t find anything wrong. Also, when it can still send a new email when I create a new email ticket, doesn’t that eliminate that as a culprit? Thanks, --Mark From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Gerald Young Sent: Thursday, June 19, 2014 4:29 PM To: User questions and discussions about OTRS. Subject: Re: [otrs] otrs suddenly doesn't want to receive emails
Client does not have permissions to send as this sender indeed. It means what it says on the box. How to fix? Well, this happens because the tickets create new ticket notifications and send via the SMTP server or sendmail and the SMTP server refuses to send because the notification sender address is not allowed to send mail, either anonymously, or under the credentials passed to the SMTP server.
"No, really, how do I fix that?"
permissions to send means the SMTP server is declining. If it's a credential issue, check with the SMTP server authentication/allow the IP address to send from anything without authentication. OR change your notification sender address to something that's allowed to send.
This isn't an otrs issue. It's a message that OTRS reports from the SMTP server.
On Thu, Jun 19, 2014 at 4:18 PM, Mark Campbell
OK, so I just solved the problem, but I’m not sure why it was a problem.
SysConfig Framework->Core-> NotificationSenderEmail was reset to the default otrs@
Client does not have permissions to send as this sender indeed. It means what it says on the box. How to fix? Well, this happens because the tickets create new ticket notifications and send via the SMTP server or sendmail and the SMTP server refuses to send because the notification sender address is not allowed to send mail, either anonymously, or under the credentials passed to the SMTP server.
"No, really, how do I fix that?"
permissions to send means the SMTP server is declining. If it's a credential issue, check with the SMTP server authentication/allow the IP address to send from anything without authentication. OR change your notification sender address to something that's allowed to send.
This isn't an otrs issue. It's a message that OTRS reports from the SMTP server.
On Thu, Jun 19, 2014 at 4:18 PM, Mark Campbell
participants (2)
-
Gerald Young -
Mark Campbell