Hello, I inherited responsibility for a UNIX (HP-UX 10.20) mail server running Smartlist with several mailing lists. I've read the FAQ's, Smartlist manual, and the appropriate sections of the Mailing Lists book by O'Reilly but I couldn't find an answer to one of my current problems. Additionally the mail messages will be composed in Microsoft Outlook. When I (or anyone else for that matter), subscribes/unsubscribes to a list they get the appropriate message and a bunch of information appended at the bottom. An example will follow at the end of this email. The questions are: 1) Why is this happening? 2) Can it be prevented? Thanks in advance. Tom O'Rourke Example: ----
From TORourk@hq.odedodea.edu Wed Dec 6 09:01:28 2000 Received: from hq.odedodea.edu (hq.odedodea.edu [192.156.209.69]) by myserver.odedodea.edu (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id JAA22104 for <boguslist@myserver.odedodea.edu>; Wed, 6 Dec 2000 09:01:27 -0500 (EST) Received: by hq.odedodea.edu with Internet Mail Service (5.5.2650.21) id <YKRTV0XT>; Wed, 6 Dec 2000 09:05:36 -0500 Message-ID: <654C545F67BFD21188A90008C7D90ECD08E34DD0@gpj4383-3.odedodea.edu> From: "O'Rourke, Tom (CTR)" <TORourk@hq.odedodea.edu> To: "'boguslist@myserver.odedodea.edu'" <boguslist@myserver.odedodea.edu> Subject: subscribe Date: Wed, 6 Dec 2000 08:58:37 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C05F8C.A1252480"
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.
------_=_NextPart_001_01C05F8C.A1252480 Content-Type: text/plain; charset="iso-8859-1"
------_=_NextPart_001_01C05F8C.A1252480 Content-Type: text/html; charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2651.75"> <TITLE>subscribe</TITLE> </HEAD> <BODY>
</BODY> </HTML> ------_=_NextPart_001_01C05F8C.A1252480--
----
At 9:57 AM -0500 12/6/00, O'Rourke, Tom (CTR) is rumored to have typed:
1) Why is this happening?
What they receive is a copy of the message they sent initially to subscribe; if someone else forge-subscribed them against their will, this copy will show the path of the subscription message for use in tracking down the miscrient. The fact that it looks ugly is Microsoft's fault, since Outlook defaults to sending a simple one-word subscription request as a huge HTML email message. (Look carefully at the message, and you'll see tucked in there amid all the HTML tags and other unnecessary garbage is the one word you typed - "subscribe")If I subscribe to your list, using a text/plain message, it would look considerably better but would still contain the Received: header fields necessary for making sure the request came from me and not from someone else.
2) Can it be prevented?
Why in heavens name would you _want_ to prevent a copy of the original subscription request from being included in the message? How would a user track down someone forge-subscribing them otherwise? Charlie
participants (2)
-
Charlie Summers -
O'Rourke, Tom (CTR)