Outlook 2016 Error – A required action was not successful because of an unspecified error

When trying to digitally sign an email message in Outlook 2016 for Windows running in Windows 10 you may get this error:

Error - A required action was not successful because of an unspecified error
“A required action was not successful because of an unspecified error”

Encrypting emails works fine, it is only when you try to JUST sign an email you get this error. This error appears to only occur with Outlook x64 (64-bit). When you search the internet on the errorĀ “A required action was not successful because of an unspecified error” in relation to Outlook for Windows the most common solution you come across is to run the command “sfc /scannow” in an elevated command prompt. This didn’t work for me when I tried it on Windows 10 Enterprise (Current Branch) with Outlook 2016 for Windows. The solution that worked for me was in this forum post. The solution in that post was to enable the email security option “Request S/MIME receipt for all S/MIME signed messages”. Once I did that I was able to sign emails successfully without getting any errors. Sending emails to non-exchange email users with this option enabled doesn’t appear to have any adverse effects.

How to Clear the Password History in Linux

In Red Hat Enterprise Linux 7 (RHEL 7) the password history is stored in the file /etc/security/opasswd. You can only edit this file while logged in as the root user. You can either selectively delete old passwords from the file or you can clear everything out of the file with the command:

echo “” > /etc/security/opasswd

How to Configure Splunk to use a Web Proxy Server

A Splunk server I installed was configured such that it could only communicate with hosts within the corporate network so it did not have direct internet access. This posed a problem when trying to use the “Browse Splunkbase” option in the Splunk administrator web interface. I also could not use the “iplocation” data-processing command.

This was the suggestion I got from Splunk Support which didn’t work for me for some reason. I am including it here for reference for someone where this solution may work for them:

You can set the environment variable HTTP_PROXY in the session shell.
You can set it in your /etc/bashrc or /etc/profile.

# Proxy Settings

I also found something in the forums:

The Splunk install I was running was version 3.4.9 which was on a CentOS 5 server. The Splunk installation was configured to autostart on boot. I ended up getting this to work by editing the /etc/init.d/splunk startup script file by adding the following to it:

# Proxy settings

Change “proxy.domain.com:8080” to be the proxy server address and port for the proxy server that you want to use. So with the above lines added to my /etc/init.d/splunk file, the top portion of the file looked like this:

# /etc/init.d/splunk
# init script for Splunk.
# generated by 'splunk enable boot-start'.
# chkconfig: 2345 90 60
# description: Splunk indexer service
# Proxy settings

I put the setting into effect by restarting my Splunk service with the command: /sbin/service splunk restart

Splunk Logo

How to Get Trixbox Working Behind a NAT Firewall

trixbox is a line of Asterisk-based IP-PBX products designed to meet the needs of companies from 2 to 500 employees. trixbox is available in a free open source Community Edition. If you are experimenting with trixbox at home, then you are probably in the situation where you have trixbox running on your home network which is behind a Firewall that uses NAT. Here is how to get your trixbox intall communicating outside of your home network:

  1. Be sure the LAN/Private address is statically assigned to the Trixbox server.
  2. Forward the following ports on your firewall to your Trixbox server IP:
    • UDP Port 5060 is for SIP communication.
    • UDP Port 5060-5082 range, SIP communications.
    • TCP Port 5060 is for SIP but thought to be rarely used.
    • UDP Port 10000 – 20000 is for RTP – the media stream, voice/video channel.
  3. You must also edit the sip_nat.conf file. Go to Trixbox home page, then select administrator mode. Select from PBX -> Config File Editor, click on sip_nat.conf and insert the following lines:
    • If you have a static external IP address:
      • Externip = your_external_ip_address
      • localnet = internal.network.address_of_your machine/
    • If you have a dynanic IP external IP address, use a dynamic IP address hosting service like DynDNS.org:
      • externhost = home.mydomain.com
      • externrefresh = 5 (which means lookup hostname every 5 minutes to refresh ip adress)
      • localnet = internal.network.address_of_your machine/

Then click on update and then “Re-Read Configs”. Or just restart the Trixbox machine.