At 02:20 PM 12/18/96 GMT, Bruce Bergman wrote:
>Hey folks --
>
>Here's one for the masses. This has been driving nuts, but fortunately
>I can redirect the annoying message to another account.
Well, with UNIX, you could use procmail and direct them to /dev/null.
But if "hundreds" is correct, you should want to stop the traffic.
>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.
Can you post one of your *outgoing* messages' full headers?
What kind of list are you running? My suspicion is that somehow you've
got something like a "Return-Receipt-To:" header. If so, you want to
nuke that!
I can't believe that Novell Groupwise *always* sends that, or else
when one user wrote another, they'd see:
"I read your message"
"I read your receipt of my message"
"I read your receipt of my receipt of your message"
"I read your receipt of my receipt of your receipt of my message"
...ad nauseum...
and then *nobody* would use Groupwise at all for that reason.
Chances are, one of your outgoing header fields is what Groupwise interprets
as a request for acknowlegment.
>
>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... ;-)
Have one for me too ;-) Dilute it with rum; less fat per ounce then ;-)
My best guess, though, is that there's a header you need to remove,
not add. (Actually, "header field" is the correct term, but who's
keeping score anyway? :-)
>
>thanks,
>
>bruce
>----- begin sample message -----
[message snipped]
Cheers,
Stan.
|
|
