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

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&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "