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

vmware net_device trans_start

VMWare Workstation 12 and Kernel 4.7 When recompiling vmware kernel modules on a kernel 4.7, I get this error:

/tmp/modconfig-xrrZGZ/vmnet-only/netif.c:468:7: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?     dev->trans_start = jiffies;
This seems to be an already encountered problem: http://rglinuxtech.com/?p=1746http://ferenc.homelinux.com/?p=356 I choosed to replace the line, instead of deleting it.

- dev->trans_start = jiffies; + netif_trans_update(dev); I also noted that I had to re-tar the modified sources instead of leaving them untared, because the compilation process only takes the archives. 
On precedent editions of these files, I just left the modified folders "vmnet-only/" and "vmmon-only/" expanded without the need to re-tar them.


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 selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…

vmware workstation 12 unable to load libvmwareui.so

Using VMWare Workstation on ArchLinux, it suddenly refused to launch.
when inspecting the logs, which BTW are in /tmp/vmware-<id>, I see:

2015-12-11T17:41:54.442+03:00| appLoader| I125: Log for appLoader pid=1727 version=12.0.1 build=build-3160714 option=Release
2015-12-11T17:41:54.442+03:00| appLoader| I125: The process is 64-bit.
2015-12-11T17:41:54.442+03:00| appLoader| I125: Host codepage=UTF-8 encoding=UTF-8
2015-12-11T17:41:54.442+03:00| appLoader| I125: Host is unknown
2015-12-11T17:41:54.448+03:00| appLoader| W115: HostinfoReadDistroFile: Cannot work with empty file.
2015-12-11T17:41:54.448+03:00| appLoader| W115: HostinfoOSData: Error: no distro file found
2015-12-11T17:41:54.448+03:00| appLoader| I125: Invocation: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware-modconfig --appname=VMware Workstation --icon=vmware-workstation"
2015-12-11T17:41:54.448+03:00| appLoader| I125: Calling: "/usr/lib/vmware/bin/vmware-modconfig --launcher=/usr/bin/vmware…