(idea) drop header filtering functionality

[rimas-kudelis]

Vexim comes with an ability for users to block emails by certain headers (From, To, Subject and X-Mailer).

This functionality means four extra routers (one per each header), but I doubt it's that useful anymore. Perhaps we should remove it in future releases, what do you think?

[kaluang]

A bit off topic but what I miss most in Vexim is the possibility to filter mails into subfolders by sender/subject/content. Does anyone know a good third party software to do that with vexim or is it something we should consider adding?

[rimas-kudelis]

@kaluang, that would probably be Sieve or it's alternatives. Yeah, we probably should consider integrating it somewhere somehow (I have yet no idea where and how Sieve filters are stored, because I never used it).

Alternatively, we could have an interface like shown above, but with added ability to move emails to subfolders instead of rejecting them. Not sure I'd like us implementing that limited filtering though. Perhaps generating/parsing Sieve filters would be a nicer choice.

[runout-at]

I never did use the header filter. And for normal users its too technical.

@kaluang, I use sieve filters a lot. Roundcube has/had a good plugin for configuring sieve filters.

[Udera]

I am using Dovecot (exim pipes the messages to dovecot), there you can easily implement sieve filters that you can configure through Roundcube.

Regarding the header filters, I have used this function once, and it does not even stop the mail at reception, so sieve filters (or others) can do similar filtering. And it is easier for users to have just one place to manage that.

[rimas-kudelis]

Cool, seems we're in agreement that this can be dropped then!

[MrSleeps]

You could also just combine them into 1.

Something along the lines of..

SELECT COUNT(*) FROM blocklists 
JOIN users ON users.user_id = blocklists.user_id 
JOIN domains ON domains.domain_id = blocklists.domain_id 
WHERE users.localpart = 'john' 
AND domains.domain = 'example.com' 
AND ( 
    (blocklists.blockhdr = 'x-mailer' AND blocklists.blockval = 'bad-x-mailer-client') 
    OR (blocklists.blockhdr = 'to' AND blocklists.blockval = 'spam@example.com') 
    OR (blocklists.blockhdr = 'from' AND blocklists.blockval = 'enemy@example.com') 
    OR (blocklists.blockhdr = 'subject' AND blocklists.blockval = 'viagra') 
) 
LIMIT 1;

Which when using string expansions would translate to something like

SELECT COUNT(*) FROM blocklists \
        JOIN users ON users.user_id = blocklists.user_id \
        JOIN domains ON domains.domain_id = blocklists.domain_id \
        WHERE users.localpart = '${quote_mysql:$local_part}' \
        AND domains.domain = '${quote_mysql:$domain}' \
        AND ( \
            (blocklists.blockhdr = 'x-mailer' AND blocklists.blockval = '${quote_mysql:${sg{$h_x-mailer:}{\n}{}}}') \
            OR (blocklists.blockhdr = 'to'       AND blocklists.blockval = '${quote_mysql:${sg{$h_to:}{\n}{}}}') \
            OR (blocklists.blockhdr = 'from'     AND blocklists.blockval = '${quote_mysql:${sg{$h_from:}{\n}{}}}') \
            OR (blocklists.blockhdr = 'subject'  AND blocklists.blockval = '${quote_mysql:${sg{$h_subject:}{\n}{}}}') \
        ) \
        LIMIT 1

Which could also be changed to use like

OR (blocklists.blockhdr = 'subject' AND '${quote_mysql:${sg{$h_subject:}{\n}{}}}' LIKE CONCAT('%', blocklists.blockval, '%'))

But I agree, they are pretty pointless.