Exchange log Clear (Fake Backup)

Open Command Prompt as Administrator

Diskshadow
Add volume d: (optional, add one line for each additional drive to include) 
Begin Backup
Create
End Backup

At this step you should notice the following events in the application log indicating that the backup was indeed successful and logs will now be deleted.

Setup nginx Reverse Proxy

install nginx
ubuntu:

sudo apt-get update
sudo apt-get install nginx

Centos: yum install ngix

Edit the config

Ubuntu: sudo nano /etc/nginx/sites-enabled/default
You might need to delete the config file contents and start fresh


server {
    listen 80;
    return 301 https://$host$request_uri;
}

server {

    listen 443;
    server_name blabla.domain.com;

    ssl_certificate           /etc/nginx/cert.crt;
    ssl_certificate_key       /etc/nginx/cert.key;

    ssl on;
    ssl_session_cache  builtin:1000  shared:SSL:10m;
    ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
    ssl_prefer_server_ciphers on;

    access_log            /var/log/nginx/jenkins.access.log;

    location / {

      proxy_set_header        Host $host;
      proxy_set_header        X-Real-IP $remote_addr;
      proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header        X-Forwarded-Proto $scheme;

      # Fix the β€œIt appears that your reverse proxy set up is broken" error.
      proxy_pass          http://localhost:8080;
      proxy_read_timeout  90;

      proxy_redirect      http://localhost:8080 https://blabla.domain.com;
    }
  }

Setup JIRA with Reverse Proxy with SSL on backend

Its really simple, but Atlassian make it sound more complicated then it needs to be.

First thing you want to make the Tomcat process that Jira uses to only run on a self signed SSl cert, so all communication is encrypted.

Run this as root
/opt/atlassian/jira/jre/bin/keytool  -genkey -alias tomcat -keyalg RSA -validity 1095
When asked, set the password to “changeit” without quotes

This will make a .keystore file in root’s home directory.
Move it to where jira can get to it easily.
mv /root/.keystore /opt/atlassian/jira/

make sure Jira is stopped
Now its time to Exit the server.xml
nano /opt/atlassian/jira/conf/server.xml

Find the original port 8080 connector section and commend it out by surrounding it in
<!--   -->

Create a New Connector


            <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
              maxHttpHeaderSize="8192" SSLEnabled="true"
              maxThreads="150" minSpareThreads="25"
              enableLookups="false" disableUploadTimeout="true"
              acceptCount="100" scheme="https" secure="true"
              proxyName="jira.domain.com" proxyPort="443"
              clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true"
              keystoreFile="/opt/atlassian/jira/.keystore"/>

Change your proxyName value to what it would be on your front end. Jira needs to know this so when it serves the page up it has correct links.

Start Jira, make sure there are no errors

Check your server on https://ipaddress:8443 and make sure it hosts the page correctly.
Then you can set your IIS or Apache Proxy to point to https://ipaddress:8443 and you can then serve as needed

Sharepoint Incoming Email

Start here:
https://technet.microsoft.com/en-us/library/cc287879(v=office.14).aspx

Tips:
1. Check that the document library and contact is set to allow from all senders (network scanners were not regarded as authenticated users)
2. Check the size limits on the SharePoint send connector (Exchange -> Hub Transport -> Send Connectors -> Properties -> Maximum message size (KB))
3. Check the size limits on SMTP receiver on SharePoint (IIS 6 Mgr -> Properties on SMTP Virtual Server -> Messages tab -> Limit message size, Limit session size)
4. Turn off SharePoint reading RTF documents from Exchange (Exchange -> Hub Transport -> Remote Domains -> Format of original message sent as attachment to journal report: -> Exchange rich-text format -> Never use)
5. Check for potential mail routing problems (Exchange -> Hub Transport -> Accepted Domains -> Add domain for INTERNAL RELAY) – we noticed a couple of times the scanned mail tried to go external through our mail gateway – this was the last 1% of our problems.

Tips from: http://www.heyweb.net/2011/02/diagnosing-problems-with-sharepoint-incoming-email/