[Bug 4747] new EnvelopeFrom auto-detection needs doco

[bu...@bugzilla.spamassassin.org]

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4747


Mark.Martinec@ijs.si changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Mark.Martinec@ijs.si




------- Additional Comments From Mark.Martinec@ijs.si  2007-03-28 09:58 -------
I'm posting here below part of the discussion on SA users ML on
March 8 2007, subject 'NOTICE: SpamAssassin 3.2.0-pre2 PRERELEASE
available'. It was somehow forgotten (partly also my fault),
but the noisy warnings are still filling my logs with SA 3.2.0-rc1.

The short story is:
  Each bounce mail (with null return path) produce two warnings:

[59483] warn: message:
  envelope_sender_header '' is not an FQDN - ignoring
  at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
  line 2306.
[59483] warn: message:
  envelope_sender_header '' is not an FQDN - ignoring
  at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm
  line 2306.
(not at initialization time, but later during mail processing)

Here is a short mail that demonstrates it:

  Return-Path: <>
  Date: Wed, 28 Mar 2007 17:23:33 +0100
  From: mailer-daemon@example.net
  To: user@example.com
  Message-ID: <ma...@example.net>
  Subject: test

  test

A command like 'spamassassin -t <0.msg >/dev/null' produces the
above two warnings, but if Return-Path: <xx...@example.net> is used,
there are no warnings.

I use the following settings in local.cf:
  always_trust_envelope_sender 1
  envelope_sender_header  Return-Path


Here is the original thread:

On Tuesday 06 March 2007 23:53, Mark Martinec wrote:
> Btw, the following warnings (in v320) seem excessive, a null return path
> (aka envelope sender) is normal and constitute few percent of all mail:
> message: envelope_sender_header '' is not an FQDN - ignoring

Nick Leverton <nj...@leverton.org> writes:
  This may be due to my bugs 4717 and 4718.  My changes were supposed to 
treat <> properly and predictably, rather than silently ignoring null 
sender as happened previously whenever envelope-from couldn't be deduced 
from the Received: line.  But I have been through some nasty personal 
stuff recently and never got back to the devs' questions about my issues, 
so I think they didn't take the full set of fixes.

If you're only seeing this on startup, Mark, I think it's probably related 
to the formatting of the dummy mails SA uses to initialise everything, as 
I have seen the same thing in our logs when Amavis starts.  If you're 
seeing it on real null senders please let me know.

It certainly shouldn't be so noisy, I'll have a look this evening if they 
let me out of here in time, otherwise tomorrow - can you all wait that 
long ?




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.