04-07-2008 01:10 PM
We got hundreds of such messages this weekend:
Ihre Nachricht hat einige oder alle Empfänger nicht erreicht.
Betreff: Новинка на рынке баз данных
Gesendet am: 06.04.2008 18:56
Folgende Empfänger konnten nicht erreicht werden:
pavel@kolomna.ru am 06.04.2008 20:43
Das E-Mail-Konto ist in der Organisation, an die diese Nachricht gesendet wurde, nicht vorhanden. Überprüfen Sie die E-Mail-Adresse, oder setzen Sie sich direkt mit dem Empfänger in Verbindung, um die richtige E-Mail-Adresse herauszufinden.
- mail.test.kolomna.ru #5.1.1 X-Postfix; unknown user: "pavel@kolomna.ru" -
Новинка на рынке баз данных
04-08-2008 01:10 PM
Pat,
you should think about using the bounce verification feature on your gateways. I guess you recieve NDR's for emails sent by a spammer with your users's addresses as senderaddress. Bounce verification can detect these false NDR's and delete them.
Jörg
04-08-2008 01:50 PM
Could you please tell me some practical advantages/disadvantages about "bounce verification"?
04-09-2008 04:38 PM
We have been encountering this issue recently as well. It started about two weeks ago. Even with bounce verification turned on these still get through. I talked with a support representative and because these bounces are not the RFC standard they will make it through. Any suggestions to help stop this would be much appreciated. We also get them from other places than Russia, but they seem to be one of the primary offenders.
04-09-2008 05:40 PM
Could you please tell me some practical advantages/disadvantages about "bounce verification"?
04-09-2008 06:10 PM
All of this presumes that the message is actually a "bounce" (ie, an NDR). If it's just a normal message that is made to look like a bounce then BV doesn't help - but in that case you should be forwarding the message through to spam@access.ironport.com so that we can write a rule and get it pushed out.I already tried to send it to the spam@-address with the help of IronPorts outlook-plugin. :wink: But the plugin couldn't send it, because it was not recognized as a spam-message. I hope this checks are sufficient enough to tell me that such mails are NDR... :oops:
04-10-2008 01:18 AM
[quote="Pat"]
I already tried to send it to the spam@-address with the help of IronPorts outlook-plugin. :wink: But the plugin couldn't send it, because it was not recognized as a spam-message. I hope this checks are sufficient enough to tell me that such mails are NDR... :oops:
04-10-2008 07:02 AM
Thank you for the hint. Other messages works fine and will be sent to you and a copy goes to \Deleted Objects\_IPSpam in my Outlook.
04-14-2008 07:52 AM
We have activated the "Bounce Verification"-Feature.
Now, I have 3 questions:
a) Will the 'Address Tagging Key' be removed from a mail-reply?
(I sent a mail to my private address and wrote a reply. But I can't see the "Address Tagging Key" in the mail-header.
b) Which logfile do I have to check to ensure that this feature is working well?
c) How many times should we change this key? Once a month?
04-14-2008 03:14 PM
a) Will the 'Address Tagging Key' be removed from a mail-reply?
(I sent a mail to my private address and wrote a reply. But I can't see the "Address Tagging Key" in the mail-header.
b) Which logfile do I have to check to ensure that this feature is working well?
04-15-2008 04:47 PM
Thank you Andrea, you are right!
In the meantime I have found the KB answer ID 778 "What logs will show rejected bounces?" which contains:
The IronPort mail logs will show rejected bounces.
The mail log syntax of a rejected bounce will appear as follows:# # invalid bounce, rejected by bounce verification.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide