Postings by sebastian

Postfix with sqlite - Database becomes locked

Dear all,

I am running postfix 3.3 and recently migrated all my virtual domains from MySQL to Sqlite for performance reasons. So far, everything works fine however up to 5-8 times a day, I am seeing an error message in my mail.log saying that the Sqlite 3 database may be locked. Here is an example:

PCRE regex in header_checks ignored - why?


I have a problem with a PCRE-based rule in header_checks which seems to be ignored and I can’t understand why this is the case. Hopefully you guys have an idea on how to fix this :-)

So here is my setup: I am using Postfix 2.11.7 on FreeBSD 10 and as I am being bombarded with emails from certain hosts in France (and I have no idea why).

Duplicate entries in

Dear all,

I am on Postfix 2.11.7 and have pcre-based sender_access, body_checks and header_checks files.

body_checks = pcre:/etc/postfix/body_checks,pcre:/etc/postfix/bad_urls
header_checks = pcre:/etc/postfix/header_checks

When using postmap on these files, I am getting a lot of warnings saying there are duplicate entries such as:

# postmap /etc/postfix/body_checks


postmap: warning: /etc/postfix/body_checks.db: duplicate entry: "/you"
postmap: warning: /etc/postfix/body_checks.db: duplicate entry: "/you"
postmap: warning: /etc/postfix/body_checks.db: duplicate entry: "/you"

Blocking base64 encoded spam mails using body_checks


I am fighting with spam mails entirely encoded in base64 (UTF8). What's
the best way of blocking these mails using body_checks?

I understand from
<a href="" title=""></a> that I
need to base64 encode the input but is there a sample available
somewhere? I found some documentation (see
<a href="" title=""></a>) but it did
not really work for me so maybe somebody can explain how he/she dealt
with such a problem before?

Many thanks.

Best regards