Page 1 of 1

Quarantained SPAM messages are kept as application/octet-stream; charset=binary 3.0.1.8

Posted: 28 Mar 2017 16:32
by ajmind
Sorry, if I am wrong as I am not an expert. (Not yet :) )

After various customsation of my current test install, at some point I have found some messages in the daily spam folder which are looking odd, with no usual file header. You could not see the content in MailWatch, the window stays empty.

Code: Select all

[root@it1mailgw2 spam]# file -i E6FD1C014F.AC235
E6FD1C014F.AC235: application/octet-stream; charset=binary
Just an example of the begin of such a file:

Code: Select all

 C_          11763             743               1               0           11763               0T^0T^Q1490634516 411609A^Vcreate_time=1490634517A^Tlog_ident=025B2C014FA^Vrewrite_context=remoteS
I know it should be

Code: Select all

 text/x-mail; charset=utf-8
Now I am lost. Any hint on how to find a possible error or way to correct this problem would be great.

I am now back on a fresh OVF packagage, already version 3.0.1.9. I will document properly all configuratrion steps.
Hopefully, I will find the root cause... :think:

Re: Quarantained SPAM messages are kept as application/octet-stream; charset=binary since upgrade to 3.0.1.9

Posted: 28 Mar 2017 16:37
by shawniverson
That is odd. 3.0.1.9 does not update postfix or MailScanner, which is responsible for saving these files to disk.

Are you seeing any error messages in /var/log/maillog or if you restart MailScanner?

Re: Quarantained SPAM messages are kept as application/octet-stream; charset=binary since upgrade to 3.0.1.9

Posted: 28 Mar 2017 16:44
by ajmind
Mailscanner restarts without a problem.

I will fire up later this evening the previous version of EFA and will let pass some messages. Maybe I have messed something with my testing of signatures in the rules directory?

I will revert with the result tomorrow as I have to leave now.

Re: Quarantained SPAM messages are kept as application/octet-stream; charset=binary since upgrade to 3.0.1.9

Posted: 29 Mar 2017 12:38
by ajmind
Please disregard this topic for now. My snapshot before the upgrade shows the same problem. So it is not related to 3.0.1.9.

Sorry for the opened thread. Could I delete it or mark it somehow?