Hey folks --
Here's one for the masses. This has been driving nuts, but fortunately
I can redirect the annoying message to another account. The problem is
that Novell Groupwise sends this silly "message opened" response every
time one of my subscribers reads a message. As result, I get hundreds
of these a week.
Anyone know how to nuke them? Is there a header I can put in the
messages to turn off this insanity? I need some EggNog... ;-)
thanks,
bruce
----- begin sample message -----
Received: from licwall1.lic.gov.au by donews.cts.com with smtp
(Smail3.1.29.1 #5) id m0vaTTf-00004HC; Wed, 18 Dec 96 13:24 PST
Received: by licwall1.lic.gov.au; id IAA26696; Thu, 19 Dec 1996 08:37:48 +1100 (EST)
Received: from unknown(190.0.200.81) by licwall1.lic.gov.au via smap (V3.1)
id xma026690; Thu, 19 Dec 96 08:37:21 +1100
Received: from groupy by lic711 with SMTP
(1.38.193.4/16.2) id AA13473; Thu, 19 Dec 1996 08:22:02 +1100
Received: from LIC#u#DOMAIN-Message_Server by lic.gov.au
with Novell_GroupWise; Thu, 19 Dec 1996 08:22:25 +1000
Message-Id: <s2b8fb41.093@lic.gov.au>
X-Mailer: Novell GroupWise 4.1
Date: Thu, 19 Dec 1996 08:22:25 +1000
From: Mailer-Daemon@lic.gov.au
To: ML-ERRORS@fatcity.com
Subject: Message status - opened
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=_3D6EBAB1.32533F60"
The message that you sent was opened by the following:
jobejne
Information about your message:
Subject: Re: How do I use aggregate keys in Des/2000?
Message-Id: <F001.0C70341A.19961218064832@fatcity.com>
----- end sample message -----
Follow-Ups:
|
|