Wietse Venema wrote:
The following solution solves 99% of the problem:
- IF mail is from a local (or authenticated) client
That's the magic part right there. How do I accomplish this?
- AND the sender has already passed "reject_unlisted_sender"
- THEN store the (sender, recipient) pair in
Daniel L. Miller:
> Wietse Venema wrote:
> > The following solution solves 99% of the problem:
> >
> > - IF mail is from a local (or authenticated) client
> >
> That's the magic part right there. How do I accomplish this?
The client IP address passed along in the policy protocol.
> > - AND th
Wietse Venema wrote:
The client IP address passed along in the policy protocol.
This goes back to my original question. How, using existing Postfix
syntax, can I call the policy daemon - after the IP address and/or
sender authentication has been performed by Postfix? Or would I have to
r
Daniel L. Miller wrote:
Wietse Venema wrote:
The client IP address passed along in the policy protocol.
This goes back to my original question. How, using existing Postfix
syntax, can I call the policy daemon - after the IP address and/or
sender authentication has been performed by Postfi
The following solution solves 99% of the problem:
- IF mail is from a local (or authenticated) client
- AND the sender has already passed "reject_unlisted_sender"
- THEN store the (sender, recipient) pair in a whitelist.
This can be done with trivial modification of an existing greylisting
poli
