Issue with group e-mail and campain and mass emails

[ThomasB]

Now I checked the email with outlook.

[CODE]EspoCrm 8.4.2

I trying to setup an Email/newsletter campaign and ran into a strange issue.

I have system email smtp and two group smtp accounts.

I go to campaign and create my campaign.

I create a mass email with the second group account as sender. The sender address is newsletter@ and the reply adress is person.x@

If I reload the page or to another page and go back the mass email details, the entry for smtp account is empty.

If I send a test email, it seems the correct group account is used.

However my second issue is that I have now two reply addresses in my mail: Person X <newsletter@> and person.x@

I fixed the second issue with two adresse by removing the reply-to adress from the group email account but I see only the email adress and not the name as reply.

Only "person.x@company.com" instead of "Person X <person.x@company.com>"

Email client thunderbird.


Now I checked the email with the outlook client:

The from address reads "=?UTF-8?Q?newsletter@ <company.com?=newsletter@company.com>"

[ThomasB]

If I check the raw code with thunderbird, it see,s the subject of the html email also prints =?UTF-8?Q? at the start of subject and from address.

Precedence: =?UTF-8?Q?bulk?=

Just found out there was an existing issue: https://github.com/espocrm/espocrm/issues/2923

But still happens with the latest version.

Might be related? https://github.com/laminas/laminas-mail/issues/265 and https://github.com/laminas/laminas-mail/pull/235


If the library is to blame not sure if another one could be used like: https://github.com/PHPMailer/PHPMailer

Not sure about licence and other potential drawbacks.

[ThomasB]

Ok, one issue I have identified.

The problem with =?UTF-8?Q?newsletter@ in the from address happens when you enter the email adress as "From Name". The @ letter is causing this.

From Address	From Name	Result
newsletter@company.com	newsletter@company.com	=?UTF-8?Q? issue
newsletter@company.com	newsletter company.com	works fine

[yuri]

Related: https://github.com/espocrm/espocrm/issues/2923

[ThomasB]

Ok, to summarize all issues:

1. Do not use letters like @ in the "From Name" field.

2. In the Mass Emails dialog, where you specify the SMTP Account, the field is no longer visible if you reload or reenter the dialog.

3. If you specify a "Reply-to-Name" in the Mass Emails dialog and use a group account, then the emails do not contain the name but only the Reply-to-Address.

4. If you setup a group account with a "Reply To Address" in the Administration-> Group Email Accounts settings, and use in the Mass Emails dialog also a different Reply-To-Name,
then the emails you send will have two reply address. One with the "replay-to-name" and the email address from the group emails settings and one email with just the email adress from the Mass Emails dialog.
If you remove the reply-to-name from the group email account, you will have only one email address but without name. See issue 3.

[ThomasB]

One last remark.

I'm using a different domain name in the group e-mail account than the system email account. E.g group@company_B.com and system@company_A.com

If I leave the From Address and From Name field empty in the Mass Emails dialog then the emails will look like this:


group@company_B.com <system@company_A.com>

The From Name will be taken then from the SMTP settings of the Group Email account, however the sender is the system account?

[victor]

Thomas, A very similar topic has has already been considered. Please familiarize with it: https://forum.espocrm.com/forum/gene...-header-source.

[lifecrane]

Hello, sorry to intervene, but i dont think i can post , or I cant find a way to post .. and could not find answer for this problem:
I am trying this software, because the project extension looked ok when i get setup , but I can
t make this email deal to work on the email smtp.. in the imap, it works fine..

However, on the smtp , it gives 500 error, and logs are in the picture, and setup is as follows:
I have vps with crm with highvalue.cloud and domain with site harmonicalpha.com .. I decided to use email from harmonicalpha,com, because trying to save money , once i decided to get a vps so that I have future separated website space, from the crm .. maybe this was a bad idea, I don't know enough about this stuff. ..

What i know, is that now the problem is that I am trying to use the free email address i have at harmonicalpha.com , and set it tup on the espocrm installed at the vps in ubuntu at highvalue.com ... and the error is that Email sending error: 5.7.1 <partners@highvalue.cloud>: Sender address rejected: not owned by user at admin@harmonicalpha.com ..

I have no idea for what to do, and any help is greatly appreciated.

[lifecrane]

By the way, I could not edit my message above, there is error, so had to post this one too: I checked the setup with online smtp checker, and it works fine, with tls and ssl, so I know that the settings I am using, are fine.

[ThomasB]

This topic doesn't really shed any new light on the problem.

If you read all my posts, you'll notice that I've already referenced a similar bug report in the Github project.

I also list 4 or even 5 issues that could be considered bugs. At least issue 2 with the disappearing settings I would consider a bug.

I worked around the UTF8 issue by not using the @ character in the name field.

[ThomasB]

Just saw that laminas-mail will not developed any further.

Source: https://github.com/laminas/laminas-mail

This package is abandoned and will receive no further development!

It is suggested to use

• ddeboer/imap for interacting with IMAP
• zbateson/mail-mime-parser for parsing MIME messages
• symfony/mailer for sending mail

[yuri]

It's sad. We might need to fork it or find a fork.

[yuri]

Magento2 uses laminas-mail. Interesting how (if) they dealt with the encoding issue.

We still need laminas-mail for IMAP, SMTP and email composing for sending. It's not an option to switch to ddeboer/imap and symfony/mailer now because of compatibility issues, big required effort and some limitations of the latter.

We've already been using zbateson/mail-mime-parser for long.

[yuri]

Bug with the smtp account field was recently fixed in the master branch.

[lifecrane]

tx for info. Turns out, my problem was solved, and to do that.. I had to buy local email for my domain, without, I could not make it work because of sender problem ,even w smtp from neighbor site under same account on host .

So I apologize to ThomasB et to get on this discusison, I had no idea how to help fix his problems, and tried to initiate a topic, but I didn't see anywhere a button to initiate, but it was late, so sorry about that . There was a notice though, something about being limited.

Latter, when I know more or less what I am doing, I will try to upgrade this , but this install is recent, like 2 days ago. I will look forward to study this some, and latter buy some extensions. The project management seems what I will need once I have work going.

[yuri]

ChatGPT told:

Yes, there are documented MIME header encoding issues in Magento 2, especially with emails. These issues typically involve problems with character encoding in email headers or bodies when non-ASCII characters are used. Here are the key details:

1. Non-ASCII Characters in Sender Name: Emails fail to send if the sender's name contains non-ASCII characters. This issue is tied to improper encoding of headers, resulting in errors during the email-sending process. For example, when special characters like accents are used, Magento may not encode them correctly
   GitHub
   
   GitHub
   .
2. Plain Text Email Encoding: Starting with Magento 2.2.8, plain text emails are no longer sent as MIME types, leading to character encoding issues in certain email clients. This is because such emails default to non-encoded text, which does not support special characters properly
   GitHub
   
   GitHub
   .
3. Missing Content-Disposition: inline Header: This header, which ensures proper rendering of email attachments and inline content, has reportedly been omitted in some versions. This can lead to emails being displayed incorrectly in email clients
   GitHub
   .

Solutions and Workarounds:

• Update Magento: Ensure your Magento version includes fixes for these issues. Check release notes or apply patches for email encoding problems.
• Use Correct Email Libraries: Some issues arise from underlying email libraries (e.g., Zend Mail). Configuring the library to use ENCODING_QUOTEDPRINTABLE or similar settings may resolve encoding problems
  GitHub
  
  GitHub
  .
• Avoid Special Characters: If you encounter persistent issues, removing special characters from email fields may temporarily prevent errors.

For more details, review relevant threads on GitHub such as Magento issue 24902 and 22065, or consult the Magento developer forums.


I'll try look into deeper when get a chance.

[ThomasB]

Magento seems to use laminas-mail as you can see in the meeting minutes: https://github.com/laminas/technical...TSC-Minutes.md

Laminas-devs also said this: Aleksei came back to point out that UTF-8 encoded subjects is one modern MIME capability we do not support, and these are very common today.

So maybe it would be good to look for an alternative in the long run even if this is a lot of work. Find a well-maintained library which licence also fits EspoCRM.

[yuri]

As I mentioned above, switching libs is not easy. It's a lot of re-work and even another lib not necessary better in every aspect. For example, one does not support XOauth that we do support and have code in our extensions which mean that switching libs introduces compatibility challenges.

[yuri]

Mime subjects is not related to our case I think. We do not use Laminas/Mail for mail parsing.