I have setup the RBL's in Exchange 2007 and things are working great, even created custom RBL messages for each provider so that our testing included more detail when rejecting messages. I'm at the point where I want to continue using the RBL's, but I don't want it to send a reject/deny message to the sender - I can't seem to find where to disable the reject message for RBL's. TIA You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free@rrohio.com (remove 999 for proper email address)

Why don't you want to send back NDRs? If you are going to allow someone else to control what email you can and cannot receive, you should at least provide enough information so that the sender can deal with the issue if they have got blacklisted in error. It does happen, and email being dropped in to a black hole is a frustration for many people. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

In article <4e098eab-7635-4fdb-a17f-5af9f4325951 @communitybridge.codeplex.com>, Sembee [MVP] says... Why don't you want to send back NDRs? If you are going to allow someone else to control what email you can and cannot receive, you should at least provide enough information so that the sender can deal with the issue if they have got blacklisted in error. It does happen, and email being dropped in to a black hole is a frustration for many people. Simon. Why would I want to send 40,000 NDR's a day? You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free@rrohio.com (remove 999 for proper email address)

On Mon, 11 Apr 2011 18:42:55 +0000, Leythos wrote: > > >I have setup the RBL's in Exchange 2007 and things are working great, even created custom RBL messages for each provider so that our testing included more detail when rejecting messages. > >I'm at the point where I want to continue using the RBL's, but I don't want it to send a reject/deny message to the sender - I can't seem to find where to disable the reject message for RBL's. If you're using a DNSBL to refuse mail then you're not sending anything to the sender -- that what their MTA is doing. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Tue, 12 Apr 2011 01:15:30 +0000, Leythos wrote: >Why would I want to send 40,000 NDR's a day? You don't. That's why you refuse to accept the e-mail in the 1st place. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

In article <8e81c280-8bc3-4664-8451-26a3bba71d63 @communitybridge.codeplex.com>, Rich Matheisen [MVP] says... On Mon, 11 Apr 2011 18:42:55 +0000, Leythos wrote:   I have setup the RBL's in Exchange 2007 and things are working great, ev en created custom RBL messages for each provider so that our testing includ ed more detail when rejecting messages. I'm at the point where I want to continue using the RBL's, but I don't w ant it to send a reject/deny message to the sender - I can't seem to find w here to disable the reject message for RBL's.   If you're using a DNSBL to refuse mail then you're not sending anything to the sender -- that what their MTA is doing. Under Exchange 2007, if you look at Black List Providers, there is a CUSTOM message option for each - any email rejected by the RBL match gets that message. You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free@rrohio.com (remove 999 for proper email address)

I don't think you quite understand how RBLs work. When the connection is made to your server, the server will do the lookup of that connecting IP address to see if it is on the blacklist. If it is not, then the SMTP communication continues. If it is, then the connection is rejected, with that custom text that you can create. The connection is then dropped. The email is bounced back to the sender, by the remote email server, not yours. If it is a spamming system, then no one will see the message. This actually uses LESS resources than what you are proposing because the bulk of the work is done by the email server that is trying to deliver the message, not the server receiving it. If you want to silently drop the message, then you have to accept the entire message, then drop it. That is a waste of bandwidth. So if you are expecting to drop 40,000 messages a day, then it is a difference of 40,000 x a few bytes, compared to 40,000 of three or four kb. That quickly adds up, to a lot of traffic that you are accepting, just to drop. I have a client who drops over 1 million messages a day. Their bandwidth use dropped by 90% when we changed to a host based blocking system (not quite RBLs, but very similar). http://blog.sembee.co.uk/post/Truly-Spectacular-Results-from-Vamsoft-ORF.aspx It is that dropping of traffic at the point of connection which is why RBLs and other host/IP address based blocking techniques are so popular. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

In article <6745936e-d1a1-4813-9651- c1e7462fb12f@communitybridge.codeplex.com>, Sembee [MVP] says... When the connection is made to your server, the server will do the lookup of that connecting IP address to see if it is on the blacklist. If it is not, then the SMTP communication continues. If it is, then the connection is rejected, with that custom text that you can create. The connection is then dropped. The email is bounced back to the sender, by the remote email server, not yours. If it is a spamming sys tem, then no one will see the message.   This actually uses LESS resources than what you are proposing because the bulk of the work is done by the email server that is trying to deliver the message, not the server receiving it. Is this true when the connection is using a forget sending name? You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free@rrohio.com (remove 999 for proper email address)

The name that is being used as the sender doesn't matter. The communication hasn't got that far. The connection is rejected at the point of delivery. It is then down to the sending server to deal with the message. If it is spam (which is why the sender information is spoofed), who cares what it does with it. The message has been blocked from sending. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

In article <788973da-3f41-44ca-8acc- 382e6c52bcba@communitybridge.codeplex.com>, Sembee [MVP] says... The name that is being used as the sender doesn't matter. The communication hasn't got that far. The connection is rejected at the point of delivery. It is then down to the sending server to deal with the message. If it is spam (which is why the sender information is spoofed), who cares what it does with it. The message has been blocked from sending. Simon. Thanks for explaining this to me - I was completely off-track on this one. You can't trust your best friends, your five senses, only the little voice inside you that most civilians don't even hear -- Listen to that. Trust yourself. spam999free@rrohio.com (remove 999 for proper email address)

Hi TIA, Simon is right. Realtime Block Lists (RBLs) are anti-spam services that offer another layer of protection against spam. These services block e-mail messages based on the IP address from which they originate. The service uses various methods to detect spamming IP addresses and enters them into a database. E-mail messages entering your organization are compared against the RBL database and are blocked if they match an IP on the block list. Non-delivery reports (NDRs) are a type of delivery status notification. NDRs are generated whenever a message can't be delivered. If a server detects the reason for the delivery failure, it associates the reason to a status code and a corresponding error message is written. Since the NDRs are generated when messages try to deliver, you cannot find where to disable it for RBLs. You can get more information from these documents: Configuring RBL services http://technet.microsoft.com/en-us/library/bb914050.aspx Non-Delivery Report Issues http://technet.microsoft.com/en-us/library/bb397219(EXCHG.80).aspx Thanks, Evan Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.