Skip to main content

How to import a user level filtering list to a cpanel account ?

Comments

11 comments

  • cPanelMichael
    Hello :) You can manually edit the following files: /home/$user/etc/filter /home/$user/etc/filter.yaml
    It's acceptable to use the same list for multiple accounts, and the skeleton directory can include filter files. EX: /root/cpanel3-skel/etc/filter /root/cpanel3-skel/etc/filter.yaml
    Thank you.
    0
  • menkom
    [quote="cPanelMichael, post: 1467281">Hello :) You can manually edit the following files: /home/$user/etc/filter /home/$user/etc/filter.yaml
    It's acceptable to use the same list for multiple accounts, and the skeleton directory can include filter files. EX: /root/cpanel3-skel/etc/filter /root/cpanel3-skel/etc/filter.yaml
    Thank you.
    Thank you so much for this, is the filter you mention above USER LEVEL FILTERING or ACCOUNT LEVEL FILTERING or do they inherit the same ? Thank you so much for your answer
    0
  • cPanelMichael
    My previous post is intended for the "User Level Filtering" option in cPanel. The "Account Level Filtering" values are stored per domain name in: /etc/vfilters/
    Thank you.
    0
  • menkom
    [quote="cPanelMichael, post: 1468341">My previous post is intended for the "User Level Filtering" option in cPanel. The "Account Level Filtering" values are stored per domain name in: /etc/vfilters/
    Thank you.
    Ok my setup is a little different i am on sharedhost so i am not sure if this still applies to me ? My directly for USER LEVEL FILTERING IS /etc/domain.com/username/filter.yaml not exactly as you specified. I do not have a directory under root /etc directory called /vfilters ? Please advise, sorry for all the question. Thank you so much.
    0
  • menkom
    I tried manually creating /etc/vfilters and putting the yaml file but there is no difference i cannot see the rule in cpanel I also tried putting the yaml file into /etc and no difference as well for both USER LEVEL FILTERING and ACCOUNT LEVEL FILTERING, do you think its because im in a shared environment ?
    0
  • cPanelMichael
    The /etc/vfilters directory is only accessible with "root" access. You will not be able to modify the files in this directory with a shared hosting account. As for the user level filtering, it's fine to use the additional domain name in the directory path. That's typically for parked or addon domain names. Thank you.
    0
  • menkom
    [quote="cPanelMichael, post: 1469162">The /etc/vfilters directory is only accessible with "root" access. You will not be able to modify the files in this directory with a shared hosting account. As for the user level filtering, it's fine to use the additional domain name in the directory path. That's typically for parked or addon domain names. Thank you.
    I had a feeling, i will ask my host admin if we can gain root access, sometimes they allow it on reseller accounts. Is it possible to user the USER LEVEL FILTERING on ALL ACCOUNT but not specifically to a domain i think, for example is it possible to not use the domain path and just add the user level filter yaml file to be available for all domains ? You have been very helpful
    0
  • cPanelMichael
    [quote="menkom, post: 1469772">Is it possible to user the USER LEVEL FILTERING on ALL ACCOUNT but not specifically to a domain i think, for example is it possible to not use the domain path and just add the user level filter yaml file to be available for all domains ?
    The user level filters are stored in the directory associated with the email account. For example, if you create "123@domain.com", then the user level filter is stored in: /home/username/etc/domain.com/123 The exception to this is the default email address of the account, which is the account username. That filter is stored in: /home/username/etc It's not possible to apply a user level filter to all accounts, as that is essentially what the account level filtering option is for. Thank you.
    0
  • menkom
    [quote="cPanelMichael, post: 1470111">The user level filters are stored in the directory associated with the email account. For example, if you create "123@domain.com", then the user level filter is stored in: /home/username/etc/domain.com/123 The exception to this is the default email address of the account, which is the account username. That filter is stored in: /home/username/etc It's not possible to apply a user level filter to all accounts, as that is essentially what the account level filtering option is for. Thank you.
    Ok thanks very much you have answered my question :)
    0
  • PCZero
    Michael I fond this when looking for a way to manually restore account level filters. I see that /etc/vfilters is the file that holds the filters in question which is great. However when I go into that file and add in the filters manually, then go into that clients cPanel/Account Level Filters, they are not listed. How do I make sure these manually added filters show up and are used?
    0
  • cPanelMichael
    [quote="PCZero, post: 1829871">Michael I fond this when looking for a way to manually restore account level filters. I see that /etc/vfilters is the file that holds the filters in question which is great. However when I go into that file and add in the filters manually, then go into that clients cPanel/Account Level Filters, they are not listed. How do I make sure these manually added filters show up and are used?
    Ensure you remove any filter.cache files in the /home/$username/.cpanel directory. Also, make sure /home/$username/.cpanel/filter.yaml is accurate. Thank you.
    0

Please sign in to leave a comment.