[Mailman-Users] Mailman Blocking Squirrelmail: Bad headers?

[Brad Knowles]

At 10:03 PM -0700 2004/06/01, Karl R. Balsmeier wrote:

>  I'm using Mailman 2.1.2 on obsd.
>
>  I've seen a few threads that match my current situation:
>
>  I am unable to get mails from squirrelmail-based https sessions to get to
>  the lists I have curently working properly for all other methods of
>  posting/replying.  Joining works, but posting does not.

	Are you using the same account for posting this message?  Looking 
through the headers of this message, I don't see anything obviously 
bad:

Received: from localhost ([127.0.0.1] helo=mail.python.org)
	by mail.python.org with esmtp (Exim 4.34)
	id 1BVNus-0005hW-Bx; Wed, 02 Jun 2004 01:03:54 -0400
Received: from 209-128-81-025.bayarea.net ([209.128.81.25]
	helo=mail.sfdata.net) by mail.python.org with smtp (Exim 4.34)
	id 1BVNun-0005ct-GR
	for mailman-users at python.org; Wed, 02 Jun 2004 01:03:50 -0400
Received: (qmail 3007 invoked from network); 2 Jun 2004 05:03:47 -0000
Received: from localhost (HELO eugenia.sfdata.net) (127.0.0.1)
	by localhost with SMTP; 2 Jun 2004 05:03:47 -0000
Received: from 216.175.80.132 (SquirrelMail authenticated user karl at sfdata.net)
	by eugenia.sfdata.net with HTTP; Tue, 1 Jun 2004 22:03:47 -0700 (PDT)
Message-ID: <9630.216.175.80.132.1086152627.squirrel at eugenia.sfdata.net>
Date: Tue, 1 Jun 2004 22:03:47 -0700 (PDT)
From: "Karl R. Balsmeier" <karl at sfdata.net>
To: mailman-users at python.org
User-Agent: SquirrelMail/1.4.2-1.qvcs.1
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
X-Spam-Status: OK (lists-mailman 0.000)
Subject: [Mailman-Users] Mailman Blocking Squirrelmail: Bad headers?
X-BeenThere: mailman-users at python.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: karl at sfdata.net
List-Id: Mailman mailing list management users <mailman-users.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/listinfo/mailman-users>,
	<mailto:mailman-users-request at python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/mailman-users>
List-Post: <mailto:mailman-users at python.org>
List-Help: <mailto:mailman-users-request at python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/mailman-users>,
	<mailto:mailman-users-request at python.org?subject=subscribe>
Sender: mailman-users-bounces at python.org
Errors-To: mailman-users-bounces at python.org
X-UIDL: 4590d50273837a949a03ad3b00e1427a

>  http://mail.python.org/pipermail/mailman-users/2002-June/020336.html
>
>  Anyone else out there seen the same problem and rendered a fix?

	This is the first I've heard of this problem.  It sounds to me 
like SquirrelMail may sometimes put some strange headers on your 
outgoing mail, and there would be two ways to fix that -- either 
configure the remote Mailman not to filter on those headers, or 
configure the local SquirrelMail server not to put them on there in 
the first place.

	Alternatively, this could be a body content filtering issue, but 
the solutions are basically the same.  If we can see some samples of 
what is getting rejected and compare that to what should be accepted, 
we might be able to figure out how to get from point A to point B.

-- 
Brad Knowles, <brad.knowles at skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

   SAGE member since 1995.  See <http://www.sage.org/> for more info.