[Exim] Any idea why require_verify=headers_sender would trip…

Página Inicial
Delete this message
Reply to this message
Autor: Suresh Ramasubramanian
Data:  
Para: exim-users
Assunto: [Exim] Any idea why require_verify=headers_sender would trip on this?
Sourceforge (which runs Exim) seems to object to several bounces we are
sending them, and the bounce is typical of require_verify=headers_sender

>>> From: MAILER-DAEMON@??? - the mta5-2 machine does

have an A record (but no MX - it is a mailhub host anyway)

Any idea where this check is getting tripped?

         srs


>spf2# cat /var/spool/mqueue/q1/qfh429kq550269
>V4
>T1051868812
>K1051883757
>N3
>P215539
>I116/131076/636027
>MDeferred: 451-Cannot accept 'From:' header address
>MAILER-DAEMON@???
>Fb
>$_202-77-181-23.outblaze.com [202.77.181.23]
>$rESMTP
>$smg.hk5.outblaze.com
>${daemon_flags}
>${if_addr}202.77.181.64
>S<>
>RPFD:<linux-india-programmers-admin@???>
>H?P?Return-Path: <g>
>H??Received: from mg.hk5.outblaze.com (202-77-181-23.outblaze.com
>[202.77.181.23])
>         by spf2.outblaze.com (8.11.7/8.11.7/srs) with ESMTP id h429kq550269
>         for <linux-india-programmers-admin@???>; Fri, 2
> May 2003 09:46:52 GMT
>H??X-Authentication-Warning: spf2.outblaze.com: Host
>202-77-181-23.outblaze.com [202.77.181.23] claimed to be mg.hk5.outblaze.com
>H??Received: from mta1-3.us4.outblaze.com (205-158-62-44.outblaze.com
>[205.158.62.44])
>         by mg.hk5.outblaze.com (8.12.9/8.12.9/srs) with ESMTP id
> h427iDWl013879
>         for <linux-india-programmers-admin@???>; Fri, 2
> May 2003 07:44:14 GMT
>H??Received: from mta5-2.us4.outblaze.com (205-158-62-145.outblaze.com
>[205.158.62.145])
>         by mta1-3.us4.outblaze.com (Postfix) with SMTP id 880236EC14D
>         for <linux-india-programmers-admin@???>;
> Fri,  2 May 2003 07:44:13 +0000 (GMT)
>H??Received: (qmail 10890 invoked for bounce); 2 May 2003 07:43:55 -0000
>H??Date: 2 May 2003 07:43:55 -0000
>H??From: MAILER-DAEMON@???
>H??To: linux-india-programmers-admin@???
>H??Subject: failure notice
>H??Message-Id: <20030502074413.880236EC14D@???>
>.