The mailing list for listmasters using Sympa

["Patrick von der Hagen" <address@concealed>]

Hi all,

I have a problem with one of the lists I recently migrated from listserv
to sympa. There is a address at a big german provider which is
configured to forward all messages to the mailinglist.
Most of the list-traffic first passes through this provider.
The provider started to add Headers reporting on SPF-checks. Now the
incoming messages look like this:

Received: from moutng.kundenserver.de (moutng.kundenserver.de
[212.227.126.186])
        by spametec.rz.uni-karlsruhe.de with esmtp (Exim 4.50 #1)
        id 1Gozx9-0000Jw-02 for address@concealed; Tue,
28 Nov 2006 11:12:43 +0100
Received-SPF: none (mxeu4: 129.13.185.218 is neither permitted nor
denied by domain of somewhere.de) client-ip=129.13.185.218;
address@concealed; helo=smtp2.rz.uni-karlsruhe.de;
Received: from [129.13.185.218] (helo=smtp2.rz.uni-karlsruhe.de)
        by mx.kundenserver.de (node=mxeu4) with ESMTP (Nemesis),
        id 0MKqlY-1Gozx81aBD-0007GM for address@concealed;
Tue, 28 Nov 2006 11:12:38 +0100

Sympa refuses to process those messages and sends a bounce. As a
listmaster I'm informed about the error and are told to have a look at
the logfiles. Those files do not contain any more information, but when
I remove the Received-SPF-line and reinject the message, it is processed
without any problems.

Looks like sympa does not like the Received-SPF-Header. I don't relly
like it either, but I consider it to be valid.

Any comments regarding that issue? I know to little about SPF to be able
to judge this behaviour as "strange", "normal" or something like that,
so I don't know how to handle this issue.

-- 
CU,
   Patrick.

Attachment: smime.p7s
Description: S/MIME cryptographic signature