Cloudron Forum

@girish
So I tested it with Amazon SES relay and then with a different SMTP server (PurelyMail's). It works with PurelyMail's but not with Amazon SES. The error message refers to the '<' character.

So now, looking at emails sent to me using the working SMTP server, I am noticing that Commento's app does something different with the headers:

Here's a typical test email header sent from the Cloudron email settings page:

From: Cloudron <no-reply@mydomain.com>
To: me@mydomain.com

Here's one sent from Commento's app. Note that this is the one that I received via PurelyMail's SMTP server. This would have failed with Amazon SES:

From: Commento <<commento.app@mydomain.com>>
To: Joe Smith <<me@mydomain.com>>

I swapped out the domain to mydomain.com. But notice that Commento has the extra brackets, and whereas PurelyMail's SMTP server handles it fine, Amazon SES chokes on it. Is this something in Cloudron's implementation of Commento that adds this?

Thanks for taking a look!

Ah, I just saw the new commits on the commento++ repository and it looks like they have fixed it. The previous file smtp_send.go seemed to add the brackets and cause issues, but the new formatting is simplified and should work.

I assume there is no easy way to bring in these changes to my Cloudron instance beyond simply waiting for the next update?

Thanks!