ConfigServer Community Forum

Hi all!

We're trying to allow .dbf file attachments but we've had no luck so far.

We tried allowing this file extension in:
- archives.filename.rules.conf;
- archives.filetype.rules.conf;
- filename.rules.conf;
- filetype.rules.conf;
with no success.

When trying to send a .dbf attachement we keep triggering this rule: in file "filetype.rules.conf".

Is there a way to leave this rule active but only allow certain (.dbf) files through?

Unfortunately I am not aware of a way to accomplish this. If you read this knowledgebase article:

https://support.configserver.com/en/kno ... d-to-block

You will note that it is actually the file command and the magic file on your server that is identifying the file as an executable, and not MailScanner itself. You might find a solution by investigating the file command and magic file via the links provided in that article, or searching the MailScanner mailing list database, etc.

Hello, thank you for such quick response.

I've been researching MailScanner v5 Github and found this thread:
- https://github.com/MailScanner/v5/issues/592

Would I be correct in assuming that this feature is in development right now?
Could you please confirm (or deny) this?

If not I probably misunderstood the Github discussion but at the moment this looks like exactly the feature we need.

Many thanks.

We are not the developers of MailScanner itself, so I cannot verify whether it is a feature they are working on. In any case we usually do not integrate new versions of MailScanner into our MailScanner Front-End install right away, because we need to ensure that there are no changes that will cause issues for our implementation.

Thank you for your response.

Since update of MailScanner will probably resolve our issue, can you please provide us with information, when do you plan to update it?

Thank you.

Sorry, I can't provide any timescale for this.