[...Stuff deleted about my problem with Novell Groupwise...]
Thanks for all the replies, gang! I guess I wasn't clear about my
problem, however... Here are some important facts:
1) I am NOT administering a Groupwise/Novell configuration. I am a
mailing list administrator who has *subscribers* (elsewhere on the
Internet) that are using Groupwise. This also occurs on many .gov
installations, but not quite as frequently (thank gosh).
2) I am NOT using a COTS MLM. I have my own MLM that I wrote (had to),
therefore I am VERY familiar with what headers are going out with a
message. I promise that there are no Return-Receipt: or
X-Confirm-Reading-To: headers. In fact, here is an example of a
recent message with all the headers I put in my messages:
----- begin included file -----
Message-ID: <F001.0C703481.19961219002817@fatcity.com>
Date: Thu, 19 Dec 1996 00:28:17 -0800
To: Multiple recipients of list ODTUG-L <ODTUG-L@fatcity.com>
X-Comment: ODTUG Administrative List
X-Sender: bruceb@fatcity.com (Bruce Bergman)
Sender: root@fatcity.com
Reply-To: ODTUG-L@fatcity.com
Errors-To: ML-ERRORS@fatcity.com
From: bruceb@fatcity.com (Bruce Bergman)
Subject: Christmas Present: Developer/2000 bug fixed by Oracle!
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Organization: Fat City Network Services, San Diego, California
X-ListServer: v0.9d, build 45; FCListServ (c) 1996 Bruce A. Bergman
Precendence: bulk
----- end included file -----
3) I strip out obnoxious/annoying headers, so they aren't sneaking in
from user submissions. There are no offending headers in the
incoming messages that are being redistributed. As far as I can tell
(and without watching every single message for a day), I get these
replies from Groupwise with every outgoing message, regardless of
message content, headers, etc.
Now, two more interesting facts:
1) If I remove the Errors-To: header, the "message opened" replies come
to the sender (root, in this case). Leaving it in, at least they go
to the address specified in that header. So Groupwise is at least
aware of the Errors-To: header.
2) Talking to the administrators of the offending Groupwise systems
isn't really helpful. The admin responses have varied from ignoring
me completely, to saying its my fault, to telling me "that's tough"
and blowing me off. None have offered to fix it on their end.
(Maybe it's a psychological problem with Groupwise admins... ;-)
Unfortunately, I can't REALLY just drop the subscribers with this
problem, since some lists aren't mine and I prefer not to impose that
kind of iron-will on someone else's lists. If this becomes a bigger
issue, however, I WILL drop the offending subscriber sites. As it
stands now, I have a process which cleans these out of the mailbox, but
as you can tell, that's not the *ideal* solution.
What I was hoping to hear is that there is some header that Groupwise
looks for in re-directing the "message opened" responses to. For
example, something like a X-Groupwise-Reply-To: or whatever. Barring
that, maybe some magic incarnation I can say while waving a copy of the
Camel Book over my server... :-D
Personally, this is just one more reason to boycott Novell, and I'm not
going to be reticent to say so in the future. Basically, this sucks.
Suggestions of ANY kind are most welcome at this point. ;-)
thanks,
bruce
Follow-Ups:
|
|
