Kevin Colagio wrote: > It's a valid address otherwise, it's just the one old domain that he > gets SPAM through. As much as I'd love to drop support for the domain, > it's used by others yet... > > Good thought though. I just wish it were that easy.
Oh, it's easy enuf - just not *as* easy... In our case, set the 'active' flag to 'f' for the account... ;-) Now - *your* case... How is it that whatever you are using for validating recipients is NOT ALREADY specific as to both $local_part AND $domain? i.e. - fix the 'general case', and this problem is gone. Ex: He can have '[EMAIL PROTECTED], [EMAIL PROTECTED], etc. But so long as your list, table, or DB does NOT have: '[EMAIL PROTECTED]' - a require verify = recipient will reject traffic at rcpt time. A bit more work will be needed if you are permitting on-box 'shell' accounts, but not much more. Bill > > W B Hacker wrote: > >>Kevin Colagio wrote: >> >> >>>We are accepting mail for an old domain space "x.y.geneseo.edu". This >>>domain is defined as part of our local_domain definition. >>> >>>One of the recipients doesn't want the mail that is addressed to him at >>>that address ([EMAIL PROTECTED]) because it's all SPAM. However, we >>>need to accept the other mail on that domain space for the other people. >>> >>>I tried adding a system filter to delete mail to his address, and that >>>didn't work. >>> >>>Is there a way to block a single person's e-mail within a domain that is >>>otherwise accepted for delivery? >>> >>>Thanks in advance. >>> >> >>IF the $local_part is not used in any of your other domains, how about adding >>it >>to the system aliases file and pointing it to bit-bucket (/dev/null)? >> >>Cheap and cheerful, though it leaves senders in the dark. >> >>Bill >> >> > > -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
