[Exim] Still having problems with incoming mail being frozen…

Top Page
Delete this message
Reply to this message
Author: Cory Daehn
Date:  
To: exim-users
Subject: [Exim] Still having problems with incoming mail being frozen....
Every incoming message gets a log entry something like this:

+++ 17L7uE-0001jk-00 not completed +++
2002-06-20 14:47:46 17L7uE-0001jk-00 <= newsletterbot@???
H=vader.labnet.com (vader) [205.238.148.11] P=smtp S=1176
2002-06-20 14:47:46 17L7uE-0001jk-00 Unable to get root to set uid 60003
and gid 12 for local delivery to patricia: uid=8 euid=8
2002-06-20 14:47:46 17L7uE-0001jk-00 failed to read delivery status for
patricia@??? from delivery subprocess
2002-06-20 14:47:46 17L7uE-0001jk-00 appendfile transport process
returned non-zero status 0x0100: exit code 1
2002-06-20 14:47:46 17L7uE-0001jk-00 == patricia@???
T=virtual_local_delivery defer (-1)
2002-06-20 14:47:46 17L7uE-0001jk-00 Frozen
2002-06-20 14:49:29 17L7uE-0001jk-00 Message is frozen


For some reason, exim (or another program) keeps changing itself to
102711 on it's access flags. I originally had a crontab entry set up to
run a script
that checked (every 5 minutes) to ensure it was 106755 ... But it seems
silly to have to run such a script all the time.

in order for exim to change it's UID for every incoming message, do I
need to add *ALL* my users as trusted users or something?

Right now it reads as follows:

trusted_users = mail:root:majordomo

Funny thing is, these access flags don't affect the problem... it still
appears.