procmail
[Top] [All Lists]

Re: The header field that would not die...

1997-08-08 13:47:00
In the SmartList header below, there's a "Resent-From" field (second from
the top). SmartList *used* to put such a field in itself, but I stopped it
by modifying rc.submit. I don't want that field in there.
I don't want the field because it confuses the AOL mail system something
awful and this makes the AOLers complain. Any suggestions appreciated.

It confuses my procmail too, and subsequently, Pine.  But unix users are not
allowed to complain.

This is how your message looks in my inbox:

  PINE 3.95   FOLDER INDEX               Folder: INBOX  Message 2 of 6
->    1                                            [ No Message Text Available ]
      2 Aug  8 SmartBiz(_at_)NevWest(_dot_)com                 (2,497) EARN 
$2,000-5,000/Week Part Time


And this is what it looks like in my spool:
From type2-request(_at_)bigkitty(_dot_)azaccess(_dot_)com  Fri Aug  8 14:47:18 
1997
Received: from mail2.bellsouth.net (mail2.bellsouth.net [205.152.16.6])
    by mail.mem.bellsouth.net (8.8.5/8.8.5) with ESMTP id MAA21056
    for <bighouse(_at_)mem(_dot_)bellsouth(_dot_)net>; Fri, 8 Aug 1997 12:03:40 
-0400 (EDT)
Resent-From: type2-request(_at_)bigkitty(_dot_)azaccess(_dot_)com
Received: from bigkitty.azaccess.com 
(slist(_at_)bigkitty(_dot_)azaccess(_dot_)com
Status: RO
X-Status:

[206.62.242.4])
    by mail2.bellsouth.net (8.8.5/8.8.5) with ESMTP id MAA04405
    for <bighouse(_at_)bellsouth(_dot_)net>; Fri, 8 Aug 1997 12:03:38 -0400 
(EDT)
Received: (from slist(_at_)localhost) by bigkitty.azaccess.com (blue/stone) id
JAA21912 for bighouse(_at_)type2(_dot_)com; Fri, 8 Aug 1997 09:01:58 -0700
Resent-Date: Fri, 8 Aug 1997 09:01:58 -0700
Message-ID: <33EB4317(_dot_)23D1(_at_)execpc(_dot_)com>
Date: Fri, 08 Aug 1997 11:02:31 -0500
From: Andy McKinley <airhedz(_at_)execpc(_dot_)com>
Reply-To: airhedz(_at_)execpc(_dot_)com
Organization: airhedz
X-Mailer: Mozilla 3.01C-KIT  (Win95; I)
MIME-Version: 1.0
To: 0394*gf <avis(_at_)globalfrontiers(_dot_)com>
CC: Type2 listposting <type2(_at_)bigkitty(_dot_)azaccess(_dot_)com>
Subject: Re: Seat belts
References: <l03102801b01038a3a533(_at_)[205(_dot_)152(_dot_)250(_dot_)18]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Resent-Message-ID: <"3gYMMC.A.8VF.dL06z"@bigkitty.azaccess.com>
X-Mailing-List: <type2(_at_)bigkitty(_dot_)azaccess(_dot_)com> 
archive/latest/1668
X-Loop: type2(_at_)bigkitty(_dot_)azaccess(_dot_)com
Precedence: list
Sender: type2(_at_)bigkitty(_dot_)azaccess(_dot_)com
X-UIDL: 41b4e99a3f031c9b043700fbb9a3869a


--Ken
           68 Westy, Admin -- type2 -- The VW Bus Mailing List


____O/___
    o\

It passed through the following recipes:

:0:
* type2(_at_)bigkitty(_dot_)azaccess(_dot_)com
type2

(which DID NOT deliver it, therefore, it did not understand the header,
because of the CR after X-Status I think)

:0:
* procmail(_at_)Informatik(_dot_)RWTH-Aachen(_dot_)DE
procmail

(Which it deliver, but the attachment was left in my mailspool; obviously a 
separate message from POP3)


I don't know if this is of any use to anyone.

--
g-r-a-t-e-f-u-l-l-y---[   email:<fishbowl(_at_)conservatory(_dot_)com>   
]---l-i-v-i-n-g
d-e-a-d-i-c-a-t-e-d---[     http://www.conservatory.com/      ]-----l-i-g-h-t
Batteries not included.

<Prev in Thread] Current Thread [Next in Thread>