Re: $BOGOFILTER_DIR has no effect, rc example: bogofilter_dir not recognized
Masaru Nomiya <[email protected]> Mon, 21 Apr 2025 20:08:15 +0900
| Newsgroups | gmane.mail.bogofilter.general |
|---|---|
| Message-ID | <[email protected]> |
Hello, In the Message; Subject : Re: $BOGOFILTER_DIR has no effect, rc example: bogofilter_dir not recognized Message-ID : <[email protected]> Date & Time: Mon, 21 Apr 2025 11:27:34 +0100 [CE] == Christian Ebert <[email protected]> has written: CE> * Christian Ebert on Saturday, April 19, 2025 at 09:25:30 +0100: CE> > * Christian Ebert on Friday, April 18, 2025 at 19:44:01 +0100: [...] CE> man 1 bogofilter: CE> #v+ CE> ENVIRONMENT CE> Bogofilter uses a database directory, which can be set in the config CE> file. If not set there, bogofilter will use the value of CE> BOGOFILTER_DIR. Both can be overridden by the -d dir option. If none of CE> that is available, bogofilter will use directory $HOME/.bogofilter. CE> #v- CE> Hm, the behaviour I get is very much like: CE> If not set in a config file, bogofilter-dir will be set "as defined in the CE> bogofilter source code" _regardless_ of what the BOGOFILTER_DIR environment CE> says. CE> i.e., BOGOFILTER_DIR never overrides bogofilter-dir - unless when CE> manually set before invocation. In short, to avoid this on MacOS, it is advisable to source .bashrc within .bash_profile to ensure consistent behavior across shell sessions. Please look into Bash configuration files on MacOS. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃\/彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring -- _______________________________________________ bogofilter mailing list [email protected] https://www.bogofilter.org/mailman/listinfo/bogofilter