Skip to main content

exim all mail catcher

All mail catcher with Exim 4, on Debian 8

We have un bunch of "development" VM that has the feature of sending a mail via a relay, or MTA. 

We usually achieve this by setting the "mail host" setting in the used framework or CMS.

But for development purpose, there is no need to really send the message over the Internet: if the "mail host" catches it all and delivers it to a mailbox, the work is done.

Here is how to setup an Exim 4 on Debian 8 in order to make it catched all mail for all destination and always deliver it to a single local mailbox. That signel local mailbox can then be accessed via IMAP so that the development team can check if the message has been sent by the application.

Configuring with "debconf"

The first stage of configuration is done with debconf

# dpkg-reconfigure exim4-config

Then choose the following answers:

  • Internet site; mail is sent and received directly using SMTP
  • System mail name: (put the FQDN of this machine)
  • IP-addresses to listen on : (leave empty)
  • Other destinations for which mail is accepted:   *
    (Remember we want to catch all destination)
  • Domains to relay mail for: *
    (Remember we want to catch all destination)
  • Machines to relay mail for: 192.168.128.0/23
    (Ajust to your subnet)
  • Keep number of DNS-queries minimal (Dial-on-Demand)? <yes>
    (As far as we wont deliver to the outside world, we dont need to query DNS)
  • The remaining options are up to you

Modify the "deconf'd" configuration

The generated configuration is stored in
/var/lib/exim4/config.autogenerated

We need to copy this to
/etc/exim4/exim4.conf

Then we edit it, and the only line to edit is in the "system_aliases:" router:
-  data = ${lookup{$local_part}lsearch{/etc/aliases}}
+  data = mihamina

This will route all the messages to the "mihamina" Maildir: just install a Dovecot-IMAP and a webmail in order to see the messages.

Note that
  • "mihamina" user must have been created.
  • we dont need to touch the "aliases" file

Comments

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that