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.
Estou usando o Mailgun e tenho um Grupo do Discourse configurado para receber Mensagens por meio de um endereço de e-mail. O Mailgun faz uma chamada HTTP para minha instalação do Discourse para entregar esses e-mails como Mensagens, mas essas chamadas HTTP falham com um 406 Not acceptable, que é descrito oficialmente como:
O recurso é válido, mas não pode ser fornecido no formato especificado nos cabeçalhos Accept da solicitação.
Os logs do Discourse não revelam nada sobre esses erros HTTP 406
Um erro menos comum é o Mailgun relatando um 413 Request Entity Too Large, o que eu entendo, mas não tenho certeza de como resolver no lado do Discourse. Como configuro o Discourse para aceitar isso?
