This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Verify recipient problem.

Hi,
I have my SMTP proxy set to verify recipient.

Before version 5.100 this worked well and blackholed and that failed.

Now they all end up in the proxy content manager quickly filling it... See here...
2005:02:14-16:50:00 (none) exim[304]: 2005-02-14 16:50:00 1D0bvX-00004R-QM ** nursedlo@micromine.com.au R=static_route T=remote_smtp: SMTP error from remote mailer after RCPT TO:: host 192.168.3.15 [192.168.3.15]: 550 5.1.1 User unknown
2005:02:14-16:50:00 (none) exim[304]: 2005-02-14 16:50:00 1D0bvX-00004R-QM Frozen (delivery error message)

Is there a way to get this to just blackhole or reject with extreme prejudice any mails that get sent to fake recipients on our domain?
Version 5.102

Cheers.

This thread was automatically locked due to age.

0 Simon Shaw over 20 years ago in reply to Gregg_01

Suprised more people aren't commenting on this issue, I have 1000's of emails in the content manager to fake users after just a few days.
Cancel
Vote Up 0 Vote Down

Cancel
0 avdelst over 20 years ago in reply to Simon Shaw

yeah, I have 132 pages in the proxy content manager. (over 3600 entries). This in 1 1/2 days. But for me this only happens with messages that are relayed to the Exchange2003 server, I also have a sendmail system for a couple of domains and this works flawlessly.

Is there a maximum number of messages allowed in the proxy-content manager ? I wouldn't want it to crash.

Andre.
Cancel
Vote Up 0 Vote Down

Cancel
0 DrMabuse over 20 years ago in reply to avdelst

This behaviour is up to a bug that bounce-messages to unknown receipients are not rejected which they should, but end up in the content-manager. This happens when receipient-verification is on. It will be fixed in the next up2date.
Cancel
Vote Up 0 Vote Down

Cancel
0 Xeno over 20 years ago in reply to DrMabuse

BATV would be a workaround.

Xeno
Cancel
Vote Up 0 Vote Down

Cancel
0 Simon Shaw over 20 years ago in reply to Xeno

Fixed in 5.200 Thanks!
Cancel
Vote Up 0 Vote Down

Cancel
0 avdelst over 20 years ago in reply to Simon Shaw

yep, workes fine now in 5.200

Thanks.
Cancel
Vote Up 0 Vote Down

Cancel
0 Biffa over 20 years ago in reply to avdelst

Still not working for me in 5.200, haven't tried 5.201 or 5.202 yet to see if its fixed, but these German spams that flooded out on the weekend didn't trigger it. And if I do a search for "User Unknown" in the SMTP logs I don't see any relating to my domains.
Cancel
Vote Up 0 Vote Down

Cancel
0 Henrik_01 over 20 years ago in reply to Simon Shaw

Hi,

I wonder how you managed to get it work, cause as much as I know, Microsoft Exchange Server doesn't support this.

Thanks for your info,
Henrik
Cancel
Vote Up 0 Vote Down

Cancel