Re: [Exim] 3.36 -> 4.05 Migration Problem

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Simon Williams
Datum:  
To: exim-users
Betreff: Re: [Exim] 3.36 -> 4.05 Migration Problem
* On Sat, Jul 20, 2002 at 01:50:40PM BST, Odhiambo G. Washington <wash@???> wrote:
> In the old setup I used /home/$local_part/.bouncelist as a way of
> helping the clients specify addresses they wanted blocked. They
> would do this by sending requests to our CS Dept who then can
> modify the file. When this file was absent for any user, e-mails
> will still get delivered. Now with Exim-4, when I run a test, it
> does look for this file and failing to find it, it barfs (fails):
>
> [root@ns2]#./bin/exim -bt sales@???
> LOG: MAIN PANIC DIE
> failed to open /home/sales/.bouncelist when checking
> "/home/$local_part/.bouncelist": No such file or directory
>
>
> I could create this file in all users home but that is not the
> solution I am looking for since this file is _NOT_ mandatory.
>
> My Question:
>
> How do I tell Exim4 that if this file is not found it should just
> deliver the message??


I'm doing a similar thing, but with per-domain IP blacklists. I
added this to the acl_check_rcpt ACL under the example for DNS
blacklists:

  deny    hosts         = ${if exists {/usr/exim/rbl/$domain}\
                            {/usr/exim/rbl/$domain}}
          message       = host $sender_host_address blacklisted by \
                            administrator


Maybe something like this would work (not tested):

  deny    sender        = ${if exists {/home/$local_part/.bouncelist}\
                            {/home/$local_part/.bouncelist}}
          message       = user $local_part doesn't like you; go away



--
 Simon Williams <simon@???> **** PGP: 099977D0
 "We demand rigidly defined areas of doubt and uncertainty."
                       - Douglas Adams