What are the symptoms of a RNDR attack?
|
 |
Your corporate mail server is repeatedly
blacklisted |
 |
Sluggish email delivery |
 |
Outbound queues full of non-delivery notices |
 |
Excessive admin time to clear outbound queues |
|
How does a "Reverse NDR" attack work?
|
Phase 1 |
Spam email is created with the intended spam victim's address in the sender
field and a random, fictitious recipient, at your domain, in the To: field.
|
Phase 2 |
Your mail server cannot deliver the message and sends an NDR email back to
what appears to be the sender of the original message, the spam victim.
|
Phase 3 |
The return email carries the non-delivery report and possibly the original
spam message. Thinking it is email they sent, the spam victim reads
the NDR and the included spam.
|
|
Is RNDR all hype? These people disagree |
"This [NDR Attack] has been a big problem for us, particularly over night, when
our exchange server was sending our great batches of NDRs in response to randomly
chosen email addresses at our domain."
Stephen H. IT Mgr - KCE Europe
|
|
"The product [Praetor] was suggested by Microsoft Tech Support to address an NDR
SPAM attack on our server..."
Private School Principal New Jersey
|
|
"We called Microsoft Support about the reverse NDR problem only to
find out that Microsoft doesn't have a solution for it."
Stephan van Heerden IT Administrator Media Profile
Referred to CMS, Praetor was the solution to halt RNDR attacks
|
|