Search found 3 matches
- 28 Apr 2017 14:20
- Forum: Discussion
- Topic: EFA-Config not being read in MailWatchConf.pm??
- Replies: 2
- Views: 3068
Resolved
Fixed the issue! Perms somehow changed on EFA-Config
- 28 Apr 2017 13:57
- Forum: Discussion
- Topic: EFA-Config not being read in MailWatchConf.pm??
- Replies: 2
- Views: 3068
Re: EFA-Config not being read in MailWatchConf.pm??
This is where the problem seems to be? What can I do for a fix?
Restarting MailScanner ...
readline() on closed filehandle $fh at /usr/share/MailScanner/perl/custom/MailWatchConf.pm line 21.
Use of uninitialized value $db_pass in substitution (s///) at /usr/share/MailScanner/perl/custom ...
Restarting MailScanner ...
readline() on closed filehandle $fh at /usr/share/MailScanner/perl/custom/MailWatchConf.pm line 21.
Use of uninitialized value $db_pass in substitution (s///) at /usr/share/MailScanner/perl/custom ...
- 27 Apr 2017 20:04
- Forum: Discussion
- Topic: EFA-Config not being read in MailWatchConf.pm??
- Replies: 2
- Views: 3068
EFA-Config not being read in MailWatchConf.pm??
Did an update on EFA today and now getting the following errors:
Apr 27 15:07:05 relay-4 MailScanner[1993]: Could not use Custom Function code MailScanner::CustomConfig::InitSQLBlacklist, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBI connect('database ...
Apr 27 15:07:05 relay-4 MailScanner[1993]: Could not use Custom Function code MailScanner::CustomConfig::InitSQLBlacklist, it could not be "eval"ed. Make sure the module is correct with perl -wc (Error: DBI connect('database ...