Dear all,
today I recived a user complain that his messages were rejected with error "The message's content type was not explicitly allowed"
I checked the list and indeed, it was configured to filter content and to allow only a very limited number of content types, namely application/pdf and image/jpeg.
After some experiments, the problems seems to be the s/mime signature. The messages contain a signature: <snip> Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s"
<snap>
I added this type to the allowed MIME content type, but signed messages are still rejected.
What do I miss?
Viele Grüße,
Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst@aip.de https://www.aip.de
Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam
Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026
Mailman's content filtering has removed the following MIME parts from this message.
Content-Type: application/x-pkcs7-signature Name: smime.p7s
On 11/12/21 5:38 AM, Rainer Herbst wrote:
today I recived a user complain that his messages were rejected with error "The message's content type was not explicitly allowed"
For a message to be rejected with that reason, the messages top level content type must not be allowed. I.e. the list's Pass types is not empty and doesn't pass this message's content type. I'm guessing the message is multipart/signed and that's not allowed. Generally, you want to include 'multipart' in pass types to accept all multipart/* types and filter the sub-parts.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Rainer Herbst