D'oh nothing =(
Return-Path: <wi...@xxx.com>
Delivered-To: de...@geekzone.com.uy
Received: (qmail 22442 invoked by uid 89); 22 Jan 2011 01:25:23 -0000
Received: from unknown (HELO xxx.com) (208.110.83.154)
by mx.xen30.node01001 with (DHE-RSA-AES256-SHA encrypted) SMTP; 22 Jan
2011 01:25:23 -0000
Received-SPF: none (mx.xen30.node01001: domain at xxx.com does not designate
permitted sender hosts)
Received: (qmail 10908 invoked by uid 89); 22 Jan 2011 01:25:21 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=private; d=xxx.com;
b=BowgCbJUIT8JXP5SJGcjB5D1ByFQGodQSxI1kGp1Rf3gjtv0z7xZBCILsFG265Yr;
Received: from unknown (HELO webmail.xxx.com) (wi...@xxx.com@127.0.0.1)
by mx.xxx.com with ESMTPA; 22 Jan 2011 01:25:21 -0000
Received: from 186.48.208.107
(SquirrelMail authenticated user wi...@xxx.com)
by webmail.xxx.com with HTTP;
Fri, 21 Jan 2011 19:25:21 -0600
Message-ID: <6e2e63dd730a50f52dcfca4a172dec85.squir...@webmail.xxx.com>
Date: Fri, 21 Jan 2011 19:25:21 -0600
Subject: doh
From: "Mace Windu" <wi...@xxx.com>
To: de...@geekzone.com.uy
Reply-To: wi...@xxx.com
User-Agent: SquirrelMail/1.4.20-1.3.17
MIME-Version: 1.0
Content-Type: multipart/mixed;boundary="----=_20110121192521_34248"
X-Priority: 3 (Normal)
Importance: Normal
Just in case:
# cat /etc/tcprules.d/tcp.smtp
127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",QMAILQUEUE="/var/qmail/bin/qmail-queue",NOP0FCHEC="1"
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",DKSIGN="/var/qmail/control/domainkeys/%/private",QMAILQUEUE="/var/qmail/bin/qmail-queue",NOP0FCHEC="1"
Bruno
On Fri, Jan 21, 2011 at 11:22 PM, Bruno De Leone <dele...@gmail.com> wrote:
> I never touched the tcp.smtp file before, not that I remember. I had to
> locate it to know where it was :P
>
> Both of my servers have the same tcp.smtp and they were installed on
> november 2010 and january 2011 so it might be missing on some source file.
>
> I'm adding the text you said and I'll report the results...
>
> Thanks!
>
> Bruno
>
>
> On Fri, Jan 21, 2011 at 10:47 PM, Eric Shubert <e...@shubes.net> wrote:
>
>> Do you know how:
>> ,QMAILQUEUE="/var/qmail/bin/qmail-queue",NOP0FCHEC="1"
>> came to be missing from the end of your :allow line?
>> You really need them both.
>>
>> If they're missing in some source package somewhere, that really needs to
>> be fixed.
>>
>> You might want/need them on the localhost (127.) line as well. I'm not
>> sure about this because I've removed the localhost line from my
>> configuration (I have Squirrelmail use port 587 and authenticate itself, so
>> it's consistent with settings for other submissions).
>>
>> --
>> -Eric 'shubes'
>>
>>
>> On 01/21/2011 05:14 PM, Bruno De Leone wrote:
>>
>>> # cat /etc/tcprules.d/tcp.smtp
>>>
>>>
>>> 127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private"
>>>
>>> :allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",DKSIGN="/var/qmail/control/domainkeys/%/private"
>>>
>>>
>>>
>>> On Fri, Jan 21, 2011 at 2:34 AM, Eric Shubert <e...@shubes.net
>>> <mailto:e...@shubes.net>> wrote:
>>>
>>> It appears from the header that simscan didn't process the message.
>>> What's in your tcp.smtp file?
>>>
>>>
>>> On 01/20/2011 05:12 PM, Bruno De Leone wrote:
>>>
>>> I disabled spamdyke and messages are arriving as before. I'll
>>> enable it
>>> again when I can make the configurations for it right.
>>>
>>> What worries me is that mails are not being scanned by
>>> spamassassin or
>>> clamav. I'm looking to the first test emails I sent when I
>>> finished
>>> installing both servers and I can't find any header indicating the
>>> emails were scanned.
>>>
>>> # cat /var/qmail/control/simcontrol
>>> :clam=yes,spam=yes,spam_hits=2000,attach=.zzz
>>>
>>> # cat /etc/mail/spamassassin/local.cf <http://local.cf>
>>> <http://local.cf>
>>>
>>> ok_locales all
>>> skip_rbl_checks 1
>>>
>>> required_score 5
>>> report_safe 0
>>> rewrite_header Subject ***SPAM***
>>>
>>> use_pyzor 1
>>>
>>> use_auto_whitelist 1
>>>
>>> use_bayes 1
>>> use_bayes_rules 1
>>> bayes_auto_learn 1
>>>
>>>
>>> Here is an email I sent from an account at adinet.com.uy
>>> <http://adinet.com.uy>
>>> <http://adinet.com.uy> to one of my toasters:
>>>
>>> Return-Path: <dele...@adinet.com.uy
>>> <mailto:dele...@adinet.com.uy> <mailto:dele...@adinet.com.uy
>>>
>>> <mailto:dele...@adinet.com.uy>>>
>>> Delivered-To: wi...@something.com <mailto:wi...@something.com>
>>> <mailto:wi...@something.com <mailto:wi...@something.com>>
>>>
>>>
>>> Received: (qmail 11069 invoked by uid 89); 24 Dec 2010 17:32:18
>>> -0000
>>> Received: from unknown (HELO smtp-s04.adinet.com.uy
>>> <http://smtp-s04.adinet.com.uy>
>>> <http://smtp-s04.adinet.com.uy>) (200.40.30.64)
>>> by mx.something.com <http://mx.something.com>
>>> <http://mx.something.com> with SMTP; 24 Dec
>>>
>>> 2010 17:32:18 -0000
>>> Received-SPF: pass (mx.something.com <http://mx.something.com>
>>> <http://mx.something.com>: SPF
>>> record at adinet.com.uy <http://adinet.com.uy>
>>> <http://adinet.com.uy> designates 200.40.30.64
>>>
>>> as permitted sender)
>>> Received: from fe-ps05 (192.168.2.209) by smtp-s04.adinet.com.uy
>>> <http://smtp-s04.adinet.com.uy>
>>> <http://smtp-s04.adinet.com.uy> (8.5.124.03) (authenticated as
>>> dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>
>>> <mailto:dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>>)
>>>
>>>
>>> id 4C7C4DE906BF2B95 for wi...@something.com
>>> <mailto:wi...@something.com>
>>> <mailto:wi...@something.com <mailto:wi...@something.com>>; Fri,
>>>
>>> 24 Dec 2010 15:32:13 -0200
>>>
>>> Received: from [190.135.66.162] by correo.adinet.com.uy
>>> <http://correo.adinet.com.uy>
>>> <http://correo.adinet.com.uy> via http; Fri Dec 24 14:32:12 UYT
>>> 2010
>>>
>>> Message-ID: <19047404.1293211933059.JavaMail.tomcat@fe-ps05>
>>> Date: Fri, 24 Dec 2010 14:32:13 -0300 (UYT)
>>> From: "dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>
>>> <mailto:dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>>"
>>>
>>> <dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>
>>> <mailto:dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>>>
>>>
>>> Reply-To: "dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>
>>> <mailto:dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>>"
>>>
>>> <dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>
>>> <mailto:dele...@adinet.com.uy <mailto:dele...@adinet.com.uy>>>
>>>
>>> To: wi...@something.com <mailto:wi...@something.com>
>>> <mailto:wi...@something.com <mailto:wi...@something.com>>
>>>
>>>
>>> Subject: hola!
>>> MIME-Version: 1.0
>>> Content-Type: text/plain;charset="UTF-8"
>>> Content-Transfer-Encoding: 7bit
>>> X-Originating-IP: 190.135.66.162
>>>
>>>
>>> Is there something I might have missed while installing
>>> spamassassin for
>>> it to run properly?
>>>
>>>
>>> Bruno
>>>
>>> On Thu, Jan 20, 2011 at 9:44 PM, Bruno De Leone
>>> <dele...@gmail.com <mailto:dele...@gmail.com>
>>> <mailto:dele...@gmail.com <mailto:dele...@gmail.com>>> wrote:
>>>
>>> Great! Thanks Eric!
>>>
>>> Bruno
>>>
>>>
>>> On Thu, Jan 20, 2011 at 8:45 PM, Eric Shubert
>>> <e...@shubes.net <mailto:e...@shubes.net>
>>> <mailto:e...@shubes.net <mailto:e...@shubes.net>>> wrote:
>>>
>>> # cd /var/qmail/supervise/smtp
>>> # ln -sf run.dist run
>>> # service qmail restart
>>>
>>> This will disactivate spamdyke. To reactivate it, replace
>>> run.dist with run.spamdyke.
>>>
>>> You may need to tweak spamdyke's configuration a little
>>> to get
>>> it working ideally in your environment. Sometimes you
>>> need to
>>> whitelist mail servers that are misconfigured, etc. Any
>>> problem
>>> you have with spamdyke is usually easy to remedy by
>>> adjusting
>>> its configuration.
>>>
>>> --
>>> -Eric 'shubes'
>>>
>>>
>>> On 01/20/2011 03:22 PM, Bruno De Leone wrote:
>>>
>>> I just realized the received mails are not being
>>> scaned by
>>> spamassasin
>>> and reading other mails I found spamdyke might be "my
>>> problem". I'm also
>>> not receiving some mails because of RDNS checks.
>>>
>>> How can I disable or remove Spamdyke until I can set
>>> everything right?
>>>
>>> Bruno.
>>>
>>> On Thu, Jan 20, 2011 at 4:50 PM, Cecil Yother, Jr.
>>> <c...@yother.com <mailto:c...@yother.com> <mailto:c...@yother.com
>>> <mailto:c...@yother.com>>
>>> <mailto:c...@yother.com <mailto:c...@yother.com>
>>> <mailto:c...@yother.com <mailto:c...@yother.com>>>> wrote:
>>>
>>>
>>>
>>> On 01/20/2011 10:45 AM, Eric Shubert wrote:
>>> >
>>> > On 01/20/2011 11:27 AM, Cecil Yother, Jr. wrote:
>>> >> Now, I'm thoroughly confused. What is the purpose of
>>> Simscan
>>> then if
>>> >> the file has already been scanned?
>>> >
>>> > Simscan does not itself do any scanning. It simply
>>> invokes other
>>> > scanners.
>>> I got this part.
>>> > The other scanners "report back" to simscan what the results
>>> were, and
>>> > simscan takes the care of rejecting messages
>>> appropriately. Simscan
>>> > isn't invoked after the scanners. Simscan invokes the
>>> other scanners,
>>> > which subsequently return control back to simscan, which
>>> subsequently
>>> > returns control back to qmail-smtpd.
>>> OK, now I understand
>>> >
>>> >> If spamassassin rejects it at 5
>>> >> what would Simscan ever do when it's set to 12?
>>> >
>>> > Spamassassin does no rejecting. SA simply scans and
>>> scores the
>>> > message, adds header records, tags the subject line when
>>> appropriate
>>> > (over 5), and returns control to simscan. It's simscan
>>> that does the
>>> > rejecting, based on spam_hits.
>>> Woohoo, I got it!
>>> >
>>> >> On 01/20/2011 09:51 AM, Eric Shubert wrote:
>>> >>> On 01/20/2011 10:39 AM, Maxwell Smart wrote:
>>> >>>>
>>> >>>> That's what I meant. When Simscan is run it starts
>>> spamd to
>>> scan based
>>> >>>> on the hits number in the simcontrol file and then if it
>>> passes that
>>> >>>> spamassassin scans it again using the local .cf file.
>>> Is that
>>> correct?
>>> >>>
>>> >>> No. spamassassin only scans once. simscan applies
>>> spam_hits *after*
>>> >>> spamassassin is done scanning.
>>> >>>
>>> >>>> Basically Simscan is a gatekeeper/bouncer. If you
>>> don't get past
>>> >>>> Simscan
>>> >>>> you don't get the patdown by spamassassin.
>>> >>>
>>> >>> Not exactly. Simscan only rejects based on the result
>>> of the
>>> scanners
>>> >>> that it invokes. local.cf <http://local.cf> <http://local.cf
>>> >
>>> <http://local.cf> comes first, then
>>>
>>> spam_hits.
>>> >>>
>>> >>>>
>>> >>>> On 01/20/2011 09:32 AM, Eric Shubert wrote:
>>> >>>>> No. simscan does no scanning. It simply takes action
>>> (rejects
>>> some
>>> >>>>> messages) based on the result of scanners that in invokes
>>> (clamav and
>>> >>>>> spamassassin).
>>> >>>>
>>> >>>
>>> >>>
>>> >>
>>> >
>>> >
>>>
>>> --
>>> Cecil Yother, Jr. "cj"
>>> cj's
>>> 2318 Clement Ave
>>> Alameda, CA 94501
>>>
>>> tel 510.865.2787 | http://yother.com
>>> Check out the new Volvo classified resource
>>> http://www.volvoclassified.com
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------------------
>>> Qmailtoaster is sponsored by Vickers Consulting
>>> Group
>>> (www.vickersconsulting.com
>>> <http://www.vickersconsulting.com>
>>> <http://www.vickersconsulting.com>
>>> <http://www.vickersconsulting.com>)
>>>
>>> Vickers Consulting Group offers Qmailtoaster
>>> support and
>>> installations.
>>> If you need professional help with your
>>> setup,
>>> contact them today!
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------------------
>>> Please visit qmailtoaster.com
>>> <http://qmailtoaster.com>
>>> <http://qmailtoaster.com> <http://qmailtoaster.com> for the
>>>
>>>
>>> latest news, updates, and packages.
>>>
>>> To unsubscribe, e-mail:
>>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>>
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>>>
>>>
>>> For additional commands, e-mail:
>>> qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>>
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------------------
>>> Qmailtoaster is sponsored by Vickers Consulting Group
>>> (www.vickersconsulting.com
>>> <http://www.vickersconsulting.com>
>>> <http://www.vickersconsulting.com>)
>>> Vickers Consulting Group offers Qmailtoaster support
>>> and
>>> installations.
>>> If you need professional help with your setup,
>>> contact them
>>> today!
>>>
>>>
>>>
>>> ---------------------------------------------------------------------------------
>>> Please visit qmailtoaster.com
>>> <http://qmailtoaster.com> <http://qmailtoaster.com> for
>>> the latest news, updates, and packages.
>>> To unsubscribe, e-mail:
>>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>>
>>> For additional commands, e-mail:
>>> qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> -Eric 'shubes'
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------------------
>>> Qmailtoaster is sponsored by Vickers Consulting Group
>>> (www.vickersconsulting.com <http://www.vickersconsulting.com>)
>>> Vickers Consulting Group offers Qmailtoaster support and
>>> installations.
>>> If you need professional help with your setup, contact them
>>> today!
>>>
>>>
>>> ---------------------------------------------------------------------------------
>>> Please visit qmailtoaster.com <http://qmailtoaster.com> for the
>>> latest news, updates, and packages.
>>> To unsubscribe, e-mail:
>>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
>>> For additional commands, e-mail:
>>> qmailtoaster-list-h...@qmailtoaster.com
>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com>
>>>
>>>
>>>
>>>
>>
>> --
>> -Eric 'shubes'
>>
>>
>>
>> ---------------------------------------------------------------------------------
>> Qmailtoaster is sponsored by Vickers Consulting Group (
>> www.vickersconsulting.com)
>> Vickers Consulting Group offers Qmailtoaster support and installations.
>> If you need professional help with your setup, contact them today!
>>
>> ---------------------------------------------------------------------------------
>> Please visit qmailtoaster.com for the latest news, updates, and
>> packages.
>> To unsubscribe, e-mail:
>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail:
>> qmailtoaster-list-h...@qmailtoaster.com
>>
>>
>>
>
