Attachment issue after updating to Mailcow 2025-03a

CK_beats

😂😂😂😂😂 When it comes to circumventing a ban, people are generally very inventive.

From my point of view, there is nothing at all against using it on the intranet and within the network.

But not every file format has to flow into your own system from outside.
You can read about the problems that emails with malicious code lead to every day.

CK_beats

I have another small update:
It seems as if no more attachments are being “lost” at the moment.

However, Mailow appears to partially rename the file attachments.

File name of the original file (mail was held as SPAM and delivered manually): “Unknown attachment 00173.pdf”

File name after internal forwarding to another user:
“Unknown attachment 00082.pdf”.

I am relatively sure that the sender did not label his attachment (training program) as an “unknown attachment”.

Outlook 2016 is generally used as client software.
Access to Mailcow using EAS.

« Previous Page