SOGo: Customize Title!

Hey there! The link I had in the original post for this thread includes instructions for how to customize the web UI’s interface for the Logo, Favicon and color theme:
SOGo - mailcow: dockerized documentation

mailcow.github.io

SOGo - mailcow: dockerized documentation

None

If it helps for the color theme, which is the most complicated part of this process, I did come across this post in the community, which helped give me a reference point for customizing the custom-theme.js file with a blue color (note, I had no issues that are mentioned by the user in the post … one thing to remember is dumping your browser’s cache as you make these changes): Customize SOGo theme

mailcow communityDiscussion

Customize SOGo theme

D dennisB

Hi, I managed to change the theme of my SOGo login interface according to https://mailcow.github.io/mailcow-dockerized-docs/u_e-sogo/#change-theme. I decided to go for the “blue” style instead of the green one for testing purposes. Also uploading a custom logo works like a charme. However the

10 7 Mar 5, 2021

Here is my custom-theme.js file using the same blue colored theme (that’s what I needed for our setup):

(function() {
‘use strict’;
angular.module(‘SOGo.Common’)
.config(configure)

configure.$inject = [‘$mdThemingProvider’];
function configure($mdThemingProvider) {
var greyMap = $mdThemingProvider.extendPalette(‘grey’, {
‘200’: ‘F5F5F5’,
‘300’: ‘E5E5E5’,
‘1000’: ‘4C566A’
});
var blueCow = $mdThemingProvider.extendPalette(‘blue’, {
‘600’: ‘E5E5E5’
});
$mdThemingProvider.definePalette(‘frost-grey’, greyMap);
$mdThemingProvider.definePalette(‘blue-cow’, blueCow);
$mdThemingProvider.theme(‘default’)
.primaryPalette(‘blue-cow’, {
‘default’: ‘400’,
‘hue-1’: ‘400’,
‘hue-2’: ‘600’,
‘hue-3’: ‘A700’
})
.accentPalette(‘blue’, {
‘default’: ‘600’,
‘hue-1’: ‘300’,
‘hue-2’: ‘300’,
‘hue-3’: ‘A700’
})
.backgroundPalette(‘frost-grey’);
$mdThemingProvider.generateThemesOnDemand(false);
}
})();

The color scheme is defined by Angular, so you may want to try reading through the 3 links provided in the same Mailcow document. I read these over and over, repeatedly looking at the custom-theme.js file referenced in the post I found, to help increase my understanding of how this works:
AngularJS Material

material.angularjs.org

AngularJS Material

AngularJS Material

material.angularjs.org

AngularJS Material

Color - Style - Material Design

Material Design

Color - Style - Material Design

Regarding Docker, you may want to check out some videos by Network Chuck to help you get comfortable with docker and docker-compose (there’s still so much for me to learn on this topic as well!)

you need to learn Docker RIGHT NOW!! // Docker Containers 101

YouTube

you need to learn Docker RIGHT NOW!! // Docker Containers 101

Create a Docker Container on Linode right now w/ $100 credit: https://bit.ly/nc_linode*Sponsored by Linode➡️Checkout ALL my training at CBT Nuggets: http://b...

Docker networking is CRAZY!! (you NEED to learn it)

YouTube

Docker networking is CRAZY!! (you NEED to learn it)

Don’t leave yourself unprotected, get the best protection by checking out BitDefender Premium Security at the link below.https://bit.ly/BitdefenderNC Today y...

Docker Compose will BLOW your MIND!! (a tutorial)

YouTube

Docker Compose will BLOW your MIND!! (a tutorial)

We don’t live in Docker containers, keep yourself safe with Bitdefender Premium Security: https://bit.ly/BitdefenderNC (59% discount on a 1 year sub)Stop sp...

learning Docker is HARD!! (this makes it easy)

YouTube

learning Docker is HARD!! (this makes it easy)

Start using Docker the RIGHT WAY with Linode: https://ntck.co/linode Sign up using my link and you will get a 100$ credit that is valid for 60 daysSTOP using...

There is a doc here as well if you wish to deploy Portainers alongside Mailcow on the same server (I don’t plan to do that vs. using the agent model to manage it):
Portainer - mailcow: dockerized documentation

docs.mailcow.email

Portainer - mailcow: dockerized documentation

None

Regarding DNS, to maximize delivery you’ll want to do a few things:

1. Make sure your mail server hostname’s “A” record (IPV4) is set up. If your server also has a public IPV6 record, you should setup it’s “AAAA” record as well. The “A” records are what are using via “nslookup hostname.domain.com” to find out its IP.

2. Make sure you have reverse DNS setup. Basically for hostname.domain.com pointing to an IP address, ensure the reverse is also possible, so you can nslookup the IP and get the hostname.

3. Set up your MX record for your email domain. This maps “domain.com” to “hostname.domain.com” so email systems know which server(s) can receive messages for the domain.

Next will be your SPF, DKIM and DMARC records in DNS. I recommend setting up all 3:
https://docs.mailcow.email/prerequisite/prerequisite-dns/#dkim-spf-and-dmarc

4. Set up your SPF record, which lists all the servers authorized to send emails from a particular domain. This ensures others cannot fake your domain:
   https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/
   cloudflare.com

   https://www.cloudflare.com/learning/dns/dns-records/dns-spf-record/

   No preview could be generated for this link
   
   SPF: FAQ/Examples
   open-spf.org

   SPF: FAQ/Examples

   
   
   SPF: SPF Record Syntax
   open-spf.org

   SPF: SPF Record Syntax

   

This the SPF (TXT) record I established. It basically says "check the MX record to validate who is allowed to send email on behalf of my domain, and from anywhere else, mark it as spam (soft-reject):

dig -t txt domain.com +short
“v=spf1 mx ~all”

5. Set up your DKIM record (when you add a domain in Mailcow, it generates a DKIM private/public key. You can use the public key provided to setup your DKIM record. This is also a TXT record but uses dkim._domainkey.domain.com for setting up this record. Email messages sent from your email system are Digital signed with the private DKIM key that only mailcow knows, but can be verified as authentic by other systems using the public DKIM key published via DNS:
   https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/
   cloudflare.com

   https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/

   No preview could be generated for this link

In my example below, “…PUBLIC KEY…” will be a long string of seemingly random letters and numbers:

dig -t txt dkim._domainkey.domain.com +short
“v=DKIM1;k=rsa;t=s;s=email;p=…PUBLIC KEY…”

6. Finally, set up your DMARC record, which can be used for overall reporting and conformance for what to do when another system rejects an email message from you, and for providing reporting/stats back to your system on emails exchanged between domains. This requires you to setup a “DMARC” email inbox to receive the reports. This step is not done by all nor is as important as SPF and DKIM, but I recommend doing so:
   https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/
   cloudflare.com

   https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/

   No preview could be generated for this link

This is mine … I’ve specified DMARC reports to be sent from other systems to dmac@domain.com and indicates any failed emails from the direct domain.com be soft-rejected (marked as spam), but if anyone tries to spoof my domain by faking a sub-domain like sender@important.domain.com then to reject it completely:

dig -t txt _dmarc.domain.com +short
“v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc@domain.com; ruf=mailto:dmarc@domain.com; fo=0:1:d:s; aspf=s; adkim=s;”

Finally, you can use these tools to help verify you do not have an open SMTP relay, and to verify your email server is not on any blacklists:
Network Tools: DNS,IP,Email

MxToolbox

Network Tools: DNS,IP,Email