RE: Has anyone tried MailScanner on CentOS 7?

[Mogens Melander]

Well,

"Why did tarballs fall out of grace?" Sorry for the following ...

When you delegate all the difficult stuff to the maintainers,
of whatever OS you're running on your hardware, so you can
focus on doing, whatever you wanted your software to do.

Me, I'm on slackware variants, and nobody supports that, so I
have to change/patch all those packages going out to you
lazy guys, expecting  software coming updated, specially for
your choice of hardware/OS combination.

Pretty much all important software, running on my servers, I
have made build scripts, to compile compliant install packages,
to install in the tool chain. Zenwalk not being maintained
anymore, I'm moving my servers to Salix, going back to where
I started. Slackware. There is no possible way to upgrade
my old server/kernel with out sending someone to do it hands on.

So, Zenwalk is out, and Slackware is back in.

Basically, what I'm saying. I'm not alone, being older than 40,
maintaining servers that has been running for more than 1780
days, without a single reboot. Patches/upgrades are done online,
on running production systems.

And that's why tarballs are not in grace. They are used by the
original linux distributions.

This is my personal thinking, after a long night of hard drinking,
just stumbling, noticing that lead comment:

"Why did tarballs fall out of grace?"

Peace.

On Sun, September 14, 2014 21:13, Remco Barendse wrote:
> So far, i did not manage to become friends with github (yet?).  Hope that
> sometime there will be a small (maintained) website with info on how to
> pull the latest stable version from github and install from that.
>
> (Why did tarballs fall out of grace?)
>
> Cheers!
>
>
> On Fri, 8 Aug 2014, Randal, Phil wrote:
>
>> MailScanner - latest release plus updated updated TNEF.pm from Git
>> (https://github.com/MailScanner/v4/pull/29) and my phishing filter fix (
>> https://github.com/MailScanner/v4/pull/30)
>>
>> This patchset might be useful too, but I don't know for sure:
>> https://github.com/MailScanner/v4/commit/0b59afc1dde177150331248179d64d12820512c8
>> (uses IO::Pipe instead of IO)
>>
>> MailWatch - latest from Git (https://github.com/mailwatch/1.2.0)
>>
>> Cheers,
>>
>> Phil
>>
>> -----Original Message-----
>> From: mailscanner-bounces at lists.mailscanner.info
>> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Glenn
>> Steen
>> Sent: 08 August 2014 09:39
>> To: MailScanner discussion
>> Subject: Re: Has anyone tried MailScanner on CentOS 7?
>>
>> Hi Phil,
>>
>> As you may remember (or not), I used to use Mandriva for my servers (up
>> until the Mandriva/Mageia split), so this sounds ... easy and
>> straightforward:-). No mixing in CPAN when all else fails;-).
>>
>>
>> On 7 August 2014 22:08, Randal, Phil <phil.randal at hoopleltd.co.uk>
>> wrote:
>>>
>>> OK, here’s a fuller list of what I did to get MailScanner running on
>>> CentOS 7
>>>
>> (snip)
>>>
>>> Cheers,
>>>
>>>
>>>
>>> Phil
>>>
>> As said, this all seems quite straightforward, so ... I'll do that
>> then:-). Which MW install did you use?
>>
>>>
>>>
>>> From: mailscanner-bounces at lists.mailscanner.info
>>> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of
>>> Randal, Phil
>>> Sent: 07 August 2014 16:22
>>> To: MailScanner discussion
>>> Subject: RE: Has anyone tried MailScanner on CentOS 7?
>>>
>>>
>>>
>>> No,
>>>
>>>
>>>
>>> I didn’t try them.
>>>
>> Ok, some fun and games to look forward to then:-).
>>
>>>
>> (snip)>
>>>
>>> Only gotcha I had was forgetting to ensure that /etc/hosts had a
>>> correct entry for the host in it.  They joys of cloning VMs and
>>> forgetting the little details.
>>>
>> Isn't it a bitch, progress:-):-). Do you use any prebuilt VM, or rolled
>> your own?
>>
>>>
>>>
>>> Phil

-- 
Mogens Melander
+66 8701 33224


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.