> I defined something like this:
>
> !%BLA,!%Null_Sender in Policy Members
>
>
>
> In Policy Groups I defined:
>
> Null_Sender Policy
>
>
>
> In Policy Group Members:
>
> Completely empty Member.
>
>
>
> In order to be able to do this I had to add lines in policies.pm to
> come up:
>
> [POLICIES] WARNING: [YOU GO: 10/Name: External to external] => (group:
> Null_Sender): - Source ' ' is not to valid specification:
>
>
>
> diff policies.pm.bkp policies.pm
>
>
>
> 331a332,337
>
> > # Match email NULL
>
> > } elsif ($item =~ //) {
>
> > $res =
> emailAddressMatches($sessionData->{'Sender'},$item);
>
> > $server->log(LOG_DEBUG,"[POLICIES] $debugTxt: -
> Resolved source '$item' to a email Null address specification, match =
> $res") if ($log);
>
> >
>
> >
>
I think a policy member of just @ may be more inline with the rest.
Its a little more work than the above, but I can hack it together pretty
quick.
There is then also the other issue about invalid/non-rfc senders and
recipients .... should policyd's behavior be to reject, ignore, discard
... probably configurable may be the best idea?
-N
_______________________________________________
Users mailing list
[email protected]
http://lists.policyd.org/mailman/listinfo/users
