Category Archives: SME Server

Outlook 2013 error 552 SME Server

Outlook 2013 perpetuates an issue with the Test email that is sent when creating a new email account or profile.

The issue has been there since much older versions of Outlook (like Office 97) but was always allowed to error gracefully, report, and be ignored.

The issue is that the Test Email does not have a date in the header. After all why would we want a date on a test email? (dripping with sarcasm!) other than to make it compliant with internet standards (which apparently in the RFC the date is optional, common sense says that adding todays date cannot be that hard, but I digress.

So, Outlook 2013 now has no option to accept the failure becuase ‘the server must be faulty’.

The error is 552 no date in header or similar depending on which flavour of server is reporting it.

For SME Server this could be remedied by allowing no header emails from within the local network, which should not present an issue for spam (which assumes that spammers do not worry about dates either) as it is on the local interface and not opening it up to the public.

This is documented in the SME Server Wiki but it is a simple snippet for a custom template created like this:

mkdir -p /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/local
cd /etc/e-smith/templates-custom/var/service/qpsmtpd/config/peers/local
echo “# 17check_basicheaders disabled by custom template” > 17check_basicheaders
signal-event email-update

The last command resets the mail handling and you should be ok to run the test from the local network. Remote connections, unless on the VPN, will not work as the external interface will continue to reject the message without the date.

SME Server 8.0 Outlook email external connection imaps

I had the need to setup Outlook to connect to an SME Server 8.0 recently and at first glance it seemed easy enough but it did not work as expected.

The primary issue appears to be that Outlook does not like to play with the SME Server SSL or Ports without being shown the way.

The end result is a step by step guide that I have published over at the WrenMaxwell Knowledgebase complete with screenshots of each step.

I suspect that this may well apply to other self-hosted servers beyond SME Server and kept the text generic for that purpose, but if you are trying to get your SME Server to work then the first thing to do is make sure that the imaps and smtps ports are open on the firewall and on the SME server.

The only other thing that needs doing is aligning the server name with the external hostname and the self-issued SSL certificate.

It was interesting that setting up a couple of portable devices, an iPhone, iPad, and Android all worked with the SME Server connection without any specific settings being required, the server was just accepted and worked from the get-go.  Microsoft Outlook, however, seems to raise barriers.

I did reference this Microsoft article KB286197 as a preliminary to this process and found it lacking for the options of secure SSL connections and certainly it has the basics but insufficient detail to guide an appropriate outcome for an SME Server connection.

The SME documentation over at is also lacking a bit of input and I might try to help out there if I can make some time.

SME Server as a Nagios NRPE Client only

If you are wanting to install Nagios on an SME Server version 8 then you will probably start with the Wiki Contribs page for a Nagios Server install.

Which is going to lead you down a path of installing a complete Nagios Server assuming you overcome the issues with those instructions.

But if you have a Nagios Server elsewhere and you want to just add the SME Server as a client then a different set of instructions can be found in the forums.,48587.msg241615.html#msg241615

Which is really helpful but is missing a couple of key points for a complete set of instructions. So here is a re-write of that instruction set.

NRPE SME Server 8 Installation

1. Configure the dag repository

The following command will configure the dag repository on SME Server.


/sbin/e-smith/db yum_repositories set dag repository
Name ‘Dag – EL5’
BaseURL ‘<a href="" target="_blank"></a>$basearch/dag’
EnableGroups no
GPGCheck yes
GPGKey <a href="" target="_blank"></a>
Visible no
Exclude freetype,htop,iptraf,rsync,syslinux
status disabled


2. After adding it to the database we have to update the changes to the configuration file:

[text]signal-event yum-modify[/text]

3. Then run this to enable the repo


/usr/bin/yum –enablerepo=dag install


4. Copy nrpe rpm’s

Current download for the files are:

5. Install the nrpe rpm’s


yum localinstall nagios-3.2.1-5.el5.rf.i386.rpm
yum localinstall nagios-nrpe-2.5.2-1.el5.rf.i386.rpm
yum localinstall nagios-plugins-nrpe-2.5.2-1.el5.rf.i386.rpm


6. Modify the nrpe.cfg file to allow the external ip of your Nagios server  (swap vim for your favourite editor)


vim /etc/nagios/nrpe.cfg


the allowed_hosts parameter is already in the file, remove the # from the start of the line and add your nagios server ip




Save the file and exit.

7. Add the service


cd /etc/rc7.d

cp -s /etc/init.d/nrpe S95nrpe


8. Port forward 5666 to localhost (swap vim for your favourite editor)



mkdir -p /etc/e-smith/templates-custom/etc/hosts.allow/


(if you get an error it means the directory already exists.)



vim /etc/e-smith/templates-custom/etc/hosts.allow/nrpe


and add the following lines to the nrpe file, adding your nagios server ip


$OUT="nrpe: " . ($nrpe{HostsAllow} ? $nrpe{HostsAllow} : "" );


Save the file and exit.

9. Configure the new template


expand-template /etc/hosts.allow


10. Start NRPE


service nrpe restart


And then off to your Nagios server to add the new SME Server as a client.

Raid 1 repair on SMEServer

I had the displeasure to find a failing drive within a server earlier today.

But with trusty SME Server and the Linux software raid process it was relatively painless, albeit that I had the wrong drive out at the first attempt.

The reference at How-to Forge was the one I used and it made it easy to follow.