-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17 Dec 99, at 17:13, Gil Prudente wrote:
> Someone used a non-existent address in our domain
> ( [EMAIL PROTECTED] ) to send spam and we're getting
> hundreds of bounced messages, which in turn are
> double-bounced because the mailbox does not exist.
Pity you.
> I have temporarily redirected these bounced messages
> to a file by creating an alias, to get rid of the
> double-bounces.
That looks like a reasonable way to do. The even more reasonable
way would be to find out the recipient of the bounce, and point
_that_ account to bit hell (/dev/null). You don't have to generate the
second bounce, and you're not missing some (more important)
double bounces.
> What's the best way to deal with this? The spammer
> even used msc.net.ph in the greeting, but the receiving
> server was able to record the IP as 152.200.184.186.
Not much to do. It's a feature (agruably weakness) of SMTP
protocol. You can only trace further 152.200.184.186, and
undertake legal action or something, but you need to live
with the bounces.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOFoSuFMwP8g7qbw/EQJU7QCeL1XVNFxF5mYseS8TgrO8IPF7hhsAoMK8
oeY4nPoc/urnWr+pm3xiJdDQ
=VVsq
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
