Lotus Protector – Notifications (1/6/2010)

Time for a new update.

A) The system is working really well, this is truly a fire-and-forget-missile type device. No blips, no blurps, and no jiggles either.

B) Error reporting is great! I just got a Delivery Status Notification / Failure report on a mail I sent. Normally in Domino these can be rather bland. They will give you an RFC error code, but not much else. I turned on all reporting and set it up to send all reports to an internal account in my mail system. I had ot given it much thought until today when I got my first one:

I just received a failure report from my LP device and it is really good (this is me being geeklily excited) . I have added an edited version further below. Please notice section [<2>] – it gives you the actual output from the rejecting mail server. As I mentioned before, Domino will usually just give you a RFC code and a generic line but this is really helpful. It shows that even thoughs I went by the book, I did not take care of all details – I never updated my external internet DNS with the name for my Lotus Protector device. Somewhat embarrassing, but with the help of clear error messages like this I can actually deal with it right away.

Here is the actual (edited) message:

[<00>] XMail bounce: Rcpt=[john.doe@noplace.com];Error=[550-Inconsistent or no rDNS record for 71.88.57.14 (see RFC1912 2.1)
550-http://www.ietf.org/rfc/rfc1912.txt
550-Reverse DNS record and matching forward entry must exist.
550 => wrong configuration at sending server 71.88.57.14]

[<01>] Error sending message [1262715029329.2561924000.c2d.lprotector] from [lprotector.toalsys.com].

ID:        <10010518-3072-0000-0000-0000000014F3>
Mail From: <victor@toalsys.com>
Rcpt To:   <john.doe@noplace.com>
Server:    <mx.inode.at> [213.229.60.100]

[<02>] The reason of the delivery failure was:

550-Inconsistent or no rDNS record for xxx.xxx.xxx.xxx (see RFC1912 2.1)
550-http://www.ietf.org/rfc/rfc1912.txt
550-Reverse DNS record and matching forward entry must exist.
550 => wrong configuration at sending server xxx.xxx.xxx.xxx

[<05>] Here is listed the initial part of the message:

Received: from /spool/local
by lprotector.toalsys.com with XMail ESMTP
for <john.doe@noplace.com> from <victor@toalsys.com>;
Tue, 5 Jan 2010 13:10:29 -0500
Received: from serveryyyy ([xxx.xxx.xxx.xxx])
by lprotector.toalsys.com ([xxx.xxx.xxx.xxx]) with XMail ESMTP;
Tue, 5 Jan 2010 13:10:26 -0500
Subject: Re: xxxx
From: victor@toalsys.com
Date: Tue, 5 Jan 2010 13:04:47 -0500
To: “John Doe” <john.doe@noplace.com>
Importance: Normal
MIME-Version: 1.0
Message-ID: <OFDB1C99BB.1B47753E-ON852576A2.006350DE@toalsys.com>
X-MIMETrack: Serialize by Router on serveryyyy at 01/05/2010 01:04:49 PM,
Serialize complete at 01/05/2010 01:04:49 PM
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary=”—-_=_NextPart_001_01CA8E30.EAB72282″
x-cbid: 10010518-3072-0000-0000-0000000014F3

This is a multi-part message in MIME format.

——_=_NextPart_001_01CA8E30.EAB72282
xxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxx
xx (text removed) xxxx
xxxxxxxxxxxxxxxxxxxxxx

—– Original Message —–