For one reason and another, I had a requirement to run a test cron job but with irregular timing to simulate the real scenario of users connecting irregularly.

The trick is to run the cron job on a normal regular interval, but then introduce a pause before it delivers the payload. So in the example below, the job runs every 10 minutes but pauses between 0 and 590 seconds. Thus making it appear semi-random.

First create a simple bash shell script, in say /home/me/demo.sh:

#!/bin/bash
sleep $(($RANDOM%590))s
echo "Hi this email was sent at ${CURRENTDATE}"

The second line tells the script to wait for a random amount of time between 0 and 590 seconds.

It’s important to note that 590 seconds is slightly less than the 10 minute (600 seconds) interval we use in the crontab below which gives a maximum of 10 seconds before the next job starts. Unless you specifically want overlapping jobs, then it’s a good idea to adjust this to allow enough time for each job to complete before the next one!

Next, edit your crontab file:

crontab -e

And add the lines:

MAILTO="<email@domain.tld>"
10 * * * * * bash /home/me/demo.sh

This will run the script and send an email at a random time every 10 minutes or so.

Obviously, you can add your own commands as required.

And as a Brucie bonus, note the MAILTO= setting on the first line. If you ever wondered how to get email notifications from your cron jobs, this is one simple way that will send all of the output created by the job to the email address configured!

Or you can suppress any emails by setting it to MAILTO=””.

And anyway that’s it! Happy cron-ing!

Found This Useful?

If you have found this useful, why not help to support the site and buy me a coffee or perhaps a cheeky beer? Thanks!

Websites Built For You

You may also like Websites Built For You which focuses on web design and development in WordPress, PHP and Javascript.

The post Run A Cron Job With A ‘Random’ Time Interval appeared first on perkinstuff.com.

Completely Disable ClamAV In iRedMail

However, I have found that whilst the steps work, they don’t go quite far enough. The problem is that although the changes stop iRedMail from scanning mails for viruses, they leave ClamAV running in the background.

This means it can still eat up excessive amounts of memory getting ready to do, well nothing!

Completely Disable ClamAV

Just one extra step can completely stop the unwanted service and free up all that precious memory:

sudo update-rc.d clamav-daemon disable
sudo update-rc.d clamav-freshclam disable

Thanks for reading, only a short article but I spent a lot of time working it out so hope it’s useful to some people!

Found This Useful?

If you have found this useful, why not help to support the site and buy me a coffee or perhaps a cheeky beer? Thanks!

Websites Built For You

You may also like Websites Built For You which focuses on web design and development in WordPress, PHP and Javascript.

The post Completely Disable ClamAV In iRedMail appeared first on perkinstuff.com.

Nullmailer is a tiny MTA that is a drop in replacement for the more complex mailers mentioned above. All that it does is accept outgoing mails and forward them via your normal SMTP mail relay server. The examples in this article are based on Debian Linux but should be helpful with other distros as well.

It’s easy to install:

sudo apt-get install nullmailer

Any other mail transfer agent you have installed will be removed as part of the install process.

Configuration (/etc/nullmailer)

Once installed you can modify the configuration files in /etc/nullmailer.

/etc/nullmailer/remotes

This is where you configure the remote mail relay server that your outgoing emails are forwarded through:

<your relay mailserver> smtp --starttls --insecure --port=<portno> --user=<username> --pass=<password>

If you have control over the relay server then I find it easier to leave off the –user and –pass options and instead whitelist the sender IP address.

/etc/nullmailer/helohost

This is where you configure how your server will identify itself when connecting to the remote relay host. This is used when connecting to the remote relay server and literally controls the name used in the SMTP HELO command:

myserver.domain.tld

Will connect to the remote relay server using:

HELO myserver.domain.tld

It’s best to use the fully qualified domain name of the server here, as defined in DNS. Ideally also add a PTR (reverse lookup) record that resolves to the same.

And that’s all! Just a little bit easier than postfix, sendmail or exim!

There are other configuration options as well, but I’ve never found them necessary. There is a link to more information about that at the end of this article.

Testing

You can send a simple test email from the command prompt using the following:

mail -s "Some subject" -a "From: <your from email address>" <your to email address>

so as an example

mail -s "Some subject" -a "From: <steve@senderaddress.tld>" <test@receipientaddress.tld>

You will then be prompted to enter a Cc: address (use ENTER to leave blank) and the email content (use CTRL+D to finish). Hopefully if you have everything set up correctly, the email will arrive in your inbox. It’s a good idea to also test using an external recipient mailbox located on another server just to ensure that the emails are being relayed correctly.

Mail Queue

All mails sent through nullmailer are processed into the mail queue directory. On Debian this is in /etc/spool/nullmailer/queue.

There is no timeout on sending mails, so if there is a problem with delivery it will keep retrying forever. The simple solution to this is a daily cron job such as below which will delete all emails in the queue older than 24 hours:

find /var/spool/nullmailer/queue -mindepth 1 -mtime +1 -delete

You could also modify this to just copy the mails somewhere else for your perusal. In my experience it’s not necessary though as it’s only occasional system alerts using email address such as root@localhost that get stuck.

Need More?

There are some great articles on using nullmailer that go into a lot more technical detail at http://troubleshooters.com/linux/nullmailer/#_Configuring_Nullmailer

Found This Useful?

If you have found this useful, why not help to support the site and buy me a coffee or perhaps a cheeky beer? Thanks!

Websites Built For You

You may also like Websites Built For You which focuses on web design and development in WordPress, PHP and Javascript.

The post Nullmailer: A Simple Mail Transfer Agent appeared first on perkinstuff.com.