[exim] Transports in an odd configuration

Página Principal
Apagar esta mensagem
Responder a esta mensagem
Autor: Roger Burton West
Data:  
Para: exim-users
Assunto: [exim] Transports in an odd configuration
This is not an urgent question, because the situation has been resolved.
I'm seeking to increase my understanding rather than looking for a quick
fix.

A few weeks ago, my primary MX died. While I was waiting for it to be
replaced, I inserted custom routers on the secondary MX to skim off
_some_ of the queued mail into other places. Thus, three users (who had
accounts on the secondary MX) got this:

fdo_backup:
debug_print = "R: fdo_backup for $local_part@$domain"
driver = accept
domains = firedrake.org
local_parts = roger:seand:paddy
check_local_user
transport = LOCAL_DELIVERY

(This is a Debian/lenny system; LOCAL_DELIVERY is mail_spool.)

I also had on this system a smartlist installation, with router:

list_director:
driver = accept
group = list
domains = firedrake.org
local_part_suffix = -request
local_part_suffix_optional
local_parts = !.bin:!.etc
require_files = /var/list/${local_part}/rc.init
retry_use_local_part
transport = list_transport
user = list

and transport:

list_transport:
  driver = pipe
  command = "/var/list/.bin/flist \
    ${local_part}${local_part_suffix}"
  current_directory = /var/list
  group = list
  home_directory = /var/list
  user = list



Now for the odd bit. Externally-sourced mail was delivered as
appropriate to the three addresses. However, mail sent through a mailing
list, which should have gone to roger and seand, was only delivered to
roger; seand's mail was apparently missing the fdo_backup router, and
being queued until the primary MX came back on-line.

What did I do wrong?

Roger