On 10/25/2014 9:29 PM, John Hardin wrote:
On Sat, 25 Oct 2014, Cathryn Mataga wrote:
Received: from ecuador.junglevision.com (localhost [127.0.0.1]) by
ecuador.junglevision.com (8.14.7/8.14.7) with ESMTP id s9P2o1ZZ026032
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
verify=NO) for <megans...@junglevision.com>; Fri, 24 Oct 2014
19:50:01 -0700
Received: (from megan@localhost) by ecuador.junglevision.com
(8.14.7/8.14.7/Submit) id s9P2o1dN026031 for
megans...@junglevision.com; Fri, 24 Oct 2014 19:50:01 -0700
Why is the message hitting ecuador.junglevision.com twice?
Would this do it? Maybe it's just failing on the initial spam check and
then .procmailrc meganspam checks again for some reason?
[root@ecuador megan]# cat .procmailrc
:0
* ^Subject:.*\[SPAM\]*
!megans...@junglevision.com
[root@ecuador etc]# pwd
/etc
[root@ecuador etc]# cat procmailrc
DROPPRIVS=yes
INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc
Then I have.
[root@ecuador spamassassin]# cat spamassassin-default.rc
# send mail through spamassassin
:0fw
| /usr/bin/spamassassin
Don't believe there's anything creative happening here, right? Am I
missing something obvious?
