Tag Archive for: El Capitan
How do I enable and disable Roundcube plugins?/0 Comments/in Roundcube installer/by Jeff Johnson
This article covers how to enable and disable plugins, but does not cover how to configure any specific plugins.
IMPORTANT: A misconfigured plugin could cause roundcube to fail. Always backup before making changes.
To see a list of your available plugins
Let’s be friendly and enable: emoticons
Plugins are enabled/disabled in the roundcube configuration file. We’ll use pico to edit the file.
sudo pico /usr/local/topicdesk/roundcube/WebApp/config/config.inc.php
Look for the plugin array, it will look something like this
$config['plugins'] = array('image_paster','html5_notifier','chbox','carddav','managesieve');
To enable show_additional_headers add it to the array, so it looks like this:
$config['plugins'] = array('image_paster','html5_notifier','chbox','carddav','managesieve','emoticons');
Logout and Login to Roundcube and now you have:
To disable plugins
If a plugin causes roundcube to fail or you simply don’t need it – you remove the plugin from the array.
sudo pico /usr/local/topicdesk/roundcube/WebApp/config/config.inc.php
Why do postconf -n and postfix reload produce unexpected output on OS X Server 5?/1 Comment/in FAQs, General and Support, OS X Server Mail Services/by Athanasios Alexandrides
If you’ve been a long-time OS X Server user, especially from the days prior to OS X Server 5, then you’ll find that commands that used to work fine, suddenly produce unexpected output.
may show you Postfix parameters which are completely different from what you would expect them to be.
may show you errors that shouldn’t be there.
The reason for this is quickly found. In recent years, and especially so in OS X Server 5, Apple has been moving server related binaries to:
and server related configuration files to:
Thus, when you call
postconf -n you are actually using
/usr/sbin/postconf -n and displaying the contents of
/etc/postfix/main.cf instead of using
/Applications/Server.app/Contents/ServerRoot/usr/sbin/postconf -n and displaying the contents of
While it makes lots of sense and allows for unbundling OS X Server from the underlying OS (OS X Server 5 works on both, Yosemite and El Capitan) it is a transition which is still not complete and has its inconsistencies. Some commands (e.g. mailq) are still in their old locations due to compatibility issues with older software (sendmail in this case).
postqueue -p instead of
Although it can drive you mad at times, overall, it is a welcome change made for good reasons.
That said, let’s see how we can make sure we use the correct binaries and configuration files.
As mentioned, binaries (applications) for Postfix are now to be found under
/Applications/Server.app/Contents/ServerRoot/. So the first thing we need to do, is to use those binaries, instead of the ones under our main root
There are multiple ways of achieving this.
1. Use the full path to the binary:
Instead of simply typing:
we would need to type:
Not exactly elegant, but it works.
2. Modify the PATH environment variable:
While this requires a little bit of work upfront, it will save you lots of time in the long run.
If you look inside
/private/etc/paths.d/ you will find a file called
com.apple.server. This in turn contains the following two paths:
Unfortunately, paths added inside
paths.d will be added to the end of
$PATH. So if you issue for example postfix reload, you will still use
/usr/sbin/postfix instead of
Note: There are many ways of modifying the PATH environment variable. Choose the one you prefer or use the method outlined below.
In your users home directory (e.g.
/Users/myadminaccount/) create a file called
Inside it, add:
Note: If you already have other custom paths set up, you will need to adapt above instructions to reflect those paths as well.
Save the file, close and re-open your terminal window (or exit and re-connect via SSH) and you should be good to go.
If in doubt, issue:
and it will show you which command is going to be used.
The steps outlined in this article are not only valid for Postfix, but pretty much for any server related binary that has been moved under
- If you are unsure about how to edit a configuration file, have a look at our tutorial on how to edit text files ↩
Setting Logging Levels for Mail Services on OS X Server 5/0 Comments/in FAQs, OS X Server Mail Services, Tutorials/by Athanasios Alexandrides
With OS X Server 5, Apple has further modified logging level and files for mail services. This setup is well thought out for occasional log peeking through Server.app, but can make it a bit cumbersome for troubleshooting since different log levels are written into separate log files, rather than a single one.
The most important logs for a mail server are:
These logs cover the SMTP, IMAP and SPAM Filter parts of mail services.
If you are curious, there are more logs here:
When troubleshooting, most of the time we have to focus on SMTP and SPAM Filters. IMAP, which is provided by Dovecot, tends to give very few issues nowadays (while this wasn’t true in the pre 10.6 era where Cyrus was used).
So let’s focus on SMTP and SPAM Filters.
The SMTP logs are written into
/var/log/mail.log while the SPAM Filter logs we usually need are written into
The amount of information written into these logs depends on the logging level. The ones we care about are typically
Most of the time you want your log levels to be at
info. This gives you plenty of information for troubleshooting the most common issues. When running into real trouble, you might need even more detail which you get by setting the level to
debug. Some object to keeping
info on all the time as they claim that this generates lots of log entries and load on your server. Truth is, unless you are running mail services with hundreds of thousands of messages a day, this will never be an issue. Should you want to reduce the number of entries, you can set the log level to
notice, but will have to compromise on the log detail you get.
Another factor is the time your log remains available before being rotated and archived or deleted. A good default setting is usually 1 day. However, most OS X Server mail servers aren’t so busy that you need to rotate daily, so setting it to 3-7 days gives you more detail to work with in the current log, rather than having to dig out archived logs. This is especially important if you suspect a breach and want to have a quick look at the past 48-72 hours.
Having said that, here is how to set what we discussed above:
sudo serveradmin settings mail:postfix:log_level = "info" sudo serveradmin settings mail:postfix:spam_log_level = “info” sudo serveradmin settings mail:imap:log_level = "info" sudo serveradmin settings mail:postfix:log_rolling_days_enabled = yes sudo serveradmin settings mail:postfix:log_rolling_days = 3
To check your settings, you can for example issue:
sudo serveradmin settings mail:imap:log_level
Besides above log related commands, there are many more parameters that can be viewed or set via the command line. For an overview, issue:
sudo serveradmin settings mail
Be careful when unsure about changing a parameter and always make sure you have a working backup.
Another option is to merge SMTP and SPAM Filter information into one log. This of course comes down to personal preference. I like it, because I can follow the entire flow of an incoming or outgoing e-mail through SMTP and all connected filters, rather then having to peek into two separate log files.
To do so, edit1
and make sure the necessary parameters are set as follows:
$log_level = 3; $DO_SYSLOG = 1; # log via syslogd (preferred) $syslog_facility = 'mail';
From now on, all SPAM Filter log entries will be written into
/var/log/mail.log rather than
/Library/Logs/Mail/amavis.log for easy troubleshooting.
- If you are unsure about how to edit a configuration file, have a look at our tutorial on how to edit text configuration files on OS X Server ↩
Is My Server Running in Performance Mode?/8 Comments/in FAQs, General and Support/by Jeff Johnson
In the earlier days (up to OS X Lion 10.7), Server Admin had an option to “Dedicate system resources for high performance services”.
This option is no longer available in the GUI, but it still exists on the command-line.
NOTE: If you are using OS X 10.11 El Capitan or greater, you will need to disable SIP (System Integrity Protection) first.
Check if your server is running in performance mode with
If you find its NOT, its generally a good idea to enable it as performance mode tunes the system to run as a server.
You can do so by issuing:
serverinfo --setperfmode 1
When done, reboot.