Continuing the discussion from Replacing Mailing lists: Email-In:
Sorry if this is already discussed. It’s rather hard to search for the 2-character “CC” on Discourse. 
Is there (ever or still) a valid reason to reject emails where the Discourse email address is on the CC or BCC line? If so, what’s the rationale? We have had this happen a few times recently with confused users.
I was asked about this on Monday. A user wanted to send an email to a consultant with a cc to our staff mailing list on discourse. The idea she had (I think) was to enable staff to reply to both consultant and staff for follow up.
This doesn’t have predictable results and so I encouraged her to write two separate emails. One to staff and another to the consultant. Otherwise if the consultant replies all it will generate an error from discourse, and the replies from the staff won’t get to the consultant.
Discourse and email are like oil and water, sadly. But folks are getting used to it and we’re getting good results.
Our scenario is quite similar. The questions come from addresses (aliases) associated with specific categories that are handled like team distribution lists, like yours.
Seems to really confuse users. How best to improve the experience? At a minimum, I think the error message here could be improved.
OK, what does it currently say and what do you think it should say?
Discourse fires off the “I didn’t recognize that To: address” error reply if it’s in the CC:.
Here’s an important question: What part of the email should be posted?
It will be difficult to strip out the email addresses from the “Forwarded Message” block, as (of course!) every email client will do it differently.
If it is not wanted to let in emails send to a category through Cc: or Bcc: I at least want to suppress the reject email. What do you think?
Reason is I currently try to move people away from using email and get them used to Discourse. So I let Discourse harvest emails send to some mailinglists. As soon as there is such an mailinglist address added to the Cc: field instead of To: the sender gets confronted with the reject email send by Discourse. This is confusing people.
Has there been any change in this behavior with 1.5, @zogstrip?
When an email is received, we look for email addresses in all the destinations fields (To, Cc and Bcc). If at least one matches a reply address, a group or a category incoming email address, then the mail will be processed.
Forse mi sfugge qualcosa, ma l’intestazione Bcc non esiste?
Vedo che il codice sorgente di Discourse la controlla, ma l’idea alla base del Bcc non è proprio quella che gli indirizzi email non debbano mai comparire in un’intestazione?
BCC è un’opzione di intestazione valida: se l’indirizzo del destinatario non fosse presente nell’intestazione, il messaggio non potrebbe raggiungerlo.
Una volta che un’email con più destinatari arriva all’MTA, viene inviata per ciascun destinatario; gli utenti in a/cc vedranno un’intestazione senza BCC, mentre qualsiasi utente in BCC vedrà il proprio indirizzo specificato come BCC:
L’instradamento viene effettuato in base alla busta RFC821; le intestazioni del messaggio non vengono utilizzate a tale scopo.
Ho effettuato ulteriori ricerche e nella specifica è effettivamente presente un’intestazione Bcc, ma non l’ho mai vista utilizzata.
In pratica, gli MTA e/o i client di posta sembrano omettere l’intestazione Bcc nei messaggi, anche quando vengono consegnati a uno dei destinatari in Bcc.
Anche questa è la mia esperienza. Non ricordo di aver mai visto il mio indirizzo email in un messaggio che mi è stato inviato in Bcc.
@zogstrip sapresti cosa potrebbe essere successo?
Sembra che in questo commit ci fosse un controllo nel “foglio”: add support for incoming emails in CC/BCC fields · discourse/discourse@93d1cc6 · GitHub (nello specifico discourse/lib/email/receiver.rb at 93d1cc6294085008e025bb3032b231a6a81c6480 · discourse/discourse · GitHub), ma poi sembra sia stato rifattorizzato nelle versioni più recenti di receiver.rb.
C’è la possibilità che le modifiche evidenziate da @k4rtik vengano reintrodotte? Ho riscontrato recentemente questo problema. I nostri utenti vorrebbero inviare aggiornamenti tramite BCC.