

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] couriermlm, SpamA...| From | Sent On | Attachments |
|---|---|---|
| Bill Taroli | Feb 14, 2004 12:31 am | |
| Bill Taroli | Feb 15, 2004 3:51 pm |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] couriermlm, SpamAssassin, and digest messages | Actions... |
|---|---|---|
| From: | Bill Taroli (bill...@billsden.org) | |
| Date: | Feb 15, 2004 3:51:42 pm | |
| List: | net.sourceforge.lists.courier-users | |
Well, figured it out. Seems that a blank line at the end of the headeradd file was the culprit. I noted it and removed it, just as a tidiness issue, and now the digests are coming through with correct headers.
Bill Taroli wrote:
Just configured a couriermlm (v 0.44) list for digests. Seems to be working OK, but I am noticing a peculiar issue in the header of the generated messages that is causing a problem in MIME decoding. Following is a sample header from one of the digest messages.
X-Scanned-By: AMaViS-ng 0.1.6.4 on mail.billsden.org Delivered-To: ww...@billsden.org Return-Path: <suesbigday-digest-bounce-2-wwt=bill...@billsden.org> Received: from localhost (localhost [127.0.0.1]) (uid 117) by mail.billsden.org with local; Fri, 13 Feb 2004 23:20:33 -0800 List-Subscribe: <mailto:sues...@billsden.org> List-Unsubscribe: <mailto:sues...@billsden.org> List-Post: <mailto:sues...@billsden.org> List-Owner: <mailto:sues...@billsden.org> List-Help: <mailto:sues...@billsden.org> Reply-To: sues...@billsden.org From: sues...@billsden.org Message-ID: <cour...@billsden.org> Date: Fri, 13 Feb 2004 23:20:33 -0800 To: undisclosed-recipients: ; X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on jeff.billsden.org X-Spam-Level: X-Spam-Status: No, hits=-4.5 required=5.0 tests=BAYES_00,HTML_MESSAGE, HTML_TITLE_EMPTY,NO_REAL_NAME autolearn=no version=2.61
From: "Courier Mailing List Manager" <sues...@billsden.org> To: sues...@billsden.org Subject: Courier Mailing List Digest #2 Mime-Version:1.0 Content-Type: multipart/digest; boundary="reformime_1076743233_1"
There are two issues here. First, there are two "From" and "To" headers. I have not specifically included From or To in either headeradd or headerdel (for the digest) and the options file gives sues...@billsden.org as the ADDRESS. Why is the first From/To line (from the regular list) being inserted?
Second, and apparently more damaging from the perspective of MIME decoding, is the blank line between X-Spam-Status and the second From header. I'm not entirely sure if this is being injected at the time the message is generated by couriermlm or whilst it's flowing through maildrop and SA. But I have found that if I manually edit the file to remove this blank line -- even in the presence of the two From and To headers -- the message renders properly in email viewers.
I've read several times through couriermlm manpage, especially the bits for digests, and all appears as requested there. Any suggestions, pointers, or additional questions to clarify what might be going on here? I grant that I may be doing something bone-headed, since this is the very first time I am using couriermlm, and first for digest config on top of that.
TIA
Bill
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________ courier-users mailing list cour...@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users







