Hi Ken,
I know this probably doesn't address the root of your issue, but I have this cron job that runs daily to clean out those bogus rejects:
------------- #!/bin/sh
# This will clean up the mailq every day from trying to tell # the spammers that the person they're trying to spam is not # here...
mailq | grep MAILER-DAEMON | \
awk '{printf $1} {print " deferred"}' | tr -d '*!' | \
xargs -n 2 postsuper -d >/dev/null 2>&1
-------------Cheers,
Jason
Ken Mink wrote:
Hi Folks, I've been trying to figure this out, but I'm stumped. I've got two servers running postfix that handle email for our domain($WORK). One is in the dmz and has relay_domain set for our domainname. In the transport file, I have an entry for our domainname and the internal server to forward it to. This works fine, but I have an issue with it. Due to people who have left the comany, tons of spam comes in for addresses in our domain, but that no longer exist. The server in the dmz accepts the messages and forwards them on like it should. The internal machine then tries to bounce the message since the user is unknown. Since most spam uses a bogus from, the internal machine is getting clogged with messages it can't bounce. There half a dozen employees here, but a postqueue -p lists a couple thousand defferred messages. What I'd like is for the dmz server to immediately reject mail for unknown users. Apart from adding an account for everyone on that machine, I don't klnow how to go about doing that. I've tried explicitly putting each account in the transport file, but that just added the bouncing to the dmz's deferred queue rather than the internal server. Any ideas?
Thanks, Ken
-- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
