[horde] Horde bug tracker

Jan Schneider jan at horde.org
Thu Sep 18 22:16:52 UTC 2008


Zitat von Michael M Slusarz <slusarz at horde.org>:

> Quoting Vince LaMonica <vjl at cullasaja.com>:
>
>> On Thu, 18 Sep 2008, Andrew Morgan wrote:
>>
>> } X-Spam-Status: Yes, score=5.422 tagged_above=-999 required=5
>> }     tests=[INVALID_MSGID=2.603, MIME_QP_LONG_LINE=1.819, SPF_SOFTFAIL=1]
>> } Message-ID: <whups-7357-727a0a3d43ca17432459a2b9c2d313d6-bugs.horde.org>
>> }
>> } The big killer seems to be INVALID_MSGID=2.603.  I'm not sure  
>> what is invalid
>> } about the Message-ID, but perhaps that could be fixed in Whups so  
>> that these
>> } messages don't end up tagged as spam?
>>
>> Looks like the Message-ID field is missing an "@" symbol. Normally the end
>> of a message-id contains the host/domain name it was sent from. If you
>> sent it from bugs.horde.org, then the "-" before "bugs" should really be
>> "@" instead.
>
> This is correct.  RFC 2822 [3.6.4] does require the '@':
> msg-id          =       [CFWS] "<" id-left "@" id-right ">" [CFWS]
>
> So we should fix this.

Done. This might explain why my server always refused to generate  
proper threads.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/



More information about the horde mailing list