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.
J’utilise Mailgun et j’ai configuré un groupe Discourse pour recevoir des messages via une adresse e-mail. Mailgun effectue un appel HTTP à mon installation Discourse pour livrer ces e-mails en tant que messages, mais ces appels HTTP échouent avec un 406 Not acceptable, qui est officiellement décrit comme :
La ressource est valide, mais ne peut pas être fournie dans un format spécifié dans les en-têtes Accept de la requête.
Les journaux Discourse ne révèlent rien sur ces erreurs HTTP 406
Une erreur moins courante est signalée par Mailgun : 413 Request Entity Too Large, que je comprends, mais je ne suis pas sûr de la manière de résoudre ce problème du côté de Discourse. Comment configurer Discourse pour les accepter ?
