RayBailey
asked on
Block or redirect 'Undisclosed Recipient' Email addresses
We receive spam with the recipient showing as "Undisclosed Recipient' in the address, yet it is being routed to the various individual's mailboxes. Looking at the header info shows it as 'Undisclosed Recipient'.
So...
1) Our Exchange 5.5 sp4 server is processing the email it is getting an address from somewhere.
2) How to block the 'Undisclosed Recipient' address when it doesn't show up in the header as an acceptable mail address?
So...
1) Our Exchange 5.5 sp4 server is processing the email it is getting an address from somewhere.
2) How to block the 'Undisclosed Recipient' address when it doesn't show up in the header as an acceptable mail address?
ASKER
This answer does not give me any info on how to block any incoming SMTP message with an empty 'To:' from Exchange 5.5 If Exchange 5.5 cannot do this without a helper program the answer should state so.
My apologies for not being clear. To my knowledge, you cannot block mail based on the To field without 3rd-party tools.
Check out Mail Essentials (http://www.gfi.com/me/mailessentials.htm) and
MailSweeper (http://www.mailsweeper.com), aka MIMEsweeper.
BZ7
Check out Mail Essentials (http://www.gfi.com/me/mailessentials.htm) and
MailSweeper (http://www.mailsweeper.com), aka MIMEsweeper.
BZ7
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the input. I was afraid that Exchange wouldn't be able to do blocking itself. Seems to be the nature of the beast.
That is the problem with SPAM. You never know what the address is. But I could block a lot of it just on the BCC rule itself.
Thanks bluezoo7
That is the problem with SPAM. You never know what the address is. But I could block a lot of it just on the BCC rule itself.
Thanks bluezoo7
Block these messages as you would any other message. If you have a way to block messages with no one in the To field, this would be your best bet.
Check out this article from MS on the issue:
http://support.microsoft.com/support/kb/articles/Q250/6/92.ASP?LN=EN-US&SD=gn&FR=0&qry=undisclosed%20recipient&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=MSALL
BZ7