MailScanner --lint error

[Glenn Steen]

On 07/08/07, Scott Silva <ssilva at sgvwater.com> wrote:
> Jody Cleveland spake the following on 8/6/2007 4:28 PM:
> >
> >
> > On 8/6/07 5:41 PM, "Scott Silva" <ssilva at sgvwater.com> wrote:
> >
> >> Jody Cleveland spake the following on 8/6/2007 3:05 PM:
> >>> Hello,
> >>>
> >>> I just upgraded to the most current stable release of MailScanner, and when
> >>> I do a MailScanner --lint, I get this error:
> >>>
> >>> Cannot open config file --lint, No such file or directory at
> >>> /usr/lib/MailScanner/MailScanner/Config.pm line 656.
> >>> Compilation failed in require at /usr/sbin/MailScanner line 69.
> >>> BEGIN failed--compilation aborted at /usr/sbin/MailScanner line 69.
> >>>
> >>> Any idea how I can fix this?
> >>>
> >>> - jody
> >>>
> >> Current stable from www.mailscanner.info, or current stable from a packager
> >> like debian or freebsd?
> >
> > The current stable from www.mailscanner.info
> >
> >> Check for .rpmnew files in /usr/lib/MailScanner/MailScanner
> >
> > There's one .rpmnew file. CustomConfig.pm.rpmnew
> >
> > Should I delete this file?
> >
> > - jody
> >
> NO!! Try renaming the CustomConfig.pm to CustomConfig.pm.old and rename
> CustomConfig.pm.rpmnew CustomConfig.pm
>
> Then retry the --lint
>
The question is _why_ there is an .rpmnew file... Did you perhaps use
the old way of incorporating MailWatch? You might benefit from looking
through the old CustomConfig.pm file to see what's there:)

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se