Alastair Campbell wrote:
> Wakko Warner wrote:
> >Why not just block bounces to the catchall?
>
> Err, ok, how?
>
> Jacob's suggestion was for acl_check_rcpt:
>
> deny
> senders = :
> ! local_parts = known@??? : another@???
> message = This address never sends out mail, so it cannot get bounces.
>
> Is there is a way of selecting the catch all, in my case defined at the
> end of: /etc/mail/virtual/domain.com
>
> *: my_username@localhost
>
> If I can say "anything that dropped through to the catch all" instead of
> putting in individual addresses for local_parts, that would be perfect...
At work I have a catchall (yea, I know, can't remove it, they like it. I've
even stated we'd get blacklisted because of it too), but it's not done like
what you're doing. We have more than 1 domain, but all addresses are the
same. Anyway, I have a router at the very end that is the catch all and
redirects to unknown-users which is an alias. On that router I have:
senders = ! :
This way, if the sender is <>, it will be a negative match and not work.
Thus sender callouts to our server also work. I did not do anything with
the ACL section.
P.S. I did have a router after that that simply gives a non-existant user
message. Seems verify recipient didn't like not having a router at the very
end that failed or something. It's been a while back and I haven't
re-visited that.
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
