Re: Allow User Rules problem

[Matus UHLAR - fantomas]

On 17.02.16 11:08, Amanda Giarla wrote:

Please note that I am working on Training Server not a working server.
My mission is to learn how all of the packages work together.
There are many - spamassassin, exim, dovecot, clamav, roundcube to name a
few
It was suggested that I set up a spamassassin user_prefs file.
AND so I have been taking steps to do just that.
The feedback seems to express it is not possible.

As I write this I have to confess I do not know the difference between a
"unix user" and a "virtual user".
Will have to look into that notion.

In the VestaCP control panel I can create a user (which ends up as
/home/clientName) with a valid FQD name.  I can send email to the user. The
user can pull up the RoundCube email client and see and read the emails.  I
can send the GTUBE spam
message and the message gets marked as SPAM and dropped in the junk email
box. I was trying to set up a blacklist so
that the user could enter email-addresses to stop receiving email form.



Since your users, and mail server seem to be maintained by VestaCP, you
should search for support in VestaCP documentation/lists/forums.

SpamAssassin supports virtual users, but it must be configured to use them.
I have never heard of this software, and I don't know if it suppports
multiuser setup at all.

I for example use spamass-milter that does, and on some servers amavis and
MailScanner that do not...

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I intend to live forever - so far so good. 

Re: Allow User Rules problem

[Amanda Giarla]

Bowie that was an excellent and definitive explanation of unix user and
virtual user.   My google searches did not come close to presenting that
information.  I can set up a few more more domains and associated "virtual"
users along with multiples of users associated with any one domain.  Also I
think I should go back and read some docs again with "virtual user" in
mind.

On Wed, Feb 17, 2016 at 12:30 PM, Bowie Bailey  wrote:

> On 2/17/2016 2:08 PM, Amanda Giarla wrote:
>
>> Please note that I am working on Training Server not a working server.
>> My mission is to learn how all of the packages work together.
>> There are many - spamassassin, exim, dovecot, clamav, roundcube to name a
>> few
>> It was suggested that I set up a spamassassin user_prefs file.
>> AND so I have been taking steps to do just that.
>> The feedback seems to express it is not possible.
>>
>> As I write this I have to confess I do not know the difference between a
>> "unix user" and a "virtual user".
>> Will have to look into that notion.
>>
>
> A "unix user" is one that is defined in the /etc/passwd file and has a
> unique UID.  A "virtual user" has their own mail directory and frequently
> has their own home directory, but all of the files for all of the virtual
> users are owned by a single unix user.
>
> In the VestaCP control panel I can create a user (which ends up as
>> /home/clientName) with a valid FQD name.  I can send email to the user. The
>> user can pull up the RoundCube email client and see and read the emails.  I
>> can send the GTUBE spam
>> message and the message gets marked as SPAM and dropped in the junk email
>> box. I was trying to set up a blacklist so
>> that the user could enter email-addresses to stop receiving email form.
>>
>
> In that case, create a couple of different users and send them emails.
> Take a look at where in the filesystem those emails are delivered and who
> owns the files.  That will give you a clue how the system is configured.
>
> --
> Bowie
>

Re: Allow User Rules problem

[Bowie Bailey]

On 2/17/2016 2:08 PM, Amanda Giarla wrote:

Please note that I am working on Training Server not a working server.
My mission is to learn how all of the packages work together.
There are many - spamassassin, exim, dovecot, clamav, roundcube to 
name a few

It was suggested that I set up a spamassassin user_prefs file.
AND so I have been taking steps to do just that.
The feedback seems to express it is not possible.

As I write this I have to confess I do not know the difference between 
a "unix user" and a "virtual user".

Will have to look into that notion.


A "unix user" is one that is defined in the /etc/passwd file and has a 
unique UID.  A "virtual user" has their own mail directory and 
frequently has their own home directory, but all of the files for all of 
the virtual users are owned by a single unix user.


In the VestaCP control panel I can create a user (which ends up as 
/home/clientName) with a valid FQD name.  I can send email to the 
user. The user can pull up the RoundCube email client and see and read 
the emails.  I can send the GTUBE spam
message and the message gets marked as SPAM and dropped in the junk 
email box. I was trying to set up a blacklist so

that the user could enter email-addresses to stop receiving email form.


In that case, create a couple of different users and send them emails.  
Take a look at where in the filesystem those emails are delivered and 
who owns the files.  That will give you a clue how the system is configured.


--
Bowie

Re: Allow User Rules problem

[Amanda Giarla]

Please note that I am working on Training Server not a working server.
My mission is to learn how all of the packages work together.
There are many - spamassassin, exim, dovecot, clamav, roundcube to name a
few
It was suggested that I set up a spamassassin user_prefs file.
AND so I have been taking steps to do just that.
The feedback seems to express it is not possible.

As I write this I have to confess I do not know the difference between a
"unix user" and a "virtual user".
Will have to look into that notion.

In the VestaCP control panel I can create a user (which ends up as
/home/clientName) with a valid FQD name.  I can send email to the user. The
user can pull up the RoundCube email client and see and read the emails.  I
can send the GTUBE spam
message and the message gets marked as SPAM and dropped in the junk email
box. I was trying to set up a blacklist so
that the user could enter email-addresses to stop receiving email form.



On Wed, Feb 17, 2016 at 5:55 AM, RW  wrote:

> On Tue, 16 Feb 2016 15:47:33 -0800
> Amanda Giarla wrote:
>
>
> >
> > On Tue, Feb 16, 2016 at 3:39 PM, RW 
> > wrote:
> >
> > > On Tue, 16 Feb 2016 14:17:02 -0800
> > > Amanda Giarla wrote:
> > >
> > >
> > > > I looked at the permission of the user_prefs file and for
> > > > ownership and group-ownership it is root root.  should it be
> > > > debian-spamd debian-spamd? I did change one of the conf files
> > > > from nobody to debian-spamd for ownership.
> > >
> > > Having a global user_prefs is pretty much pointless. The point of
> > > the file is that there is one per email account - either
> > > ~/.spamassassin/user_prefs for unix mail accounts or a custom
> > > location for virtual accounts.
> >
> > I don't think I was trying to make a global user_prefs file BUT in my
> > confusion I may accidentally have implied such.
> > The user_prefs file is located at
> > /home/clientAccount/.spamassassin/user_prefs.   Is that considered
> > global?
>
>
> If /home/clientAccount/ is a unix account home directory I'm wondering
> why user_prefs was owned by root, and what created it.
>
> I had a very quick look at the VestaCP installer, and everything seems
> to be configured with virtual users, so I doubt the spamassassin glue
> supports per unix user configuration. The spamd start-up configuration
> is the Ubuntu default, so unless it's a custom package it wont support
> user_prefs files for virtual users.
>
> I'd be surprised if this installation supports per user configuration
> beyond turning filtering off and on. It probably would then be able to
> find a user_prefs file in a specific home directory, but that would just
> represent an unnecessary location for global configuration.
>

Re: Allow User Rules problem

[RW]

On Tue, 16 Feb 2016 15:47:33 -0800
Amanda Giarla wrote:


> 
> On Tue, Feb 16, 2016 at 3:39 PM, RW 
> wrote:
> 
> > On Tue, 16 Feb 2016 14:17:02 -0800
> > Amanda Giarla wrote:
> >
> >  
> > > I looked at the permission of the user_prefs file and for
> > > ownership and group-ownership it is root root.  should it be
> > > debian-spamd debian-spamd? I did change one of the conf files
> > > from nobody to debian-spamd for ownership.  
> >
> > Having a global user_prefs is pretty much pointless. The point of
> > the file is that there is one per email account - either
> > ~/.spamassassin/user_prefs for unix mail accounts or a custom
> > location for virtual accounts.
>   
> I don't think I was trying to make a global user_prefs file BUT in my
> confusion I may accidentally have implied such.
> The user_prefs file is located at
> /home/clientAccount/.spamassassin/user_prefs.   Is that considered
> global?


If /home/clientAccount/ is a unix account home directory I'm wondering
why user_prefs was owned by root, and what created it.

I had a very quick look at the VestaCP installer, and everything seems
to be configured with virtual users, so I doubt the spamassassin glue
supports per unix user configuration. The spamd start-up configuration
is the Ubuntu default, so unless it's a custom package it wont support
user_prefs files for virtual users. 

I'd be surprised if this installation supports per user configuration
beyond turning filtering off and on. It probably would then be able to
find a user_prefs file in a specific home directory, but that would just
represent an unnecessary location for global configuration.

Re: Allow User Rules problem

[Matus UHLAR - fantomas]

On 16.02.16 15:36, Amanda Giarla wrote:

THEN I took the rule:*"blacklist_from *@gmail.com "* out
and placed in the rule: *"allow_user_rules 1"*


I feel you have missed this: "blacklist_from" is not a rule, it's
configuration directive.
You do NOT need "allow_user_rules 1" to use "blacklist_from" and you should
not allow user rules by "allow_user_rules 1"
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Atheism is a non-prophet organization. 

Re: Allow User Rules problem

[Bowie Bailey]

You should put all of your changes in /etc/spamassassin/local.cf. All of 
the files under /var/lib/spamassassin are subject to being replaced when 
you update the rules.  You probably have either a freshclam process 
running that does periodic updates, or there may be a cron job that 
calls it on a regular basis.


Of course, there is also a chance that VestaCP is doing it a different 
way, but since the files seem to be in the normal places, I would 
suspect that VestaCP is using a standard install of SpamAssassin.


Bowie

On 2/16/2016 8:27 PM, Amanda Giarla wrote:
Nope - Sorry forgot to mention /etc/spamassassin/local.cf 



In the debugging out put the following line appeared first
Feb 16 20:16:25.968 [17171] dbg: config: read file 
/etc/spamassassin/local.cf 


followed by
Feb 16 20:16:26.745 [17171] dbg: config: fixed relative path: 
/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf 

Feb 16 20:16:26.746 [17171] dbg: config: using 
"/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf 
" for included file
Feb 16 20:16:26.746 [17171] dbg: config: read file 
/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf 



Which caught my attention.

Opps! Forgot to cc the users - sorry for the duplicate

On Tue, Feb 16, 2016 at 5:06 PM, John Hardin > wrote:


On Tue, 16 Feb 2016, Amanda Giarla wrote:

I would like to confirm your suggestion regarding the cmd $
spamassassin -D
--lint 2>&1 | grep local.cf 
It did work ( after I realized there was a space in the line)
and presented
an interesting set of lines that lead me to the site wide
config file that
was actually read.

I went to directory
*/var/lib/spamassassin/3.004000/updates_spamassassin_org* and
edited


While I'm not familiar with what VestaCP may have done to modify
the standard SA config, the
/var/lib/spamassassin/3.004000/updates_spamassassin_org folder is
where rule updates downloaded from the SA live rules maintenance
process are stored. Any changes you make there will *probably* be
lost on the next rules update.

Is that the *only* local.cf  file that the debug
output mentioned?

I'd much more expect the "real" local config file to be under
/etc/ somewhere.

-- 
 John Hardin KA7OHZ http://www.impsec.org/~jhardin/


jhar...@impsec.org    FALaholic #11174 
   pgpk -a jhar...@impsec.org 

 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Gun Control is marketed to the public using the appealing delusion
  that violent criminals will obey the law.
---
 6 days until George Washington's 284th Birthday

Re: Allow User Rules problem

[John Hardin]

On Tue, 16 Feb 2016, Amanda Giarla wrote:


Nope - Sorry forgot to mention /etc/spamassassin/local.cf


OK, good.

Just for completeness, please try your basic blacklist test on *that* 
config file.






In the debugging out put the following line appeared first
Feb 16 20:16:25.968 [17171] dbg: config: read file /etc/spamassassin/
local.cf

followed by
Feb 16 20:16:26.745 [17171] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf
Feb 16 20:16:26.746 [17171] dbg: config: using
"/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf" for
included file
Feb 16 20:16:26.746 [17171] dbg: config: read file
/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf

Which caught my attention.

Opps! Forgot to cc the users - sorry for the duplicate

On Tue, Feb 16, 2016 at 5:06 PM, John Hardin  wrote:


On Tue, 16 Feb 2016, Amanda Giarla wrote:

I would like to confirm your suggestion regarding the cmd $ spamassassin -D

--lint 2>&1 | grep local.cf
It did work ( after I realized there was a space in the line) and
presented
an interesting set of lines that lead me to the site wide config file that
was actually read.

I went to directory
*/var/lib/spamassassin/3.004000/updates_spamassassin_org* and edited



While I'm not familiar with what VestaCP may have done to modify the
standard SA config, the
/var/lib/spamassassin/3.004000/updates_spamassassin_org folder is where
rule updates downloaded from the SA live rules maintenance process are
stored. Any changes you make there will *probably* be lost on the next
rules update.

Is that the *only* local.cf file that the debug output mentioned?

I'd much more expect the "real" local config file to be under /etc/
somewhere.


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Justice is justice, whereas "social justice" is code for one set
  of rules for the rich, another for the poor; one set for whites,
  another set for minorities; one set for straight men, another for
  women and gays. In short, it's the opposite of actual justice.
-- Burt Prelutsky
---
 6 days until George Washington's 284th Birthday

Re: Allow User Rules problem

[Amanda Giarla]

Nope - Sorry forgot to mention /etc/spamassassin/local.cf

In the debugging out put the following line appeared first
Feb 16 20:16:25.968 [17171] dbg: config: read file /etc/spamassassin/
local.cf

followed by
Feb 16 20:16:26.745 [17171] dbg: config: fixed relative path:
/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf
Feb 16 20:16:26.746 [17171] dbg: config: using
"/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf" for
included file
Feb 16 20:16:26.746 [17171] dbg: config: read file
/var/lib/spamassassin/3.004000/updates_spamassassin_org/local.cf

Which caught my attention.

Opps! Forgot to cc the users - sorry for the duplicate

On Tue, Feb 16, 2016 at 5:06 PM, John Hardin  wrote:

> On Tue, 16 Feb 2016, Amanda Giarla wrote:
>
> I would like to confirm your suggestion regarding the cmd $ spamassassin -D
>> --lint 2>&1 | grep local.cf
>> It did work ( after I realized there was a space in the line) and
>> presented
>> an interesting set of lines that lead me to the site wide config file that
>> was actually read.
>>
>> I went to directory
>> */var/lib/spamassassin/3.004000/updates_spamassassin_org* and edited
>>
>
> While I'm not familiar with what VestaCP may have done to modify the
> standard SA config, the
> /var/lib/spamassassin/3.004000/updates_spamassassin_org folder is where
> rule updates downloaded from the SA live rules maintenance process are
> stored. Any changes you make there will *probably* be lost on the next
> rules update.
>
> Is that the *only* local.cf file that the debug output mentioned?
>
> I'd much more expect the "real" local config file to be under /etc/
> somewhere.
>
> --
>  John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
>  jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
>  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
> ---
>   Gun Control is marketed to the public using the appealing delusion
>   that violent criminals will obey the law.
> ---
>  6 days until George Washington's 284th Birthday
>

Re: Allow User Rules problem

[John Hardin]

On Tue, 16 Feb 2016, Amanda Giarla wrote:


I would like to confirm your suggestion regarding the cmd $ spamassassin -D
--lint 2>&1 | grep local.cf
It did work ( after I realized there was a space in the line) and presented
an interesting set of lines that lead me to the site wide config file that
was actually read.

I went to directory
*/var/lib/spamassassin/3.004000/updates_spamassassin_org* and edited


While I'm not familiar with what VestaCP may have done to modify the 
standard SA config, the 
/var/lib/spamassassin/3.004000/updates_spamassassin_org folder is where 
rule updates downloaded from the SA live rules maintenance process are 
stored. Any changes you make there will *probably* be lost on the next 
rules update.


Is that the *only* local.cf file that the debug output mentioned?

I'd much more expect the "real" local config file to be under /etc/ 
somewhere.


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Gun Control is marketed to the public using the appealing delusion
  that violent criminals will obey the law.
---
 6 days until George Washington's 284th Birthday

Re: Allow User Rules problem

[Reindl Harald]

Am 17.02.2016 um 00:47 schrieb Amanda Giarla:

I don't think I was trying to make a global user_prefs file BUT in my
confusion I may accidentally have implied such.
The user_prefs file is located at
/home/clientAccount/.spamassassin/user_prefs.   Is that considered global?


no, but then there is no point that it is owned by root or debian-spamd

we still don't know how SA is called in your setup

example:
in case of spamass-milter there would be only one user (the milter user) 
which means pretty much the same as a site-wide setup



On Tue, Feb 16, 2016 at 3:39 PM, RW > wrote:

On Tue, 16 Feb 2016 14:17:02 -0800
Amanda Giarla wrote:


> I looked at the permission of the user_prefs file and for ownership
> and group-ownership it is root root.  should it be debian-spamd
> debian-spamd? I did change one of the conf files from nobody to
> debian-spamd for ownership.

Having a global user_prefs is pretty much pointless. The point of the
file is that there is one per email account - either
~/.spamassassin/user_prefs for unix mail accounts or a custom location
for virtual accounts




signature.asc
Description: OpenPGP digital signature

Re: Allow User Rules problem

[Amanda Giarla]

I don't think I was trying to make a global user_prefs file BUT in my
confusion I may accidentally have implied such.
The user_prefs file is located at
/home/clientAccount/.spamassassin/user_prefs.   Is that considered global?


On Tue, Feb 16, 2016 at 3:39 PM, RW  wrote:

> On Tue, 16 Feb 2016 14:17:02 -0800
> Amanda Giarla wrote:
>
>
> > I looked at the permission of the user_prefs file and for ownership
> > and group-ownership it is root root.  should it be debian-spamd
> > debian-spamd? I did change one of the conf files from nobody to
> > debian-spamd for ownership.
>
> Having a global user_prefs is pretty much pointless. The point of the
> file is that there is one per email account - either
> ~/.spamassassin/user_prefs for unix mail accounts or a custom location
> for virtual accounts.
>
>
>

Re: Allow User Rules problem

[RW]

On Tue, 16 Feb 2016 14:17:02 -0800
Amanda Giarla wrote:


> I looked at the permission of the user_prefs file and for ownership
> and group-ownership it is root root.  should it be debian-spamd
> debian-spamd? I did change one of the conf files from nobody to
> debian-spamd for ownership.

Having a global user_prefs is pretty much pointless. The point of the
file is that there is one per email account - either
~/.spamassassin/user_prefs for unix mail accounts or a custom location
for virtual accounts. 

Re: Allow User Rules problem

[Amanda Giarla]

I would like to confirm your suggestion regarding the cmd $ spamassassin -D
--lint 2>&1 | grep local.cf
It did work ( after I realized there was a space in the line) and presented
an interesting set of lines that lead me to the site wide config file that
was actually read.

I went to directory
*/var/lib/spamassassin/3.004000/updates_spamassassin_org* and edited
file *"local.cf
"*
I placed the following rule: * "blacklist_from *@gmail.com
"  *
AND my test emails were marked USER_IN_BLACKLIST and placed in the junk
box. - major cool.

THEN I took the rule:*"blacklist_from *@gmail.com "* out
and placed in the rule: *"allow_user_rules 1"*

THEN went to directory /home/client/.spamassassin  where the user_prefs
file is located.
I placed in the rule: *"blacklist_from *@gmail.com "*

AND changed owner from root to debian-spamd
-rw-r--r-- 1 debian-spamd debian-spamd 2190 Feb 16 13:47 user_prefs

BUT the test email from my gmail account did not get Marked as SPAM

Not sure where to look next.  Am I missing a Rule? Is the ownership wrong?

Amanda







On Tue, Feb 16, 2016 at 12:34 PM, Bowie Bailey  wrote:

> On 2/16/2016 2:44 PM, Amanda Giarla wrote:
>
> First this is on a training server running Ubuntu 14, VestaCP, Exim4 etc.
>
> In doc
> https://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html
> Under RULE DEFINITIONS AND PRIVILEGED SETTINGS
> It it my understanding that to use the a user_prefs file I have to place
> in some config file
>
> *allow_user_rules 1*
>
> first.
>
> And then write rules into the user_prefs file.
>
> WHAT I DID
>
> I have placed the allow_user_rules rule in
> */usr/share/spamassassin/local.cf *
> AND
>
> */etc/mail/spamassassin/local.cf  *
>
>
> That should work, although it is only needed in one of the two places.
> You need to determine which file SA is reading.
>
> Take a look at the output of:
> $ spamassassin -D --lint 2>&1 | grep local.cf
>
>
> THEN placed in the user_prefs file the following rule
>
> *blacklist_from *@gmail.com *
> and restarted spamassassin
>
>
> That is fine, however I don't think you need the allow_user_rules option
> for that.  It is only needed for the options listed under the RULE
> DEFINITIONS AND PRIVILEGED SETTINGS section of the man page.
>
>
> Thinking this will mark mail from my gmail account as SPAM.
>
> When I look in the logs I do not see the test emails marked as spam
> AND when I go into the webmail client the email was placed in the inbox
> not in the junk box.
>
> I have tested with GTUBE spam and that does get marked and placed in the
> junk box.
>
> Is the above the correct sequence?  Am I missing a step?
>
>
> My first guess would be that the user_prefs file is either in the wrong
> place or has incorrect permissions.  A close second would be that SA always
> runs as the same user and you are not passing the -u option to spamc (along
> with any necessary options for spamd depending on your setup).
>
> --
> Bowie
>

Re: Allow User Rules problem

[Reindl Harald]

Am 16.02.2016 um 23:22 schrieb Amanda Giarla:

Why should anybody know? Well - I'm just learning that the configuration
that I am running is very different than yours.  How would I know that
you have no knowledge of spamassassin as installed under VestaCP?


the main problem is that you did not install and configure spamassassin, 
you installed something which is wrapping and configuring SA in whatever 
way and so you can't even answer basic questions


i guess VestaCP has a support channel


On Tue, Feb 16, 2016 at 2:06 PM, Reindl Harald > wrote:

keep on list!

since VestaCP is something wrapping all sort of tools just ask there
- you don't have a normal SA setup and don't know anything about
your real configuration setup - how should anybody else know?

Am 16.02.2016 um 23:02 schrieb Amanda Giarla:

Hey Reindl

This is my first time dealing with Spam and Spamassassin

You ask how is my SA configured?   Not sure.  It was installed
as part
of the VestaCP installation. There are various locations of
configuration files like
/usr/share/spamassassin/local.cf 
.  I've been reading
various docs about spamassassin and writing rules.  There is the
notion
that a user may have a user_prefs file with rules that can
override the
sitewide rules.  Just trying to get that going.

ghow is it called?  I'm not sure what you are referring to. ghow
isn't
on my Ubuntu as a linux cmd AND when I google it I get odd
respopnses.

what is the glue (spamass-milter, amavis, scripts..)?  Well - as
I said
above its part of the VestaCP installation with other packages like
Exim4, DoveCot, ClamAV to handle Email, Spam and Anti-Virus




signature.asc
Description: OpenPGP digital signature

Re: Allow User Rules problem

[Amanda Giarla]

Thanks


On Tue, Feb 16, 2016 at 2:21 PM, Reindl Harald 
wrote:

>
>
> Am 16.02.2016 um 23:17 schrieb Amanda Giarla:
>
>> Hey Bowie
>>
>> spamassassin is working - I've sent the GTUBE email through the system
>> from my gmail account and it was marked and delivered into junk box.
>>
>> Was not sure which of the site wide local.cf  files I
>> should put the all_user_rules flag in so I put it in both.
>>
>> I did run your suggested cmd $ spamassassin -D --lint 2>&1 | grep
>> local.cf
>> AND GOT a lot of output with I think I should not have since the
>> inclusion of the grep pattern filter
>>
>
> the problem here is that "spamassassin -D" spits out everyting on sterror,
> so grep is useless
>
> "spamassassin -D --lint 2>> out.txt >> out.txt" would put all outputs into
> "out.txt" and you can grep from there
>
> "In this context is I'm not sure what &1 means"
>
> here you go: http://www.tldp.org/LDP/abs/html/io-redirection.html
>
>
>
>

Re: Allow User Rules problem

[Amanda Giarla]

Why should anybody know? Well - I'm just learning that the configuration
that I am running is very different than yours.  How would I know that you
have no knowledge of spamassassin as installed under VestaCP?

On Tue, Feb 16, 2016 at 2:06 PM, Reindl Harald 
wrote:

> keep on list!
>
> since VestaCP is something wrapping all sort of tools just ask there - you
> don't have a normal SA setup and don't know anything about your real
> configuration setup - how should anybody else know?
>
> Am 16.02.2016 um 23:02 schrieb Amanda Giarla:
>
>> Hey Reindl
>>
>> This is my first time dealing with Spam and Spamassassin
>>
>> You ask how is my SA configured?   Not sure.  It was installed as part
>> of the VestaCP installation. There are various locations of
>> configuration files like
>> /usr/share/spamassassin/local.cf .  I've been reading
>> various docs about spamassassin and writing rules.  There is the notion
>> that a user may have a user_prefs file with rules that can override the
>> sitewide rules.  Just trying to get that going.
>>
>> ghow is it called?  I'm not sure what you are referring to. ghow isn't
>> on my Ubuntu as a linux cmd AND when I google it I get odd respopnses.
>>
>> what is the glue (spamass-milter, amavis, scripts..)?  Well - as I said
>> above its part of the VestaCP installation with other packages like
>> Exim4, DoveCot, ClamAV to handle Email, Spam and Anti-Virus.
>>
>
>
>
>

Re: Allow User Rules problem

[Reindl Harald]

Am 16.02.2016 um 23:17 schrieb Amanda Giarla:

Hey Bowie

spamassassin is working - I've sent the GTUBE email through the system
from my gmail account and it was marked and delivered into junk box.

Was not sure which of the site wide local.cf  files I
should put the all_user_rules flag in so I put it in both.

I did run your suggested cmd $ spamassassin -D --lint 2>&1 | grep
local.cf
AND GOT a lot of output with I think I should not have since the
inclusion of the grep pattern filter


the problem here is that "spamassassin -D" spits out everyting on 
sterror, so grep is useless


"spamassassin -D --lint 2>> out.txt >> out.txt" would put all outputs 
into "out.txt" and you can grep from there


"In this context is I'm not sure what &1 means"

here you go: http://www.tldp.org/LDP/abs/html/io-redirection.html





signature.asc
Description: OpenPGP digital signature

Re: Allow User Rules problem

[Amanda Giarla]

Hey Bowie

spamassassin is working - I've sent the GTUBE email through the system from
my gmail account and it was marked and delivered into junk box.

Was not sure which of the site wide local.cf files I should put the
all_user_rules flag in so I put it in both.

I did run your suggested cmd $ spamassassin -D --lint 2>&1 | grep local.cf
AND GOT a lot of output with I think I should not have since the inclusion
of the grep pattern filter.
I'm not sure that cmd is what you want.
I read the command as Run spamassassin WITH OPTIONS -D and --lint 2  SEND
output to NOT SURE HERE.  In this context is I'm not sure what &1 means.
BUT the output should be sent a pipe to grep and filter on the patter
local.cf.   Perhaps my interpretation is wrong.   Anyway it didn't appear
to tell me anything about the source of the config file.  It did list all
the rules that are enabled.  That's cool.

I looked at the permission of the user_prefs file and for ownership and
group-ownership it is root root.  should it be debian-spamd debian-spamd?
I did change one of the conf files from nobody to debian-spamd for
ownership.

Amanda



On Tue, Feb 16, 2016 at 12:34 PM, Bowie Bailey  wrote:

> On 2/16/2016 2:44 PM, Amanda Giarla wrote:
>
> First this is on a training server running Ubuntu 14, VestaCP, Exim4 etc.
>
> In doc
> https://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html
> Under RULE DEFINITIONS AND PRIVILEGED SETTINGS
> It it my understanding that to use the a user_prefs file I have to place
> in some config file
>
> *allow_user_rules 1*
>
> first.
>
> And then write rules into the user_prefs file.
>
> WHAT I DID
>
> I have placed the allow_user_rules rule in
> */usr/share/spamassassin/local.cf *
> AND
>
> */etc/mail/spamassassin/local.cf  *
>
>
> That should work, although it is only needed in one of the two places.
> You need to determine which file SA is reading.
>
> Take a look at the output of:
> $ spamassassin -D --lint 2>&1 | grep local.cf
>
>
> THEN placed in the user_prefs file the following rule
>
> *blacklist_from *@gmail.com *
> and restarted spamassassin
>
>
> That is fine, however I don't think you need the allow_user_rules option
> for that.  It is only needed for the options listed under the RULE
> DEFINITIONS AND PRIVILEGED SETTINGS section of the man page.
>
>
> Thinking this will mark mail from my gmail account as SPAM.
>
> When I look in the logs I do not see the test emails marked as spam
> AND when I go into the webmail client the email was placed in the inbox
> not in the junk box.
>
> I have tested with GTUBE spam and that does get marked and placed in the
> junk box.
>
> Is the above the correct sequence?  Am I missing a step?
>
>
> My first guess would be that the user_prefs file is either in the wrong
> place or has incorrect permissions.  A close second would be that SA always
> runs as the same user and you are not passing the -u option to spamc (along
> with any necessary options for spamd depending on your setup).
>
> --
> Bowie
>

Re: Allow User Rules problem

[Reindl Harald]

keep on list!

since VestaCP is something wrapping all sort of tools just ask there - 
you don't have a normal SA setup and don't know anything about your real 
configuration setup - how should anybody else know?


Am 16.02.2016 um 23:02 schrieb Amanda Giarla:

Hey Reindl

This is my first time dealing with Spam and Spamassassin

You ask how is my SA configured?   Not sure.  It was installed as part
of the VestaCP installation. There are various locations of
configuration files like
/usr/share/spamassassin/local.cf .  I've been reading
various docs about spamassassin and writing rules.  There is the notion
that a user may have a user_prefs file with rules that can override the
sitewide rules.  Just trying to get that going.

ghow is it called?  I'm not sure what you are referring to. ghow isn't
on my Ubuntu as a linux cmd AND when I google it I get odd respopnses.

what is the glue (spamass-milter, amavis, scripts..)?  Well - as I said
above its part of the VestaCP installation with other packages like
Exim4, DoveCot, ClamAV to handle Email, Spam and Anti-Virus.






signature.asc
Description: OpenPGP digital signature

Re: Allow User Rules problem

[Bowie Bailey]

On 2/16/2016 2:44 PM, Amanda Giarla wrote:

First this is on a training server running Ubuntu 14, VestaCP, Exim4 etc.

In doc
https://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html
Under RULE DEFINITIONS AND PRIVILEGED SETTINGS
It it my understanding that to use the a user_prefs file I have to 
place in some config file


*allow_user_rules 1*

first.

And then write rules into the user_prefs file.

WHAT I DID

I have placed the allow_user_rules rule in
*/usr/share/spamassassin/local.cf *
AND
*/etc/mail/spamassassin/local.cf 
*


That should work, although it is only needed in one of the two places.  
You need to determine which file SA is reading.


Take a look at the output of:
$ spamassassin -D --lint 2>&1 | grep local.cf



THEN placed in the user_prefs file the following rule

*blacklist_from *@gmail.com *
and restarted spamassassin


That is fine, however I don't think you need the allow_user_rules option 
for that.  It is only needed for the options listed under the RULE 
DEFINITIONS AND PRIVILEGED SETTINGS section of the man page.




Thinking this will mark mail from my gmail account as SPAM.

When I look in the logs I do not see the test emails marked as spam
AND when I go into the webmail client the email was placed in the 
inbox not in the junk box.


I have tested with GTUBE spam and that does get marked and placed in 
the junk box.


Is the above the correct sequence?  Am I missing a step?


My first guess would be that the user_prefs file is either in the wrong 
place or has incorrect permissions.  A close second would be that SA 
always runs as the same user and you are not passing the -u option to 
spamc (along with any necessary options for spamd depending on your setup).


--
Bowie

Re: Allow User Rules problem

[Reindl Harald]

Am 16.02.2016 um 20:44 schrieb Amanda Giarla:

THEN placed in the user_prefs file the following rule

*blacklist_from *@gmail.com *
and restarted spamassassin

Thinking this will mark mail from my gmail account as SPAM.

When I look in the logs I do not see the test emails marked as spam
AND when I go into the webmail client the email was placed in the inbox
not in the junk box.

I have tested with GTUBE spam and that does get marked and placed in the
junk box.

Is the above the correct sequence?  Am I missing a step?


how is your SA configured?
ghow is it called?
what is the glue (spamass-milter, amavis, scripts..)?



signature.asc
Description: OpenPGP digital signature