ermcenter.com

Home > Failed To > Failed To Parse Line Use_auto_whitelist 0

Failed To Parse Line Use_auto_whitelist 0

On the plus side, it does confirm you've correctly disabled the plugin. I am using it with amavisd-new 2.3.3. you already see the problem in that line press s in less to save the whole output if unsure what to do, and then pastebin it on a webpage and This might just be root's user_prefs, which wouldn't affect MailScanner runs, but does affect lint runs as root. http://ermcenter.com/failed-to/failed-to-parse-xml-rpc-request.html

Thats all for now.. The reason I do it this way, as opposed to the standard vpopmail way (@GLOBAL), is so the preferences in my user_pref database order correctly... FTR - It looks like a third line use_auto_whitelist 0 is also not valid any longer. May 3 11:19:20.624 [621] dbg: util: running in taint mode? http://lists.mailscanner.info/pipermail/mailscanner/2011-August/098242.html

You found it in spam.assassin.prefs.conf, but it must be somewhere else as well. All SpamAssassin needs is SELECT access to the userpref table. The query must return preference and value sorted accordingly. Affecting: spamassassin (Ubuntu) Filed here by: bersyl91 When: 2010-12-11 Completed: 2010-12-13 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu

Lesson learned, keep things together not in different files, makes for easier tracking Top Display posts from previous: All posts1 day7 days2 weeks1 month3 months6 months1 year Sort by AuthorPost timeSubject In qmail-scanner, I do the following.. Is this a contrib or custom template issue? Contact Us Help Home Top RSS iHax Community Terms and Rules iHax Community iHax Community

I deleted the auto-whitelist files, ran three commands: touch /var/spool/spamd/.spamassassin/auto-whitelist touch /var/spool/spamd/.spamassassin/auto-whitelist.mutex chown spamd:spamd touch /var/spool/spamd/.spamassassin/auto-* then re-started spamd with "sv t spamd" then confirmed that AWL was working using sa-awl Top ovizii Posts: 275 Joined: 11 May 2016 08:08 Re: Problems with mailscaner.cf Quote Postby ovizii » 14 May 2016 16:01 I've copied the text straight from my ssh session. Dezember 2005 19:05 Peter wrote: > > [12981] info: config: failed to parse line, skipping: > > use_auto_whitelist 1 [12981] info: config: failed to parse line, > > skipping: use_razor2 1 https://wiki.apache.org/spamassassin/UsingSQL not using the suggested query, it _should_ _not_ return the roll 'username' or you'll receive an error like 'info: config: failed to parse line, skipping, in "(no file)": [email protected]_ _config_tag_'.

use whatever you want. Top shawniverson Posts: 1743 Joined: 13 Jan 2014 23:30 Location: Rushville, Indiana, USA Contact: Contact shawniverson Website Re: Problems with mailscaner.cf Quote Postby shawniverson » 14 May 2016 15:37 Any problems Global, Per-Domain, and Per-User Preferences via SQL SpamAssassin 3.0 supports the config option user_scores_sql_custom_query - Using this feature, one can accomplish any number of custom configuration for supporting tiered user preferences. To acheive proper sorting of SQL prefs, I use the following custom_query: user_scores_sql_custom_query SELECT preference, value FROM _TABLE_ WHERE username = _USERNAME_ OR username = '$GLOBAL' OR username = CONCAT('%',_DOMAIN_) ORDER

Recent . http://spamassassin.1065346.n5.nabble.com/spamd-18549-config-failed-to-parse-line-skipping-in-quot-etc-mail-spamassassin-local-cf-quot-use-aut1-td66255.html I am getting these messages when I start amavisd-new: [12981] info: config: failed to parse line, skipping: use_auto_whitelist 1 [12981] info: config: failed to parse line, skipping: use_razor2 1 [12981] info: Set package. To debug it, make sure spamd is not running, and from the command line, start spamd in foreground (no -d flag) mode with full debugging enabled (-D), and watch for the

I dont know what I can do for theuse_auto_whitelist setting.For the pyzor error, I run another test:spamassassin -D -t spammail.txt 2>&1 | grep -i pyzor[root at szeta cur]# spamassassin -D -t http://ermcenter.com/failed-to/failed-to-parse-wsdl-wsimport.html Fun Fun! Pagemakers Silver Pleskian 23 73% Messages: 661 Likes Received: 6 Trophy Points: 412 When I run spamassassin --lint I get the following errors. Version 3.0.1.5 released!

Format For Printing -XML -Clone This Bug -Top of page Home | New | Browse | Search | [?] | Reports | Requests | Help | NewAccount | Log In Remember yes May 3 11:19:20.639 [621] dbg: dns: Net::DNS version: 0.59 May 3 11:19:21.017 [621] dbg: diag: perl platform: 5.008008 linux May 3 11:19:21.018 [621] dbg: diag: [...] module installed: Digest::SHA1, version Comment 13 Michael McCarn 2012-02-18 06:26:26 CET Created attachment 3433 [details] diff -u /etc/e-smith/templates/etc/mail/spamassassin/local.cf/10use_auto_whitelist /etc/e-smith/templates-custom/etc/mail/spamassassin/local.cf/10use_auto_whitelist (In reply to Michael McCarn from comment #11) > To 'fix' this, do we need to http://ermcenter.com/failed-to/wsimport-failed-to-parse-the-wsdl.html Version 3.0.1.5 released!

Have a good weekend. Set target milestone. Kobus, can you please show us the output of the following command: for f in `grep -ilR auto_whitelist_path /etc/e-smith/templates*/etc/mail/spamassassin/local.cf/`; do echo $f:; rpm -qf $f; done (enter all this at one

If you have not already created it, you will want to run something like.. # mysql > CREATE DATABASE spamassassin; > exit;and then # cat userpref.sql | mysql spamassassinOnce you have

And if neither exist, it will assume global required_hits. Top shawniverson Posts: 1743 Joined: 13 Jan 2014 23:30 Location: Rushville, Indiana, USA Contact: Contact shawniverson Website Re: Problems with mailscaner.cf Quote Postby shawniverson » 14 May 2016 16:15 Is your Is > there a better way? May 3 11:19:23.417 [621] dbg: message: main message type: text/plain May 3 11:19:23.418 [621] dbg: message: ---- MIME PARSER START ---- May 3 11:19:23.418 [621] dbg: message: parsing normal part May

Is your's OK? Changed in spamassassin (Ubuntu): status: New → Fix Committed Scott Kitterman (kitterman) on 2010-12-13 Changed in spamassassin (Ubuntu): status: Fix Committed → Invalid See full activity log To post a comment Burns <[hidden email]> wrote: ram schrieb: > Hi>> i have recently update from 3.2.X to 3.3.X>> when i restart i get this message>> spamd[18549]: config: failed to parse line, skipping, in> Check This Out Note that if you are customizing your query, i.e.

To get this table active in your mysql database, save the syntax above to a file named userpref.sql and run # cat userpref.sql | mysql where is the database you On http://wiki.apache.org/spamassassin/AutoWhitelist I found this: > > "In 3.3, the plugin is not loaded by default." > > If the plugin isn't loaded, SA probably doesn't know what to do with However, there is still a permissions problem with the whitelist files. mysql> select username,preference,value from userpref WHERE (username='$GLOBAL' OR username='%nmgi.com' OR username='[email protected]') ORDER by username ASC; +------------------+-------------------------+------------------------+ | username | preference | value | +------------------+-------------------------+------------------------+ | $GLOBAL | required_hits | 4.00 |

I wrapped it for display purposes only. SQL Table Structure for User Prefs Personally, I use the following table structure for my user prefs... CREATE TABLE `userpref` ( `id` int(8) unsigned NOT NULL auto_increment, `username` varchar(128) NOT NULL default '', `preference` varchar(64) NOT NULL default '', `value` varchar(128) default NULL, `descript` varchar(128) default NULL, `added` However, for proper sorting of userpref when using Per-Domain settings, one must be careful on how SQL sorts the results.

Should the template create empty files with the correct permissions? Burns <[hidden email]> wrote: ram schrieb: > Hi>> i have recently update from 3.2.X to 3.3.X>> when i restart i get this message>> spamd[18549]: config: failed to parse line, skipping, in> Comment 14 Ian Wells 2012-07-07 11:37:03 CEST (In reply to Michael McCarn from comment #13) > However, there is still a permissions problem with the whitelist files. > > With the