I understand what BackScatter is - a neat way to get your junk message into the targets mailbox attached to an NDR. However, this isn't BackScatter as the non-delivery report was generated by our MDaemon itself. Instead of delivering the spam to the internal target, it bounced the email and tried to send to sender. The sender address however was the same as recipient (attempting to get junk through by using a trust address in sender) so the spam target ended up getting the non-delivery report. Because MDaemon attaches original messages to NDRs, the junk message came in as well.
Can't seem to find an explanation for why MDaemon rejected this message.
Main Topics
Browse All Topics





by: moorhouselondonPosted on 2009-06-23 at 03:41:01ID: 24690555
Setup BackScatter protection in Mdaemon. You will need to ensure that BackScatter protection doesn't reject anything for a few days until you are sure that any non-BackScatter protected messages have gone through the system, otherwise you may not receive an NDR when you should receive one. This topic is explained in the Mdaemon help, so if you find my explanation confusing, have a look at the help. Do remember to enable it after a few days however, as otherwise you will wonder why you're still receiving cr@p lol.