Upgrade Wrecks MailScanner

[Daniel Malmgren]

Hi.

Sorry for jumping in a bit late here (and not really having read the 
entire thread), but it kinda feels like you have about the same problems 
as I've had the last few days, see this thread: 
http://lists.mailscanner.info/pipermail/mailscanner/2016-October/103868.html

Questions:

Did you try running MailScanner --debug (after stopping the service and 
when there's at least one mail in the queue to process) to see what it says?

Did you copy the MailWatch scripts (MailWatch.pm and 
SQLBlackWhiteList.pm) to the new directory for custom functions 
(/usr/share/MailScanner/perl/custom)?

/Daniel


Den 2016-10-13 kl. 00:38, skrev Paul Scott:
> Hello Everybody,
>
> Well, I finally got MailScanner working enough for now so that it is now scanning messages AND eventually releasing them after doing it's checks.
>
> How?
>
> I commented out the lines in the following MailScanner.conf area, where they were setup to log to MAILWATCH (changed it back to MailScanner's defaults):
>
> # Spam Whitelist:
> # Make this point to a ruleset, and anything in that ruleset whose value
> # is "yes" will *never* be marked as spam.
> # The whitelist check is done before the blacklist check. If anyone whitelists
> # a message, then all recipients get the message. If no-one has whitelisted it,
> # then the blacklist is checked.
> # This setting over-rides the "Is Definitely Spam" setting.
> # This can also be the filename of a ruleset.
> Is Definitely Not Spam = no
> #Is Definitely Not Spam = &SQLWhitelist
>            
> # Spam Blacklist:
> # Make this point to a ruleset, and anything in that ruleset whose value
> # is "yes" will *always* be marked as spam.
> # This value can be over-ridden by the "Is Definitely Not Spam" setting.
> # This can also be the filename of a ruleset.
> #Is Definitely Spam = &SQLBlacklist
>
> So now I guess I have to figure out how to get MailWatch working again, but at least MailScanner seems to FINALLY be running.  This has been a heck of a nightmare for me, and I GREATLY appreciate all of your assistance!
>
> Sincerely, Paul Scott
> www.edenusa.com
>
>
> -----Original Message-----
> From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Wolfgang Baudler
> Sent: Wednesday, October 12, 2016 2:15 PM
> To: MailScanner Discussion <mailscanner at lists.mailscanner.info>
> Subject: RE: Upgrade Wrecks MailScanner
>
>> Hello again Wolfgang,
>>
>> I may have spoken too soon.  Now, I have yet another issue.  It
>> appears that the messages that are being put in the "Processing
>> Attempts Database", are not being released:
>>
>> Oct 12 13:57:37 mail MailScanner[4102]: Connected to Processing
>> Attempts Database Oct 12 13:57:37 mail MailScanner[4102]: Found 10
>> messages in the Processing Attempts Database Oct 12 13:57:37 mail
>> MailScanner[4102]: Using locktype = flock
>>
>> I am up to 10 messages now, and none have completed processing and
>> been released out.  This is much more serious than what was happening
>> before, as now nobody is getting any email.  What do you think is going on?
>>
>> Thank you again,
>> Paul Scott
> Not sure if your problem is related to the Processing Attempts Database.
> Maybe someone else can comment on that.
>
> Are your sendmail processes running properly? Did you stop your old "plain" sendmail service?
>
> ps -ef |grep sendmail
>
> output would help. Also check your queue directories. My /var/spool/mqueue.in directory was gone after the Mailscanner 5.x upgrade for some reason.
>
> ls -ald /var/spool/*queue*
>
> output would help.
>
> Wolfgang
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
>