[BlueOnyx:24209] Re: Easy Migrate Error

2020-08-23 Thread Michael Aronoff

OK, so it wouyld not work before and I tested a few times.

Since my first attempt yesterday I tried a CMU and that failed too so I 
was waiting to hear from you.


I just went to try again since you asked for the info from the messages 
log and now it is working!


I feel like I am going insane. I am going to try and do this myself now 
and I will let you know if I have any trouble.


Thanks,
_
M Aronoff Out – maron...@gmail.com

I'm a great believer in luck, and I find the harder I work the more I have of 
it.
  - Thomas Jefferson

-- Original Message --
From: "Michael Stauber" 
To: blueonyx@mail.blueonyx.it
Sent: 8/23/2020 12:24:47 PM
Subject: [BlueOnyx:24205] Re: Easy Migrate Error


Hi Michael,


 I submitted a support ticket in the GUI of the server in question but I
 thought I would ask here as well.


Sorry. I didn't get that ticket. Again. :-(

Not sure how or why. Last time this didn't work I overhauled the ticket
system mechanism to make darn sure that either I get a ticket, or you
get an error message.


 I am trying to migrate a 5209R to a 5210R and when I try and use Easy
 Migrate with the following:
 /usr/sausalito/sbin/easy-migrate.pl --source 208.67.253.1 -p 909 --ip
 208.67.253.2 --vsites www.somedomain.com --nodns

 It starts and then I get this error.

 [MIGRATION_START] Starting Migration of Vsite www.somedomain.com
 ERROR: Unable to get target Vsite baseline.


In that case please check /var/log/messages. It should tell you why it
failed to create a dummy Vsite in order to get the baseline
configuration. Please let me know what it reported there.

--
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx



___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx


[BlueOnyx:24208] Re: help with crontab <- archive

2020-08-23 Thread Meaulnes Legler @ MailList

thank you Michael for the fast reply!

BTW, I guess you had to answer this question already in the past, like probably 
other questions...

There is this BlueOnyx archive at https://mail.blueonyx.it/pipermail/blueonyx/

But one cannot browse thru the whole archive to dig for tips and tricks, one 
has to seek in each monthly [Thread] or [Subject] or download the zip-file and 
search there...

This is very cumbersome and then it's easier to ask on the list — what isn't 
very efficient (from your point of view, I presume:-)

Isn't there a better way?

Thanks again and best regards

ベ⊃ Meaulnes Legler
Zurich, Switzerland
+41¦0 44 260-1660


On 23.08.20 21:21, Michael Stauber wrote:

Hi Meaulnes,


I want to install a shell script that runs every day with crontab.

Now I know there is some catch on BlueOnyx for doing that but I didn't
jot it down.


So there*is*  a crontab file but I can't edit it the normal way... can I
just edit /etc/crontab and add my line like
5 4 * * * root /root/myScript.sh    # run myScript.sh every day at 04:05
without breaking anything?
Do I have to restart some service?

There are a couple of different ways how this can be done.

You can use "crontab -e" to create a new Root cronjob. There isn't one
already, but when you use "crontab -e" it'll fire up the VIM editor,
allows you to specify your cronjob and when you than save it, you can
see it in being present when you run "crontab -l".

Or you can put the cronjob into a file like /root/mycron and can then
run "crontab /root/mycron" to put it into effect. Likewise: Afterwards
"crontab -l" will show that cronjob as being present.

Another way is to put your cronjob into one of the existing config
directories of cron:

[root@5209r ~]# tree -d /etc/cron*|grep -v error
/etc/cron.d
/etc/cron.daily
/etc/cron.half-hourly
/etc/cron.hourly
/etc/cron.monthly
/etc/cron.quarter-daily
/etc/cron.quarter-hourly
/etc/cron.weekly

Take a look at the scripts that are already in these directories to get
some idea. Whatever is in /etc/cron.daily gets executed once per day.

Whatever is in/etc/cron.d/  gets executed by the time configured in the
config files.

Example:

[root@5209r ~]# cat /etc/cron.d/swatch.cron
# swatch is the system watcher
*/15 * * * *root/usr/sausalito/sbin/swatch.sh >/dev/null 2>&

As you can see there, /etc/cron.d/swatch.cron makes sure that
/usr/sausalito/sbin/swatch.sh gets executed every 15 minutes.

Typically when I add cronjobs, I just put a config file like this into
/etc/cron.d/, as it's the easiest and most transparent way.

When you create such a new config file, it is best to restart crond like
this: "systemct restart crond".

-- With best regards Michael Stauber



___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx


[BlueOnyx:24207] Re: AVSpam

2020-08-23 Thread Michael Stauber
Hi Richard,

> x-spam-status: No, score=4.7 required=5.0 tests=BAYES_00,DCC_CHECK,
> DKIMWL_WL_MED,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,FSL_BULK_SIG,
> HEADER_FROM_DIFFERENT_DOMAINS,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,
> MIME_HTML_ONLY,RATS_SPAM,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_NONE,SPF_PASS,
>     TXREP,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=no

Yeah, this one rattled the fence quite a bit. The sender is listed in
the RBL RATS_SPAM and in RCVD_IN_BL_SPAMCOP_NET, plus he had URLs in the
email body that are listed in URIBL_BLOCKED. Oh, and it's also listed in
DCC.

The thing here is: While the AV-SPAM assignes a positive score to all
these indicators, none of them is high enough to warrant an outright
marking as SPAM.

But you can easily throw in your own scores for existing rules.

For example, create /etc/mail/spamassassin/richard.cf and then put this
into it:

score RATS_SPAM 2.5
score DCC_CHECK 2.5
score RCVD_IN_BL_SPAMCOP_NET 2.5
score UNPARSEABLE_RELAY 2.5

Save it and restart spamassassin: "systemctl restart spamassassin".

That assigns scores of 2.5 to each of these three rules. In that case
these would have given the email a score of 10.0, even though some
negative modifiers like DKIM_SIGNED, DKIM_VALID_EF and the BAYES_00
might lower it to about 8.0. Which would still be enough to clearly mark
it as SPAM.

I also recommend adding a small custom rule. Here is a favorite of mine:

meta DCC_AND_HTML (DCC_CHECK && HTML_MESSAGE)



scoreDCC_AND_HTML 10.00



describe DCC_AND_HTML Listed in DCC and sending HTML messages.

If it's a HTML message *and* it's listed in DCC, then it gets a SPAM
score of 10.00 and nothing but a straight whitelist of the sender will
put it back into good graces again.

-- 
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx


[BlueOnyx:24206] Re: Database problem migrating from 5209R to 5210R

2020-08-23 Thread Michael Stauber
Hi Michael,

> On the 5209R you have MariaDB 10.3 and 10.4 available but on the 5210R
> there is only the built in 10.3. So it is possible to be doing a
> migration where we are moving backwards a MariaDB version.

Outch. Yes, that explains the issue. I didn't think of that possibility.

> Would it be possible to make a 10.4 for 5210R so that this is not a problem?

Yeah, I guess I'll have to do that. I'll see to it.

-- 
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx


[BlueOnyx:24205] Re: Easy Migrate Error

2020-08-23 Thread Michael Stauber
Hi Michael,

> I submitted a support ticket in the GUI of the server in question but I
> thought I would ask here as well.

Sorry. I didn't get that ticket. Again. :-(

Not sure how or why. Last time this didn't work I overhauled the ticket
system mechanism to make darn sure that either I get a ticket, or you
get an error message.

> I am trying to migrate a 5209R to a 5210R and when I try and use Easy
> Migrate with the following:
> /usr/sausalito/sbin/easy-migrate.pl --source 208.67.253.1 -p 909 --ip
> 208.67.253.2 --vsites www.somedomain.com --nodns
> 
> It starts and then I get this error.
> 
> [MIGRATION_START] Starting Migration of Vsite www.somedomain.com
> ERROR: Unable to get target Vsite baseline.

In that case please check /var/log/messages. It should tell you why it
failed to create a dummy Vsite in order to get the baseline
configuration. Please let me know what it reported there.

-- 
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx


[BlueOnyx:24204] Re: help with crontab

2020-08-23 Thread Michael Stauber
Hi Meaulnes,

> I want to install a shell script that runs every day with crontab.
> 
> Now I know there is some catch on BlueOnyx for doing that but I didn't
> jot it down.
> 
>
> So there *is* a crontab file but I can't edit it the normal way... can I
> just edit /etc/crontab and add my line like
> 5 4 * * * root /root/myScript.sh    # run myScript.sh every day at 04:05
> without breaking anything?
> Do I have to restart some service?
There are a couple of different ways how this can be done.

You can use "crontab -e" to create a new Root cronjob. There isn't one
already, but when you use "crontab -e" it'll fire up the VIM editor,
allows you to specify your cronjob and when you than save it, you can
see it in being present when you run "crontab -l".

Or you can put the cronjob into a file like /root/mycron and can then
run "crontab /root/mycron" to put it into effect. Likewise: Afterwards
"crontab -l" will show that cronjob as being present.

Another way is to put your cronjob into one of the existing config
directories of cron:

[root@5209r ~]# tree -d /etc/cron*|grep -v error
/etc/cron.d
/etc/cron.daily
/etc/cron.half-hourly
/etc/cron.hourly
/etc/cron.monthly
/etc/cron.quarter-daily
/etc/cron.quarter-hourly
/etc/cron.weekly

Take a look at the scripts that are already in these directories to get
some idea. Whatever is in /etc/cron.daily gets executed once per day.

Whatever is in /etc/cron.d/ gets executed by the time configured in the
config files.

Example:

[root@5209r ~]# cat /etc/cron.d/swatch.cron
# swatch is the system watcher
*/15 * * * *root/usr/sausalito/sbin/swatch.sh >/dev/null 2>&

As you can see there, /etc/cron.d/swatch.cron makes sure that
/usr/sausalito/sbin/swatch.sh gets executed every 15 minutes.

Typically when I add cronjobs, I just put a config file like this into
/etc/cron.d/, as it's the easiest and most transparent way.

When you create such a new config file, it is best to restart crond like
this: "systemct restart crond".

-- 
With best regards

Michael Stauber
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx


[BlueOnyx:24203] help with crontab

2020-08-23 Thread Meaulnes Legler @ MailList

hello

I want to install a shell script that runs every day with crontab.

Now I know there is some catch on BlueOnyx for doing that but I didn't jot it 
down.

[root@vs ~] # crontab -l
returns nothing

[root@vs ~] # crontab -u admin -l
no crontab for admin

[root@vs ~] # crontab -e
edits an empty file

[root@vs ~] # ls -l /etc/crontab
-rw-r--r-- 1 root root 620 2017.03.28-02:57 /etc/crontab


[root@vs ~] # less /etc/crontab
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root

# For details see man 4 crontabs

# Example of job definition:
# . minute (0 - 59)
# |  .- hour (0 - 23)
# |  |  .-- day of month (1 - 31)
# |  |  |  .--- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  . day of week (0 - 6) (Sunday=0 or 7) OR 
sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name  command to be executed

04,34 * * * * root run-parts /etc/cron.half-hourly
03,18,33,48 * * * * root run-parts /etc/cron.quarter-hourly
46 0,6,12,18 * * * root run-parts /etc/cron.quarter-daily
/etc/crontab lines 1-18/18 (END)


So there *is* a crontab file but I can't edit it the normal way... can I just 
edit /etc/crontab and add my line like
5 4 * * * root /root/myScript.sh# run myScript.sh every day at 04:05
without breaking anything?
Do I have to restart some service?

Thank you and best regards

で⊃ Meaulnes Legler
Zurich, Switzerland
+41¦0 44 260-1660


___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx