Your message dated Wed, 16 Apr 2014 22:49:46 -0600
with message-id <[email protected]>
and subject line Re: Bug#739933: spamassassin: Spamassassin scans mail to
localhost
has caused the Debian Bug report #739933,
regarding spamassassin: Spamassassin scans mail to localhost
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
739933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739933
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: spamassassin
Version: 3.4.0-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I noticed that spam to myself was flagged as spam
* What exactly did you do (or not do) that was effective (or
ineffective)?
Nothing
* What was the outcome of this action?
N/A
* What outcome did you expect instead?
I mailed a simple e-mail to myself and it was scanned. Why? Everything
I can find on the web says that by default this e-mail should not be scanned
but it is, look at the headers:
>From [email protected] Mon Feb 24 01:28:30 2014
Return-Path: <[email protected]>
Received: from bandsman.co.uk (bandsman.co.uk [127.0.0.1])
by bandsman.co.uk (8.14.4/8.14.4/Debian-5) with ESMTP id s1O1SSaT027619
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
verify=NOT)
for <[email protected]>; Mon, 24 Feb 2014 01:28:28 GMT
Received: (from njh@localhost)
by bandsman.co.uk (8.14.4/8.14.4/Submit) id s1O1SShd027565
for njh; Mon, 24 Feb 2014 01:28:28 GMT
Date: Mon, 24 Feb 2014 01:28:28 GMT
From: Nigel Horne <[email protected]>
Message-Id: <[email protected]>
To: [email protected]
Subject: test
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,BAYES_00,
DATE_IN_FUTURE_24_48,RP_MATCHES_RCVD autolearn=no autolearn_force=no
version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
nigelhorne.force9.co.uk
test
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages spamassassin depends on:
ii adduser 3.113+nmu3
pn libarchive-tar-perl <none>
ii libhtml-parser-perl 3.71-1+b1
ii libnet-dns-perl 0.68-1.2
ii libnetaddr-ip-perl 4.071+dfsg-1
ii libsocket6-perl 0.25-1
ii libsys-hostname-long-perl 1.4-3
ii libwww-perl 6.05-2
ii perl 5.18.2-2
ii perl-modules [libio-zlib-perl] 5.18.2-2
Versions of packages spamassassin recommends:
ii gnupg 1.4.16-1.1
ii libio-socket-inet6-perl 2.71-1
ii libmail-spf-perl 2.9.0-2
ii perl [libsys-syslog-perl] 5.18.2-2
ii sa-compile 3.4.0-1
ii spamc 3.4.0-1
Versions of packages spamassassin suggests:
ii libdbi-perl 1.631-1
ii libio-socket-ssl-perl 1.967-1
pn libmail-dkim-perl <none>
ii perl [libcompress-zlib-perl] 5.18.2-2
ii pyzor 1:0.5.0-2
ii razor 1:2.85-4+b2
-- Configuration Files:
/etc/default/spamassassin changed:
ENABLED=1
OPTIONS="--create-prefs --max-children 5 --helper-home-dir"
PIDFILE="/var/run/spamd.pid"
CRON=1
-- no debconf information
--- End Message ---
--- Begin Message ---
Nigel Horne wrote:
> Noah Meyerhans wrote:
> > There would be no way for spamassassin to recognize a mail as
> > originating from localhost without scanning it. If you don't want
> > spamassassin to look at locally originated mail, that's a local
> > configuration issue.
>
> I see two options here
>
> 1) preferable - tell sendmail not to scan outgoing e-mails
> 2) alternative - white list outgoing e-mails.
>
> Could you please advise me on how to go about that? Or point me to a
> clearly written URL?
Previously you said you were using spamass-milter. I think the answer
to your question lies there with spamass-milter. I don't use it and
don't know it and so, no, I can't advise you about how to do it. I
guess that Noah doesn't either. Please contact the spamass-milter
maintainers for help about it.
> > Or, to put this another way, by default spamassassin doesn't see any
> > mail at all. It's entirely up to you to pipe mail to spamassassin or
> > spamc/spamd. If you choose to pipe locally generated mail to the filter,
> > there's nothing spamassassin can do to avoid seeing it. If milter
> > includes rules by default that pass mail through spamassassin, then you
> > may want to follow up with the milter maintainers to ask them about
> > changing that behavior.
> >
> > Note that spamassassin did recognize that the message originated within
> > your local environment, which is why it triggers the ALL_TRUSTED rule.
>
> The problem arose because an outgoing e-mail of mine that had a spam sample
> attached was blocked locally. That was bad news and something I need to
> avoid happening again.
Sorry but you will need to investigate the spamass-milter configuation
elsewhere. It is a different package and project from spamassassin.
It has been two months and apparently no one associated with the
spamassassin project here knows anything about about spamass-milter
and how you are using it. There hasn't been any more input about it.
Therefore I am going to close this bug against spamassassin as having
been resolved sufficiently from the perspective of the spamassassin
packaging. If you are still having a problem I suggest filing your
bug against the spamass-milter package with a fresh set of information
regarding the issues and with the light of the information learned
here.
Bob
signature.asc
Description: Digital signature
--- End Message ---
