Ticket module - Failed to send mail (sender=robot@domain.com)

Using my Dolibarr CRM/SRM Modules
1

Hi to all!

I am new in this community and I’m apricating your help.

I am having problems with tickets module for sending mail.
“Failed to send mail (sender=robot@domain.com, receiver=xxxxxxxxxx@gmail.com)”
Not getting the specified email address info@********.com from “Outgoing emails (for module Ticket)”

This notification is only when I try to send mail form on of the thickets.

Setup/Emails/Outgoing emails (for module Ticket) is configurated correctly. ( used generic mail info@*******.com)
Test server connectivity = OK
Test Sending = OK (I’m receiving mail)

Can’t figure it out this problem. Every other module is working correctly for sending email.

Many thanks if someone can help .

2

Hello, Did you find a solution?

I have the same problem.

When I create an new ticket the customer gets an email notification that there is an ticket created but when I send an email from inside the ticket I get the error that the email was not send.

The logs show the following: Error [120]: Ran into problems sending Mail.
Response: 554 5.6.0 SMTP protocol violation: A header line must be terminated by CRLF

The thing is I cannot change the header and this is the default so I would asume that it would work.

Hope someone can help and that this ticket wil be resolved.

-Danny

3

Change email in module ticket - from robot to your email

4

Doesnt work, changed it under the ticket module and then settings, Notification.
Sender and notify are set to my contact email adress.

And under the setup setting for emails, I filled in the same mail server for outgoing email (for module Ticket)

5

Sorry, so the problem is another one. Have you checked that the outgoing mail is working? SMTP error 554 indicates that the mail server did not accept the email. Several reasons typically cause this error:

  1. Invalid Recipient Address - There are invalid recipient email addresses; in rare cases, the recipient email address may have been suspended or disabled.
  2. Blocklisted IP Address - It indicates that the sender’s IP Address might be within a blocklist; this may be because the sender can get flagged for sending spam or bulk emails.
  3. Bad DNS Records - The recipient’s email server rejects emails due to issues that it may see in the email server’s DMARC, SPF, and DKIM for validating the sender.
  4. SPF Record - The recipient may have configured SPF (Sender Policy Framework) to drop unwanted spam domains. The policy set by the recipient may be blocking the emails from being accepted by the recipient.
  5. DKIM Record - DKIM records help a mail server verify whether a sender is legitimate. Some email servers reject emails if the sender doesn’t have DKIM configured.
  6. DMARC Record - DMARC records also help a recipient verify the authenticity of an email and its source; some email servers may reject emails if they identify invalid DMARC records.
  7. Sender Flagged As Spam - Most email providers configure custom blocklists to drop potential spam users and domains; this can mean that the email address or domain falls into a blocklist, and the recipient drops all emails.
  8. Email Violation Policy - Email service providers specify policies to ensure that emails must follow a particular set of criteria. The recipient can drop emails that are not according to the set policy.
1 Like