Upgrade Wrecks MailScanner
Daniel Malmgren
daniel at kolefors.se
Fri Oct 14 06:16:14 UTC 2016
Oh. Never noticed this directory. Indeed it contains some files from
/etc. Seems like something in the upgrade isn't doing it's job though,
at least on my server, because it doesn't contain any CustomFunctions.
Here are the contents of my ms_upgrade directory:
.
├── saved.21185
│ └── etc
│ ├── default
│ │ └── mailscanner
│ └── MailScanner
│ └── reports
│ └── reports
│ ├── en
│ │ ├── deleted.content.message.txt
│ │ ├── deleted.filename.message.txt
│ │ ├── deleted.size.message.txt
│ │ ├── deleted.virus.message.txt
│ │ ├── disinfected.report.txt
│ │ ├── inline.sig.html
│ │ ├── inline.sig.txt
│ │ ├── inline.spam.warning.txt
│ │ ├── inline.warning.html
│ │ ├── inline.warning.txt
│ │ ├── languages.conf
│ │ ├── recipient.mcp.report.txt
│ │ ├── recipient.spam.report.txt
│ │ ├── rejection.report.txt
│ │ ├── sender.content.report.txt
│ │ ├── sender.error.report.txt
│ │ ├── sender.filename.report.txt
│ │ ├── sender.mcp.report.txt
│ │ ├── sender.size.report.txt
│ │ ├── sender.spam.rbl.report.txt
│ │ ├── sender.spam.report.txt
│ │ ├── sender.spam.sa.report.txt
│ │ ├── sender.virus.report.txt
│ │ ├── stored.content.message.txt
│ │ ├── stored.filename.message.txt
│ │ ├── stored.size.message.txt
│ │ └── stored.virus.message.txt
│ └── se
│ ├── deleted.content.message.txt
│ ├── deleted.filename.message.txt
│ ├── deleted.size.message.txt
│ ├── deleted.virus.message.txt
│ ├── disinfected.report.txt
│ ├── inline.sig.html
│ ├── inline.sig.txt
│ ├── inline.spam.warning.txt
│ ├── inline.warning.html
│ ├── inline.warning.txt
│ ├── languages.conf
│ ├── recipient.mcp.report.txt
│ ├── recipient.spam.report.txt
│ ├── rejection.report.txt
│ ├── sender.content.report.txt
│ ├── sender.error.report.txt
│ ├── sender.filename.report.txt
│ ├── sender.mcp.report.txt
│ ├── sender.size.report.txt
│ ├── sender.spam.rbl.report.txt
│ ├── sender.spam.report.txt
│ ├── sender.spam.sa.report.txt
│ ├── sender.virus.report.txt
│ ├── stored.content.message.txt
│ ├── stored.filename.message.txt
│ ├── stored.filename.message.txt.bak
│ ├── stored.size.message.txt
│ └── stored.virus.message.txt
└── saved.21322
└── etc
└── MailScanner
├── MailScanner.conf.dist
├── MailScanner.conf.original
└── MailScanner.new
11 directories, 59 files
/Daniel
Den 2016-10-14 kl. 08:05, skrev Jerry Benton:
> Daniel,
>
> The upgrade process does save file.
>
> SAVEDIR="$HOME/ms_upgrade/saved.$$”;
>
>
> The script copies numerous files to: ${SAVEDIR}/etc/MailScanner/
>
> The MailScanner.conf is copied to MailScanner.conf.original
>
> Custom functions and the like are copied to:
> ${SAVEDIR}/etc/MailScanner/CustomFunctions
>
>
> -
> Jerry Benton
> www.mailborder.com
> +1 - 844-436-6245
>
>
> -----Original Message-----
> From: Daniel Malmgren <daniel at kolefors.se>
> Reply: MailScanner Discussion <mailscanner at lists.mailscanner.info>
> Date: October 14, 2016 at 1:57:04 AM
> To: MailScanner Discussion <mailscanner at lists.mailscanner.info>
> Subject: Re: Upgrade Wrecks MailScanner
>
>> Hi Jerry.
>>
>> First and foremost, thank you for all the work you've put into the
>> project! I'm also a developer in open source projects so I know how
>> ungrateful it is. I also know it is a problem that many users seem to
>> think they have the right to demand things, which they of course have no
>> right to do since they're not paying customers.
>>
>> I myself didn't do the research that I should have done before upgrading
>> and so my mail server was down for almost a day before I found the
>> problems (now everything is up and running again). It's only a hobby
>> project though that is used by my family and neighbours and they aren't
>> paying me anything neither so they can live with it :-)
>>
>> My advice regarding the problems that me and others have been having
>> with the upgrade is to look over the way that the custom scripts are
>> handled by the install script. In my case they were simply deleted and I
>> had to get them from backup. People could potentially have put much time
>> in customizing those scripts so deleting them isn't a good idea. I think
>> the installer should either leave them where they are and show a notice
>> about this or simply copy them over to the new location. At least the
>> ones that doesn't come with mailscanner (ie the ones that the user put
>> there himself).
>>
>> /Daniel
>>
>>
>> Den 2016-10-14 kl. 07:33, skrev Jerry Benton:
>>> Ok, enough.
>>>
>>> I took over the MailScanner project in January 2014. At that point it
>>> had largely been abandoned. The code was woefully outdated and the
>>> structure was just plain wrong according to FHS. I updated everything
>>> to work with the modern versions of Perl. I thinned out a lot crap. I
>>> lterally put MONTHS of work into this.
>>>
>>> I am also the sole financial supporter this project. To date, I have
>>> received $220 in donations. This is over almost 3 years. For the most
>>> part, I do pretty much everything. Mark helps me with sanity checks,
>>> my crap Perl skills, and proposes fixes on MailScanner items. A couple
>>> of times some community users have helped research some issues.
>>> (Thanks BTW)
>>>
>>> The upside to using open source software is that it is free. The
>>> downside is that you need to be pretty adept at what you are doing.
>>> This is why there are a lot of companies that take open source
>>> software and build commercial products from them. You are paying them
>>> to make it simple. I paid $3000 for a Synology NAS that has software
>>> in it that I wrote. That’s right, I paid for a product that contains
>>> my own work. Go figure.
>>>
>>> No, everything is not documented in spectacular fashion. This is
>>> mainly because I have to do other things so my family can do things
>>> like eat and have a place to live. I put a lot of time into
>>> MailScanner because I use it in my own commercial product. That seems
>>> pretty damn fair on my side of the equation considering most companies
>>> do not contribute jack shit to the open source product they profit
>>> from.
>>>
>>> If MailScanner v5 does not work with MailWatch, which I know it does,
>>> I really do not care. Those guys have a commercial product that also
>>> makes money off the work that I do. Do they donate to the project?
>>> Hell no. I have never even had a conversation with them.
>>>
>>> I do not mean to sound cold or harsh, but you are essentailly bitching
>>> at me because this free product created a lot of challenges for you
>>> during the upgrade process. It appears that you did not have a plan to
>>> roll back in the event of an upgrade failure. That is not on me.
>>>
>>> You said you prepared for the upgrade. You did not. For future reference:
>>>
>>> - never apply a major upgrade to a critical system without testing it
>>> in a lab first
>>> - have a rollback plan
>>> - instead of upgrading an ancient server, build a new one and shift the email
>>> - do not blame me
>>>
>>>
>>> If you would have done any one of those first three (and always the
>>> 4th), this entire process would have been a lot less urgent and would
>>> not have impacted your operations.
>>>
>>>
>>>
>>> -
>>> Jerry Benton
>>> www.mailborder.com
>>> +1 - 844-436-6245
>>>
>>>
>>> -----Original Message-----
>>> From: Paul Scott
>>> Reply: MailScanner Discussion
>>> Date: October 13, 2016 at 9:17:44 PM
>>> To: MailScanner Discussion
>>> Subject: RE: Upgrade Wrecks MailScanner
>>>
>>>> Actually, not sure what this means ("Good. Throw it out and start over.") Care to explain?
>>>>
>>>> And insofar as your "do more research and preparation before upgrading", I did exactly
>>>> that, and nowhere was there any great deal of information available which would prepare
>>>> anybody for what is actually happening to them. How would you suggest preparing for
>> this?
>>>> And just because someone decides to bump something up from 4.85 to 5.x.x, is that an
>> excuse
>>>> for breaking so much of it? Not too much in change logs alluding to the issues which have
>>>> been happening to a lot of us out here.
>>>>
>>>> In conclusion, I am not trying to make excuses for myself, nor should anyone else. I
>> am
>>>> VERY THANKFUL for all of the assistance I received from everybody on this forum. Without
>>>> you guys, I would have probably been fired from my job.
>>>>
>>>> THANK YOU!
>>>> Paul Scott
>>>> https://www.edenusa.com
>>>>
>>>> -----Original Message-----
>>>> From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info]
>>>> On Behalf Of McMannis
>>>> Sent: Thursday, October 13, 2016 6:03 PM
>>>> To: 'MailScanner Discussion'
>>>> Subject: RE: Upgrade Wrecks MailScanner
>>>>
>>>> Good. Throw it out and start over.
>>>>
>>>> -----Original Message-----
>>>> From: MailScanner
>>>> [mailto:mailscanner-bounces+mcmannis=intergate.com at lists.mailscanner.info]
>>>> On Behalf Of Mark Sapiro
>>>> Sent: Thursday, October 13, 2016 4:19 PM
>>>> To: mailscanner at lists.mailscanner.info
>>>> Subject: Re: Upgrade Wrecks MailScanner
>>>>
>>>> On 10/13/2016 01:35 PM, Paul Scott wrote:
>>>>> Auto: Found virus scanners: clamavmodule LibClamAV Warning:
>>>>> **************************************************
>>>>> LibClamAV Warning: *** The virus database is older than 7 days! ***
>>>>> LibClamAV Warning: *** Please update it as soon as possible. ***
>>>>> LibClamAV Warning: **************************************************
>>>>> LibClamAV Warning:
>>>> ***********************************************************
>>>>> LibClamAV Warning: *** This version of the ClamAV engine is outdated.
>>>> ***
>>>>> LibClamAV Warning: *** DON'T PANIC! Read
>>>>> http://www.clamav.net/support/faq *** LibClamAV Warning:
>>>>> ***********************************************************
>>>> Try using yum or whatever to install/update clamav, clamd and freshclam.
>>>> Also, running clamd is much preferred to the clamav module. If clamd is
>>>> running, Virus Scanners = auto will use it.
>>>>
>>>>
>>>>> 4. And every now and again, I get these kind of error messages in the
>>>> maillog:
>>>>> Oct 13 13:07:44 mail MailScanner[4773]: Could not open file
>>>>>> /var/spool/MailScanner/incoming/4773/u9DK7gOS005688.header: No such
>>>>> file or directory Oct 13 13:07:44 mail MailScanner[4773]: Cannot
>>>>> create + lock headers file
>>>>> /var/spool/MailScanner/incoming/4773/u9DK7gOS005688.header
>>>>
>>>> What is the owner and group of /var/spool/MailScanner/incoming/, and what
>>>> user and group are the MailScanner processes running as?
>>>>
>>>>
>>>>> I noticed that there are a few other folks having the same or similar
>>>> issues as I ran into using the install.sh script. I feel that this is going
>>>> to become a large support issue, and I feel badly for all of us out here in
>>>> the world that are running into this problem.
>>>>
>>>>
>>>> I'm sorry for the difficulty that you and others have experienced in
>>>> upgrading from Mailscanner 4.x.x to 5.x.x. I'm sure there's much room for
>>>> improvement in the scripts and documentation, but please note that this is
>>>> not a micro or minor point release upgrade. It is a major version jump. As
>>>> such you should expect that things will change and do more research and
>>>> preparation before actually upgrading.
>>>>
>>>> --
>>>> Mark Sapiro The highway is for gamblers,
>>>> San Francisco Bay Area, California better use your sense - B. Dylan
>>>>
>>>>
>>>> --
>>>> MailScanner mailing list
>>>> mailscanner at lists.mailscanner.info
>>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>
>>>>
>>>> --
>>>> This message has been scanned for viruses and
>>>> dangerous content by MailScanner, and is
>>>> believed to be clean.
>>>>
>>>>
>>>>
>>>> --
>>>> This message has been scanned for viruses and
>>>> dangerous content by MailScanner, and is
>>>> believed to be clean.
>>>>
>>>>
>>>>
>>>> --
>>>> MailScanner mailing list
>>>> mailscanner at lists.mailscanner.info
>>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>
>>>>
>>>>
>>>> --
>>>> MailScanner mailing list
>>>> mailscanner at lists.mailscanner.info
>>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>>
>>>>
>>
>>
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>>
>
More information about the MailScanner
mailing list