Blocking or blacklisting entire Top Level Domains (TLDs) used for hostname in email server setup can be a very effective solution to stop low reputation mail servers delivering mails to your email system(s).
As most email providers use common TLDs like .net, .com or .de in their email setup, you can selectively block new or low reputation TLDs and this way reducing a lot of unwanted emails.
If you are looking for a tutorial to blocking/blacklisting sender (users/clients) using specific TLD, this tutorial is the right one for you: Howto Block Entire TLDs in Postfix for Senders.
Blocking or blacklisting entire Top Level Domains (TLDs) in Postfix mail server may have a big impact to reduce spam, phishing, and other unwanted emails. Dependent on the use case of your systems it is a valid and effective solution. The only drawback is, to monitor your email traffic and check, whether valid emails from blocked TLDs are sent to your systems. Blocking a whole TLD is mostly a temporary thing, as the bad guys move on if the domains on a specific TLD are not usable for their cases.
Sending a test email from shell using command line, send mails in shell script is a common task for an email admin. Mails were and still are used to inform admins regarding changes, warnings and problems.
Dependent on the task you want to achieve, some content should be in the body of an email or attached as file. Let’s figure out, how to do it using Linux or Unix command line like bash or zsh.
You have built your local IP blacklist for Postfix. Invested time to analyze server logs or Rspamd history to blacklist single hosts, IP addresses, or even whole networks. But how well is it working compared to public blacklists you are using? Time to see the results and get some visual insights through Munin Monitoring System.
Setup your blacklist for Munin First of all, you have to decide how to visualize the data in your graph.
By running a Postfix mail server, you need to know some commands to manage Postfix mail queues. With this knowledge, you can manage queues and write simple scripts to accomplish larger tasks.
First, I will list the most relevant commands you need for your daily business. Then we will build up real-life examples to understand how these commands work, how to use them, and when they can harm.
Postfix Mail Queue Commands Postfix has several commands to manage the queues.
You know those same hosts, providers, or whole networks, who get through your spam filter and spam your users with the same content over and over again. By building up your blacklist in Postfix, you can stop them from bothering you and your users. We will explain how local blacklists work in Postfix and how to use them with whitelists to have better control and reduce errors.
Check before you blacklist Blocking other hosts must be a well-thought decision because blocking single hosts, IP addresses, or even whole networks will stop all delivery attempts to your mail servers.
If you use any blacklists for email services, whitelisting important Hosts, single IP Addresses, and even whole networks is an essential task. By whitelisting valuables email services to your users or even customers, you as admin won’t reject important email communication.
Blacklisting in Postfix If you use any blacklist service or has your blacklist in your Postfix setup, you will probably find similar logs:
root@server $ grep "blocked using" /var/log/mail.log Dec 17 4:07:18 server postfix/smtpd[21213]: NOQUEUE: reject: RCPT from unknown[1.
Monitoring email queues on your favorite email server is an essential task of an email admin, as rising queues are often an indication of problems. First, you need to understand how queues work, manage them, and get emails enqueued. Then build a shell script to monitor them. In the last step, you will learn how to get smartphone push notifications by sending emails to a third-party push service.
Queue Basics Sending and receiving emails is by default done asynchronously.
One of the most critical parts of MailMum is to provide DNS service, which handles IP blacklisting for our customers. They are the primary service our customer’s mail servers are using.
As the DNS flag day 2020 directed to operational and security problems in DNS caused by Internet Protocol packet fragmentation, we’ve tested all our DNS services to align these rules.
Why you should test too? DNS is a distributed system and one of the most critical parts of networks.
Providing email services to your customers or even your own company is an import part of communication. Also, it is important to brand your service and this way also adds some additional trust for your users. Roundcube Support pleases admins to customize their installation, so the people don’t contact Roundcube project for support.
Select the right skin Selecting the right skin for your users is a hard task. Even if the webmail services you provide, are only for one company.
Certificates today are like DNS - they must work, because most of the systems expect them to be there and they must be valid. Especially Google changed for many services to contact with SSL/TLS enabled by default.
Renewing outdated certificates Sometimes problems arise and you need to check whether certbot (of Let’s Encrypt) or cron is still working. Maybe you simply want to check, whether your certificates are all renewed, you can simply run:
A name, domain, logo, and a draft website - this is the way MailMum was born out of an internal project.
From a necessity to this service MailMum was born out of a need to face problems with unwanted emails called spam or junk. As filters like Spamassassin were good, but spammers are human, their job is to figure out how to bypass them. They will try and will find ways to reach your inbox.