DIYMacServer » Tag: filter

DIYMacServer » Tag: filter - Recent Posts http://diymacserver.com/forum/ DIYMacServer » Tag: filter - Recent Posts en Wed, 08 Feb 2012 06:01:34 +0000 Priz on "/usr/local/bin/maildrop: Cannot have world/group permissions" http://diymacserver.com/forum/topic/usrlocalbinmaildrop-cannot-have-worldgroup-permissions#post-326 Mon, 26 Feb 2007 00:04:10 +0000 Priz 326@http://diymacserver.com/forum/ Hello, I had an error when the postfix server received an email : <blockquote><code>postfix/pipe[1692]: 8699098029C:to=<xxxxxxx@xxxxxxxx.net>,relay=maildrop, delay=3100, delays=3100/0.02/0/0.04, dsn=4.3.0, status=deferred (temporary failure. Command output: /usr/local/bin/maildrop: Cannot have world/group permissions on the filter file - for your own good. )</code> Answer from Richard : <pre><code>The rights should be: -rw------- vmail wheel /etc/maildroprc</code></pre> and I complete : <code>Don't forget to restart services authdaemond, maildrop and postfix</code> Thank's Richard</blockquote> Richard on "Regexp instead of PCRE in postfix access?" http://diymacserver.com/forum/topic/regexp-instead-of-pcre-in-postfix-access#post-281 Sat, 27 Jan 2007 09:05:20 +0000 Richard 281@http://diymacserver.com/forum/ The thing is that you are mixing up two seperate functions into one. The listing of the PCRE filter <code>/./     FILTER dspam:dspam</code> in the option "smtpd_recipient_restrictions". Is only there to filter incoming mail only. If you leave out this option all outgoing mail will be filtered as well which is not something you would want. The retraining transports are there for another reason, you want to feed dspam with incorrect identified emails and you don't want it delivered to a users mailbox. Therefore you define a separate transport. In main.cf you add the following lines to do that <code>recipient_delimiter = - </code> (to separate the username from the -spam in the mail address) and <code>transport_maps = hash:/etc/postfix/transport local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps </code> to define the transports: and then you ceate a file called transport and add: <code><a href="mailto:spam@mydomain.tld">spam@mydomain.tld</a>    dspam-retrain:spam <a href="mailto:ham@mydomain.tld">ham@mydomain.tld</a>     dspam-retrain:innocent <a href="mailto:notspam@mydomain.tld">notspam@mydomain.tld</a>     dspam-retrain:innocent </code> do a <code>sudo postmap transport</code> to convert it. and add <code>dspam-retrain   unix    -       n       n       -       10      pipe   flags=Ru user=dspam argv=/usr/local/bin/dspam-retrain $nexthop $sender $recipient </code> as a transport in our master.cf for retraining purposes ! The retraining shell script you can download from <a href="http://switch.richard5.net/serverinstall/dspam-retrain">here.</a> Hope this helps ! grgcombs on "Regexp instead of PCRE in postfix access?" http://diymacserver.com/forum/topic/regexp-instead-of-pcre-in-postfix-access#post-279 Fri, 26 Jan 2007 23:53:09 +0000 grgcombs 279@http://diymacserver.com/forum/ Oh ... I think I see what you're saying. my users won't be able to use those transports at all will they ..... can you show me how to setup the retraining as tranport maps instead? g grgcombs on "Regexp instead of PCRE in postfix access?" http://diymacserver.com/forum/topic/regexp-instead-of-pcre-in-postfix-access#post-278 Fri, 26 Jan 2007 23:50:40 +0000 grgcombs 278@http://diymacserver.com/forum/ I figured it out ... I went back and redid things since I last posted to be more like yours in main.cf I added: check_client_access regexp:/etc/postfix/dspam_regexp instead of the "pcre:" business... at the bottom I put: dspam_destination_recipient_limit =1 dspam-add_destination_recipient_limit = 1 dspam-del_destination_recipient_limit = 1 and then this went in my dspam_regexp file: /^spam-(.*)/ FILTER dspam-add:${1} /^ham-(.*)/ FILTER dspam-del:${1} /^(.*)/ FILTER dspam:${1} This way it's more like yours, but I don't have to worry about a retraining script, since I can just use these other transport methods for training. The other part of my problem is that since I'm doing my own parsing of the user names, I had to turn off the parsing in the dspam.conf file. g Richard on "Regexp instead of PCRE in postfix access?" http://diymacserver.com/forum/topic/regexp-instead-of-pcre-in-postfix-access#post-276 Fri, 26 Jan 2007 23:31:01 +0000 Richard 276@http://diymacserver.com/forum/ where did you put the FILTER stuff in in main.cf. If you put it in the same section as the documented filter stuff than it won't work as that filter is only hit by mail coming from the outside world and not for authenticated users ! You should put the retrain stuff in transport maps ! grgcombs on "Regexp instead of PCRE in postfix access?" http://diymacserver.com/forum/topic/regexp-instead-of-pcre-in-postfix-access#post-273 Fri, 26 Jan 2007 17:49:12 +0000 grgcombs 273@http://diymacserver.com/forum/ So I think I've found some sample regular expression code that *might* work in getting dspam running with postfix without PCRE... Granted I'm not sure what's happening, but I think this will break out <a href="mailto:spam-person@whoever.com">spam-person@whoever.com</a>, <a href="mailto:ham-person@whoever.com">ham-person@whoever.com</a>, and <a href="mailto:person@whoever.com">person@whoever.com</a> ... and send them off to different parts of postfix to do handle training for dspam.... /^spam-(.*)/ FILTER dspam-add:${1} /^ham-(.*)/ FILTER dspam-del:${1} /(.*)/ FILTER dspam:${1} I'm not sure if the last one is necessary... And then here's what goes in master.cf: dspam-add unix - n n - - pipe flags=Rhq user=dspam argv=/usr/bin/dspam --user ${user}@${nexthop} --class=spam --source=error dspam-del unix - n n - - pipe flags=Rhq user=dspam argv=/usr/bin/dspam --user ${user}@${nexthop} --class=innocent --source=error Now I'm not sure if this regexp needs to go in transport_maps, or access, or what... Anyone do anything like this yet?