Package: exim4-config
Version: 4.67-8
Severity: important

Hello,
it is me again, finding brokenness rather late. :-(

I have recently taken a shot at using 250_exim4-config_lowuid hovever
it currently seems to be misplaced in the order of things since it is
called before evaluating /etc/aliases, which makes it impossible to
selectively redirect system-userws somewhere else:

m26s25:~# tail -n1 /etc/aliases
www-data: ametzler
m26s25:~# swaks --pipe "exim -bh 70.103.162.31" \
   -f [EMAIL PROTECTED] -t [EMAIL PROTECTED] -q rcpt
[...]
** 550 no mail to system accounts

It is impossible to use exim4 -bt for testing the lowuid router since
it requires a remote address, but it stillshows where things go wrong:
m26s25:~# exim4 -bt [EMAIL PROTECTED]
R: lowuid_aliases for [EMAIL PROTECTED] (UID 33)
R: system_aliases for [EMAIL PROTECTED]
[...]

lowuid greps the id and rejects it, even before system_aliases sees
it.

This could easily be fixed by moving the router to a later point.

The current order causes another kind of breakage that is worse. The
router breaks our default /etc/aliases:
root: ametzler
abuse: root

m26s25:~# exim4 -bt [EMAIL PROTECTED]
R: system_aliases for [EMAIL PROTECTED]
R: lowuid_aliases for [EMAIL PROTECTED] (UID 0)
R: system_aliases for [EMAIL PROTECTED]
R: lowuid_aliases for [EMAIL PROTECTED] (UID 1000)
R: system_aliases for [EMAIL PROTECTED]
R: userforward for [EMAIL PROTECTED]
R: procmail for [EMAIL PROTECTED]
R: maildrop for [EMAIL PROTECTED]
R: local_user for [EMAIL PROTECTED]
[EMAIL PROTECTED]
   <-- [EMAIL PROTECTED]
   <-- [EMAIL PROTECTED]
 outer = local_user, transport = maildir_home
m26s25:~# swaks --pipe "exim -bh 70.103.162.31" \
 -f [EMAIL PROTECTED] -t [EMAIL PROTECTED] \
 -q rcpt 2>&1 | grep -E 'R: |550'
>>> R: dnslookup for [EMAIL PROTECTED]
>>> R: system_aliases for [EMAIL PROTECTED]
>>> R: lowuid_aliases for [EMAIL PROTECTED] (UID 0)
<** 550 no mail to system accounts

No more time for debugging right now, I just wanted to file it.
cu andreas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to