Apps cannot send emails anymore since 10.0.3

[james]

Hello @mmolivier
I think this is a duplicate of https://forum.cloudron.io/topic/15886/cannot-send-email-with-alias-anymore
Might be resolved with the 10.0.4 update.

[mmolivier]

Hi @james tried that one already, but it didn't work unfortunately. I don't work with aliases, all email is relayed through external providers.

[mmolivier]

FWIW, the error message. This one sends mails from different sender domains. I need to be able to turn off this validation.

[joseph]

@mmolivier the flag is now at a mailbox level. Go to the mailbox -> edit -> Disable FROM validation .

[mmolivier]

@joseph I don't work with mailboxes, all mail is relayed through external providers (in case of given example SendGrid)

[joseph]

@mmolivier so you have an app that is sending out email with arbitrary ids? can you give more info about the app or plugin ?

Cloudron 10 removed the domain level flag for security reasons. Instead, you have to either use relay tokens (under Email -> domain -> SMTP relay) or via the mailbox.

[mmolivier]

@joseph hi, the apps are based on a fork of the lamp app (I already updated the base image) so that shouldn't be too relevant, if you want I can give you access of course.

Behaviour before the update: App was capable of sending all emails, from different senders of different domains

Behaviour after the update: App runs into the "Connection denied. Authenticated user [mail address configured on the email tab, which i ignore] cannot send mail as [from address specified from within the app]"

The quickest workaround is to align the mail address configured on the app email tab with the from addresses used, but some apps send mails from other addresses (even from other domains in some cases). The domains are all configured within Cloudron. Mails are never sent from an email unknown to Cloudron.

The domains are configured like this

As far as I understand, Cloudron is being too strict here. Mailjet and SendGrid handle everything just fine.

I'd like to be able to turn off this restriction or at least be able to configure accepted mailaddresses somewhere. I can't find neither of those two options.

[joseph]

@mmolivier I think the mail relay token does what you want. All you have to do is create a token and this give you permission to send email as whatever you want for that domain (just like mailjet/sendgrid tokens work). Fix your setup to use relay@yourdomain.com as username and the token as the password. You can then send any email as anyone@yourdomain.com .

[mmolivier]

@joseph said:

@mmolivier I think the mail relay token does what you want. All you have to do is create a token and this give you permission to send email as whatever you want for that domain (just like mailjet/sendgrid tokens work). Fix your setup to use relay@yourdomain.com as username and the token as the password. You can then send any email as anyone@yourdomain.com .

Just to ensure that we're talking about the same problem and same fix.

Old behaviour:

• App sends mail from noreply@domain.com, Email tab of the app is set to noreply@domain.com > Email is accepted and sent based on config of domain.com (which is set to Outbound only, SendGrid)
• App sends mail from noreply2@domain.com, Email tab of the app is set to noreply@domain.com > Email is accepted and sent based on config of domain.com (which is set to Outbound only, SendGrid)
• App sends mail from noreply@otherdomain.com, Email tab of the app is set to noreply@domain.com > Email is accepted and sent based on config of otherdomain.com (which is set to Outbound only, SendGrid)

Behaviour since last night:

• App sends mail from noreply@domain.com, Email tab of the app is set to noreply@domain.com > Email is accepted and sent based on config of domain.com (which is set to Outbound only, SendGrid)
• App sends mail from noreply2@domain.com, Email tab of the app is set to noreply@domain.com > Email is denied because Cloudron allows mails from noreply@domain.com only
• App sends mail from noreply@otherdomain.com, Email tab of the app is set to noreply@domain.com > Email is denied because Cloudron allows mails from noreply@domain.com only

Given this example, your suggested fix is:

• App sends mail from noreply2@domain.com, Email tab of the app is set to noreply@domain.com > Email is denied because Cloudron allows mails from noreply@domain.com only

  To fix this, I should add a "SMTP Relay" token on domain.com, make sure the app authenticates with relay@domain.com and [token of domain.com]

• App sends mail from noreply@otherdomain.com, Email tab of the app is set to noreply@domain.com > Email is denied because Cloudron allows mails from noreply@domain.com only

  To fix this, I should add a "SMTP Relay" token on otherdomain.com, make sure the app authenticates with relay@otherdomain.com and [token of otherdomain.com]

Did I interpret it correctly?

[joseph]

@mmolivier yes, I think your interpretation is correct. One quick question, why not use the sendgrid/mailgun credentials directly in your app? You don't need to go via cloudron mail server in this case, no?

A setting that would help in your specific case is to allow apps to send without MAIL FROM validation . This would avoid the whole dance around creating relay tokens cc @girish

[mmolivier]

@joseph I like the idea of delegating mail to Cloudron entirely and being able to switch mail providers / mail configuration / rotate tokens easily from within the Cloudron UI, so I don't have to edit my own config files / manage SDKs etc.

Keeps my apps simple: Just send mail using the envvars and let Cloudron figure it out. The event log is nice too, for monitoring.

The setting you mentioned would definitely help a lot, but I have a workable solution now, thanks!