Sorry- I meant shouldn't this be added by qmail-local on delivery.  I guess I am trying to figure out why it isn't properly adding it.
-M

Michael Krieger <[EMAIL PROTECTED]> wrote:
Somewhat off-topic, but I'm imagining that somewhere in the mix is where this is all beginning.

This is an example of a [junk but unscanned] message [slightly edited for the actual e-mail addresses, though mostly should be the same] that was received.  You'll notice the Return-Path: fails to have any data or a newline after it, being prepended to a received line that already exists.

I then get this in my qmail log file: qmail-inject:_fatal:_unable_to_parse_this_line:/Return-Path:_Received:_...
when it tries to forward the mail based on a .qmail file.

So my question is where would this be allowed into the system?  Shouldn't qmail-smtpd (and simscan) be adding a proper return path based on the senders' from address when it passes it along for the initial delivery?

Received: (qmail 27397 invoked by uid 89); 8 May 2006 13:12:31 -0400
Received: by simscan 1.2.0 ppid: 27387, pid: 27395, t: 0.0977s
         scanners: clamav: 0.88.2/m:38/d:1448
DomainKey-Status: no signature
Received: from unknown (HELO 211.57.43.201) (211.57.43.201)
  by suede.mydomain.com with SMTP; 8 May 2006 13:12:28 -0400
Received-SPF: neutral (suede.mydomain.com: 211.57.43.201 is neither permitted nor denied by SPF record at _spf.google.com)
Return-Path: Received: from keith.lloyd.com (keith.lloyd.com [158.222.0.2]) by mailgate.yorkinternet.net with ESMTP; May, 08 2006 12
:03:14 PM -0300
Received: from mail.bellsouth.com (mail.bellsouth.com [139.76.165.130]) by mail.landg.com with smtp; May, 08 2006 10:54:17 AM -0300
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Atuh stock is on the move !!! Could double in a week qqkl
Sender: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Date: Mon, 8 May 2006 12:12:27 -0500
X-Mailer: Microsoft Outlook Build 10.0.2616

Any help is apprecaited,
-M


Reply via email to