We do not want to expose this subdomain to our users. Mailgun recommends the usage of subdomains when sending mails. The idea would be to force the sender headers in discourse. According to our test, it seems to work well.
I’ve been working with all our email systems, both internal and external, and also SPF, DKIM and DMARC setups -
For many of our providers, we are allowed to send through mailgun, as mg.example.com subdomain, but the sender and from fields are set to match @example.com - so there is no “on behalf of” issue.
For dmarc alignment, the really important parameter is the “d=” field when signing the email with dkim. If this is d=example.com, then everything is aligned because the @example.com is matching the top level sender domain (ie, outdomain.com) - so the mechanisms “SPF dmarc alignment” and “DKIM dmarc alignment” both show as “pass”. When eveything shows as pass, the email is accepted as valid.
So, we have a couple issues here. Can we set the “sender” and “from” fields?
Do you properly assign the domain in the “d=” when dkim signing the email?
In your settings, you can setup the domain to point to whatever domain you want.
My site is hosted on board.example.com and the emails come from example.com
here it’s not related to the website url but to the SMTP Domain vs Sender domain.
Our smtp is mg.something.com whereas our sender domain is something.com.
My mailgun is setup as mg.example as well. Still uses example.com as the protocol. edit maybe I’m just not understanding what you’re trying to imply.
Apologies.
c0ry, it seems we are not able to set the “sender” and “from” (and the “return path”) fields to be the same. If they are not the same, you can get emails that say “sent on behalf of”. Then risk of spam classification is higher.
Sto lottando con l’integrazione delle email in uscita con Office365.
Ci sono diversi thread che discutono di problemi relativi alle email.
Per informazione:
Di default, Office365 restituisce un errore 554 se il mittente non corrisponde all’account di accesso (e i log di Discourse non sono molto dettagliati).
L’indirizzo del mittente può essere impostato, come discusso altrove, utilizzando:
rails r “SiteSetting.notification_email = ‘discourse@yoursite.com’”
Ma credo che questo imposti solo la prima email inviata.
Nota: l’URL del mio forum NON è correlato al dominio della mia email…
Nel mio caso, ho dovuto impostare quanto segue nelle impostazioni (GUI):
1/ email di notifica
2/ nome utente del contatto del sito: questo significa che DEVI avere un utente con l’email da cui desideri inviare (cioè l’email con cui accedi a SMTP).
In pratica, TUTTE le email inviate da Discourse devono avere il campo ‘from’ impostato sulla stessa email utilizzata per l’accesso SMTP, per utilizzare una connessione SMTP ‘normale’ di Office365. Spero che quanto sopra riesca a ottenere questo risultato, ma sarebbe un’ottima funzionalità poter impostare in modo definitivo il campo ‘from’ per ogni email, con garanzia.