Logged In: YES 
user_id=127598

Thank you for your quick response Richard!

> Are you sure there are no
>accesses active on the roundup-server when the email
>delivery is attempted?

To my best understanding, no. I think I can narrow down the
issue: I
start the tracker like so- "roundup-server -l tracker.log -d
tracker.pid -p 8001 it=/home/drewp/trackers/it" and observe
no db/lock
file. Then I go to the web page with the tracker
(http....roundup/it/). I have no relevant cookies, so I see
the issue
list as 'anonymous'. Now, several seconds after loading that
page, I
see db/lock which contains the proper PID of roundup-server. An
incoming email will fail, as I described yesterday.

So, is that lock file behavior correct? An incoming email
bounces with
this error:
  File
"/usr/local/lib/python2.1/site-packages/roundup/backends/locking.py",
line 36, in acquire_lock
    file = open(path, 'w')
IOError: [Errno 13] Permission denied:
'/home/drewp/trackers/it/db/lock'