Mail access monitor for exim mail server

Due to abusive users, many Internet Service Providers (ISPs) block SMTP port 25. So you may want to set up another port on your web server instead of the default 25.SMTP is the acronym for Simple Mail Transfer Protocol, a protocol used to send emails. More info on the Wikipedia page.We will show you here two ways on how to add another SMTP port in WHM.Method 11.Log into WHM as root2. Navigate to Service Configuration >> Service Manager3. Look for Exim Mail Server (on another port) option. Check the two checkboxes – cPanel will enable and monitor this service. Add the desired port(s) in the right field. The notice states: Useful for providers that block port 25 (multiple comma-delimited ports may be added). 4. Scroll to the bottom of the page and click the Save button. Method 21.Log into WHM as root2. Navigate to Service Configuration >> Exim Configuration Manager3. The Exim configuration page will open. Click on the Advanced Editor top tab.4. Look for daemon_smtp_ports option and add your desired port(s). cPanel notice for this option: This option specifies one or more default SMTP ports on which the Exim daemon listens.5. Scroll to the bottom of the page and click the Save button. Instead of adding another SMTP port, you can instruct users to use Secure SMTP ports – 465 or 587. Usually, these ports are not blocked by IPSs.Don’t forget to add the new port(s) to the allowed ports in your firewall’s configuration.Read more articles

Configure Exim outside of running it in a container (which we are now doing). The beauty of containers is to be able to run them in all sorts of environments, using a known set of libraries and ideally we run as many of them as we need across a fleet of physical servers ….. however, Exim does maintain state, i.e. it’s queue. So let’s take care of that.Step 7: Queue stateThe elephant in the room at this point is, as we all know, email servers (including Exim) are normally stateful. That is, each instance of Exim maintains it’s own state directory in the form of a message queue or spool area. So, each Exim container needs it’s own, persistent, spool area. To do this, we create a Docker volume and bind it into the spool area defined in exim.conf (or as compiled into the binary):Each container needs it’s own spool area, so let’s create one for this instance:$ docker volume create exim-spool-001exim-spool-001This time, when we run our container, we will mount the volume into /var/spool/exim and we will give our instance a name by which we can reference it (i.e. exim-001):$ docker run --mount src=`pwd`/logs/mainlog,target=/var/log/exim4/mainlog,type=bind --mount src=`pwd`/logs/rejectlog,target=/var/log/exim4/rejectlog,type=bind --mount src=`pwd`/logs/paniclog,target=/var/log/exim4/paniclog,type=bind --mount src=`pwd`/exim-blog-post.conf,target=/etc/exim-blog-post.conf,type=bind -v exim-spool-001:/var/spool/exim4 -p 1025:25/tcp --name exim-001 exim-blog-post:0.4$ docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESd76915cf10ff exim-blog-post:0.4 "/usr/sbin/exim -bdf…" 4 seconds ago Up 3 seconds 0.0.0.0:1025->25/tcp exim-001$ docker stop exim-001exim-001Step 8: Mail logsIn a large environment it is typical for mail logs to be sent to a central log server, typically via syslog – which is supported by Exim out of the box. However, one of the basic premises of Docker is that apps log to stderr and stdout, and you can do whatever you want with that with various Docker log drivers. However, Exim will not send it’s

Running Exim in a container is not straightforward, especially as it is not an application built natively to run in a container. Of course, it would be great if Exim was a twelve-factor app, but it isn’t and sometimes you just have to deal with older-style apps. This post was originally posted on the 6th August 2020, today we update it with some new practices and a new operating system.This post deliberately exposes the “building block” development process of creating a Docker image and making it close to production-ready to run in a container. Rather than configure Exim to run in an Atmail specific environment here, we are describing a generic installation – you will definitely need to customise the below for your environment so that it integrates into your broader architecture and runs your desired configuration. I am not going to get into the specifics of optimising your container environment, for example how to allocate appropriate volumes for a mail server, nor am I going to overly explain the Docker commands and will largely use the defaults – that is out of scope of this article. I am simply showing the building blocks of getting a container running in Docker.Note: atmail doesn’t currently ship images that a compatible with our mail server product, but we are exploring. This post is part of that exploration. We are likely to deploy containers as part of our cloud solution long before we make them available in our on-premises products.Step 1: Create the DockerfileWe will base our Exim image on Ubuntu LTS 22.04 (jammy). First, I just want to ensure this is working and running. As we go, we will ensure that each step of the way is working before we add another layer of complexity.Create the following Dockerfile in $HOME/exim-blog-post/Dockerfile:# build file

Be deleted, quarantined, or forwarded to an administrator. Mail Access Monitor for MDaemon - Mail Access Monitor is a simple tool that analyses mail server logs and shows how much traffic is being used by e-mail, who sends and receives most messages, where the messages are being send to and if e-mail abuse takes place in your office. Mail Access Monitor for PostFix - Mail Access Monitor is a simple tool that analyses mail server logs and shows how much traffic is being used by e-mail, who sends and receives most messages, where the messages are being send to and if e-mail abuse takes place in your office. Mail Access Monitor for QMail - Mail Access Monitor is a simple tool that analyses mail server logs and shows how much traffic is being used by e-mail, who sends and receives most messages, where the messages are being send to and if e-mail abuse takes place in your office. Mail Access Monitor for Merak Mail Server - Mail Access Monitor is a simple tool that analyses mail server logs and shows how much traffic is being used by e-mail, who sends and receives most messages, where the messages are being send to and if e-mail abuse takes place in your office. Mail Access Monitor for VisNetic MailServer - Mail Access Monitor is a simple tool that analyses mail server logs and shows how much traffic is being used by e-mail, who sends and receives most messages, where the messages are being

If you are using Zabbix to monitor your infrastructure you might want to receive email alerts from your local domain somewhere on a public internet domain, even if you don’t own a valid registered internet domain name with a mail server which you can configure on your own.This tutorial will briefly discuss how to set up a Zabbix server to send mail reports to a Gmail address by using the SSMTP program, without the need to install and configure any local MTA daemon, such as Postfix, Exim, etc.RequirementsHow to Install Zabbix on RHEL/CentOS and Debian/Ubuntu – Part 1Step 1: Install and Configure SSMTP1. SSMTP is a small software, which does not fulfill any of the functionality of a mail server, but only delivers emails from a local machine to an external email address on a mailhub.To install the SSMTP program alongside with mailutils package that you will use to send mails, issue the following command on your RedHat-based distros and Debian like server:# yum install msmtp mailx [On RHEL/CentOS] $ sudo apt-get install ssmtp mailutils [On Debian/Ubuntu]2. After the packages are installed on the system, configure the SSMTP program to send local emails to your Gmail account by opening the main configuration file for editing with your favorite text editor and root privileges and use the following parameter settings:# vi /etc/msmtprc [On RHEL/CentOS]$ sudo nano /etc/ssmtp/ssmtp.conf [On Debian/Ubuntu]MSMTP settings for GMAIL account.Configuration of /etc/msmtprc#set default values for all following accounts.defaultsauth ontls ontls_trust_file /etc/pki/tls/certs/ca-bundle.crtlogfile ~/.msmtp.log# Gmailaccount gmailhost smtp.gmail.comport 587from [email protected]user [email protected]password gmailpassword# Set a default accountaccount default : gmailSSMTP settings for GMAIL account.Configuration of /etc/ssmtp/ssmtp.conf[email protected]mailhub=smtp.gmail.com:587rewriteDomain=your_local_domainhostname=your_local_FQDNUseTLS=YesUseSTARTTLS=YesAuthUser=Gmail_usernameAuthPass=Gmail_passwordFromLineOverride=YESConfigure Zabbix Email AlertsStep 2: Gmail Tests for Zabbix Email Alerts3. On the next step it’s time to send a locally generated email to a Gmail account by issuing the below command.# echo "Body test email from 'hostname -f' "| mail -s "subject here" [email protected]Gmail Tests4. Normally, Gmail prevents different types of authentications to their servers from your account, so, in case you get the error “mail: cannot send a message: Process exited with non-zero status”, then login to your Gmail account from

Linux distro’s actually have journald at the other end of /dev/log which will then send to syslog. So is there an opportunity there?Not really, well no more than syslog – it pretty much has the same problems as syslog and the same set of inelegant solutions. Let me know if you disagree.Oh, and also most containers do not run systemd so unless you go out of your way to include it, journald isn’t typically available in a container. The proof:/dev/log in a regular Ubuntu 20.04 LTS system:# ls -la /dev/loglrwxrwxrwx 1 root root 28 Oct 5 13:49 /dev/log -> /run/systemd/journal/dev-log…and the same file from inside our exim container:$ docker exec exim-001 ls -la /dev/logls: cannot access '/dev/log': No such file or directoryStep 9: Administer the containerSo, the next logical question is: How do I manage this instance of Exim? You know, get a list of the mail queue, or find out what Exim is doing, etc… Well, Docker has this figured out, you can simply run commands inside a running container like so:First, restart our container that we stopped in the last step:$ docker restart exim-001exim-001Now, run the commands we’d like to run:$ docker exec exim-001 exim -bpc # queue count0$ docker exec exim-001 exim -bp # print the queue, not very exciting with 0 messages$ docker exec exim-001 exim -bt [email protected]R: nonlocal for [email protected][email protected] is undeliverable: Mailing to remote domains not supportedSo, all very straight forward, and exactly what you are used to.The wrap upWell, there we go, we have Exim running in a Docker container. The key limitations identified are:Logging to syslog is a bit of a workaround – it would be better to have an option to log to stdout/stderr.Let us know here if you have any questions or comments.Find this useful?We’re taking ideas