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.
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 (him@???) 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
>
>
--
Kevin Colagio: Systems Analyst, Reef Geek, and Perpetual Student
Computing and Information Technology, SUNY at Geneseo, South 124
colagio@??? (585) 245-5577 http://www.geneseo.edu
Experience is a harsh teacher, the tests are first, the lessons follow.
