Re: sa-compile seems to not clean up after itself

2015-02-11 Thread listsb-spamassassin
i hope another solicitation for this help request is ok. > On Feb 04, 2015, at 09.19, btb wrote: > > hi- > > i happened to notice a bunch of old files in /tmp/, related to spamassassin. > after a bit of testing, it looks like sa-compile isn't cleaning up after > itself? > > >ls -alH /tmp/ >

Re: rule for restricting incoming email

2015-02-11 Thread David B Funk
If you look at the man page for spamassassin config, in the section that talks about the 'whitelist_to' statement, it lists the headers that SA examines when processing the addresses to white-list. That list of headers includes the "Delivered-To" header. So that -should- work, assuming your qmail

Re: rule for restricting incoming email

2015-02-11 Thread John Hardin
On Wed, 11 Feb 2015, David B Funk wrote: On Wed, 11 Feb 2015, Axb wrote: On 02/11/2015 07:09 PM, Benny Pedersen wrote: > On 11. feb. 2015 18.31.43 "Rajesh M" <24x7ser...@24x7server.net> wrote: > > > i am using qmailtoaster > > > > when the emails are sent to specified recepients via bcc

Re: rule for restricting incoming email

2015-02-11 Thread Axb
On 02/11/2015 07:35 PM, David B Funk wrote: On Wed, 11 Feb 2015, Axb wrote: On 02/11/2015 07:09 PM, Benny Pedersen wrote: On 11. feb. 2015 18.31.43 "Rajesh M" <24x7ser...@24x7server.net> wrote: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a

Re: rule for restricting incoming email

2015-02-11 Thread David B Funk
On Wed, 11 Feb 2015, Axb wrote: On 02/11/2015 07:09 PM, Benny Pedersen wrote: On 11. feb. 2015 18.31.43 "Rajesh M" <24x7ser...@24x7server.net> wrote: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to

Re: rule for restricting incoming email

2015-02-11 Thread John Hardin
On Wed, 11 Feb 2015, Benny Pedersen wrote: On 11. feb. 2015 18.31.43 "Rajesh M" <24x7ser...@24x7server.net> wrote: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to use to check however spamassass

Re: rule for restricting incoming email

2015-02-11 Thread Axb
On 02/11/2015 07:09 PM, Benny Pedersen wrote: On 11. feb. 2015 18.31.43 "Rajesh M" <24x7ser...@24x7server.net> wrote: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to use to check however spamassassi

Re: rule for restricting incoming email

2015-02-11 Thread Benny Pedersen
On 11. feb. 2015 18.31.43 "Rajesh M" <24x7ser...@24x7server.net> wrote: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to use to check however spamassassin does not seem to check Delivered-To header

Re: rule for restricting incoming email

2015-02-11 Thread John Hardin
On Wed, 11 Feb 2015, Rajesh M wrote: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to use to check however spamassassin does not seem to check Delivered-To header what could be the problem ? Wild g

Re: rule for restricting incoming email

2015-02-11 Thread Reindl Harald
Am 11.02.2015 um 18:30 schrieb Rajesh M: i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to use to check however spamassassin does not seem to check Delivered-To header what could be the problem ? tha

Re: rule for restricting incoming email

2015-02-11 Thread Rajesh M
hi i am using qmailtoaster when the emails are sent to specified recepients via bcc then there is a header Delivered-To created which i tried to use to check however spamassassin does not seem to check Delivered-To header what could be the problem ? rajesh - Original Message - From

Re: version stable

2015-02-11 Thread ricky gutierrez
2015-02-11 10:55 GMT-06:00 Kevin A. McGrail : > > Excellent. Perhaps you can open an upstream bug re: the version of Net::DNS > and the compatibility issue. > Ok my friend. regardss -- rickygm http://gnuforever.homelinux.com

Re: version stable

2015-02-11 Thread Kevin A. McGrail
On 2/11/2015 11:45 AM, ricky gutierrez wrote: solution is here: http://ximunix.blogspot.com/2013/10/howto-removeuninstall-perl-modules.html and later rpm -e --nodeps perl-Net-DNS rpm -ivh perl-Net-DNS-0.68-1.el6.rfx.x86_64.rpm sa-update and look uala!! spamassassin]# ls -l total 4 drwxr-

Re: version stable

2015-02-11 Thread ricky gutierrez
solution is here: http://ximunix.blogspot.com/2013/10/howto-removeuninstall-perl-modules.html and later rpm -e --nodeps perl-Net-DNS rpm -ivh perl-Net-DNS-0.68-1.el6.rfx.x86_64.rpm sa-update and look uala!! spamassassin]# ls -l total 4 drwxr-xr-x 3 root root 4096 Feb 11 10:41 3.003002 20

Re: version stable

2015-02-11 Thread ricky gutierrez
I'm looking to remove that library cpan :( 2015-02-11 9:40 GMT-06:00 Kevin A. McGrail : > On 2/11/2015 10:23 AM, ricky gutierrez wrote: >> >> 2015-02-11 9:12 GMT-06:00 Reindl Harald : >>> >>> >>> NO NOT DELETE THE ENTIRE DIRECTORY - READ WHAT I WROTE >> >> sorry, I understood you well, just delete

Re: version stable

2015-02-11 Thread Kevin A. McGrail
On 2/11/2015 10:23 AM, ricky gutierrez wrote: 2015-02-11 9:12 GMT-06:00 Reindl Harald : NO NOT DELETE THE ENTIRE DIRECTORY - READ WHAT I WROTE sorry, I understood you well, just delete it manually and run sa-update and did not create the directory automatically * under what user do you call

Re: version stable

2015-02-11 Thread ricky gutierrez
2015-02-11 9:12 GMT-06:00 Reindl Harald : > > > NO NOT DELETE THE ENTIRE DIRECTORY - READ WHAT I WROTE sorry, I understood you well, just delete it manually and run sa-update and did not create the directory automatically > > * under what user do you call "sa-update" in the threads above put I u

Re: version stable

2015-02-11 Thread Reindl Harald
Am 11.02.2015 um 16:08 schrieb ricky gutierrez: 2015-02-11 9:03 GMT-06:00 Reindl Harald : th versioned folders are *not* part of the install and hence are created by the very first run of "sa-update" (without any params) did you *really* delete the versioned folder and *not* "/var/lib/spamas

Re: version stable

2015-02-11 Thread Kevin A. McGrail
On 2/11/2015 10:08 AM, ricky gutierrez wrote: 2015-02-11 9:03 GMT-06:00 Reindl Harald : th versioned folders are *not* part of the install and hence are created by the very first run of "sa-update" (without any params) did you *really* delete the versioned folder and *not* "/var/lib/spamassas

Re: version stable

2015-02-11 Thread ricky gutierrez
2015-02-11 9:03 GMT-06:00 Reindl Harald : > > > > th versioned folders are *not* part of the install and hence are created by > the very first run of "sa-update" (without any params) > > did you *really* delete the versioned folder and *not* > "/var/lib/spamassassin" itself (which is part of the pa

Re: version stable

2015-02-11 Thread ricky gutierrez
2015-02-11 9:00 GMT-06:00 Kevin A. McGrail : > What user owns the /var/lib/spamassassin dir and what user are you running > sa-update as? ls -l rootroot4096 Feb 11 08:59 spamassassin I run as root -- rickygm http://gnuforever.homelinux.com

Re: version stable

2015-02-11 Thread Kevin A. McGrail
On 2/11/2015 9:56 AM, ricky gutierrez wrote: 2015-02-11 8:48 GMT-06:00 Kevin A. McGrail : On a default install, the sa-update rules are stored in /var/lib/spamassassin/ guys something happens because the directory is empty In there is a MIRRORED.BY file. I think it is corrupt. look: sa-upd

Re: version stable

2015-02-11 Thread Reindl Harald
Am 11.02.2015 um 15:56 schrieb ricky gutierrez: 2015-02-11 8:48 GMT-06:00 Kevin A. McGrail : On a default install, the sa-update rules are stored in /var/lib/spamassassin/ guys something happens because the directory is empty In there is a MIRRORED.BY file. I think it is corrupt. look:

Re: version stable

2015-02-11 Thread ricky gutierrez
2015-02-11 8:48 GMT-06:00 Kevin A. McGrail : > On a default install, the sa-update rules are stored in > /var/lib/spamassassin/ guys something happens because the directory is empty > > In there is a MIRRORED.BY file. > > I think it is corrupt. look: sa-update -D 2>&1 | grep MIRRORED Feb 11 08:

Re: Can't locate object method "check_for_spf_helo_permerror" via package "Mail: [...]:SpamAssassin::PerMsgStatus"

2015-02-11 Thread Jim Popovitch
On Tue, Feb 10, 2015 at 10:17 PM, Kevin A. McGrail wrote: > On 2/10/2015 9:13 AM, Kevin A. McGrail wrote: >> >> I would guess I missed the cutoff for yesterday's masscheck and tomorrow's >> will include it. > > Rule gen just finished and the update does include the fix if you want to > confirm. L

Re: version stable

2015-02-11 Thread Kevin A. McGrail
On 2/11/2015 9:44 AM, ricky gutierrez wrote: 2015-02-11 8:34 GMT-06:00 Kevin A. McGrail >: I seem to remember that can happen on older SA's that we fixed where the MIRRORED.BY file can be 0 bytes. Deleting it and running over fixes

Re: version stable

2015-02-11 Thread Reindl Harald
Am 11.02.2015 um 15:44 schrieb ricky gutierrez: 2015-02-11 8:34 GMT-06:00 Kevin A. McGrail: I seem to remember that can happen on older SA's that we fixed where the MIRRORED.BY file can be 0 bytes. Deleting it and running over fixes the issue. Please let me know if that he

Re: version stable

2015-02-11 Thread ricky gutierrez
2015-02-11 8:34 GMT-06:00 Kevin A. McGrail : > > > I seem to remember that can happen on older SA's that we fixed where the > MIRRORED.BY file can be 0 bytes. Deleting it and running over fixes the > issue. Please let me know if that helps point you in a good direction. > > Regards, > KAM > > so

Re: version stable

2015-02-11 Thread Kevin A. McGrail
On 2/11/2015 9:23 AM, ricky gutierrez wrote: Hi Kevin , look the ouput Feb 11 08:19:09.504 [6221] dbg: http: GET 3.3 request failed, retrying: 400 URL must be absolute: 400 URL must be absolute http: GET 3.3 request failed: 400 URL must be absolute: 400 URL must be absolute Feb 11 08:19:09.504 [

Re: rule for restricting incoming email

2015-02-11 Thread Matus UHLAR - fantomas
On Tue, 10 Feb 2015, Rajesh M wrote: i have an email id : u...@abc.com now i need to set a rule such that u...@abc.com can receive emails only from specific external domains and rest all should be rejected as spam On 11.02.15 10:47, Lucio Chiappetti wrote: To me this seems a task for procm

Re: rule for restricting incoming email

2015-02-11 Thread Lucio Chiappetti
On Tue, 10 Feb 2015, Rajesh M wrote: i have an email id : u...@abc.com now i need to set a rule such that u...@abc.com can receive emails only from specific external domains and rest all should be rejected as spam To me this seems a task for procmail. The USER can make a list of domains or a