It appears that when an attachment is stripped off (e.g., because it’s not on the approved file type list) the user is never notified that the attachment did not go through.
This causes users to think/assume we got their attachment when in fact it never got included in their post.
Stripping attachments should notify the user (similar to a failed post due to address mismatch or other problems) that the attachment was not included because the file type is not allowed. (Or too big, etc.)
Back on topic, cleared out a ton of noise in this topic.
There are a lot of email clients that include little BS “attachments” with every email they send that contain signatures, calendar files, and other meaningless errata.
If we sent a bounce email on every one, for every “unknown” attachment that was emailed in, that’d be extremely noisy.
Any actual numbers here? Calendar files are usually only sent when someone wants to communicate about an event. Email signatures perhaps but those are usually only for HTML formatted emails right?
I have seen these things but not convinced it’s really a problem here.
One could also only notify when removing a “legit” type such as accepted whitelist matches.
Sto usando Mailgun e ho impostato un Gruppo Discourse per ricevere Messaggi tramite un indirizzo email. Mailgun effettua una chiamata HTTP alla mia installazione di Discourse per recapitare queste email come Messaggi, ma queste chiamate HTTP falliscono con un 406 Not acceptable, che è ufficialmente descritto come:
La risorsa è valida, ma non può essere fornita nel formato specificato negli header Accept della richiesta.
I log di Discourse non rivelano nulla riguardo a questi errori HTTP 406
Un errore meno comune è che Mailgun riporta un 413 Request Entity Too Large, che capisco, ma non sono sicuro di come risolvere dal lato Discourse. Come configuro Discourse per accettare questi?
