su - vmail -c "/usr/bin/tmda-ofmipd -D \
-A '/usr/local/sbin/courierpasswd -s imap --stdin /bin/true' \
-c /home/vmail"
Here are the two run scripts that I used when testing with supervise.
exec su - vmail -c "/usr/bin/tmda-ofmipd \
-A '/usr/local/sbin/courierpasswd -s imap --stdin /bin/true' \
-c /home/vmail"
and
exec fghack su - vmail -c "/usr/bin/tmda-ofmipd -D \
-A '/usr/local/sbin/courierpasswd -s imap --stdin /bin/true' \
-c /home/vmail"
When I first tried using tmda-ofmipd, I tried using the -u option but it wasn't working for me. I would get a python exception when I tried to send mail. Here is the error.
error: uncaptured python exception, closing channel <__main__.SMTPChannel connected 192.168.1.10:4366 at 0x8105c34> (exceptions.KeyError:getpwnam(): name not found [/usr/lib/python2.2/asyncore.py|poll|94] [/usr/lib/python2.2/asyncore.py|handle_read_event|391] [/usr/lib/python2.2/asynchat.py|handle_read|130] [/usr/bin/tmda-ofmipd|found_terminator|654] [/usr/bin/tmda-ofmipd|process_message|922] [/usr/lib/python2.2/site-packages/TMDA/Util.py|getgid|85])
Jason suggested that I not start tmda-ofmipd as root to get around this which is why I'm using the su command in my scripts above.
I'm using virtual mail accounts with vmail as the controlling system account. All mailboxes and TMDA files are in vmail's home directory and are owned by vmail. Could that be what is complicating my life?
Andrew
Drew Raines wrote:
Andrew wrote:Neither worked. In the first case, supervise began to spin as soon as I started it. Tmda-ofmipd would immediately die for some reason and supervise would start a new process. In the second case, supervise could not successfully start tmda-ofmipd at all.Why don't you post your run scripts so we can at least try and help you? -Drew _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
