tmda-inject attempting to operate as root?

"Mark J. Nernberg" <[email protected]>
Newsgroups gmane.mail.spam.tmda.user
Organization OneNet Consulting
Message-ID <[email protected]>
regarding my previous post, I turned on debugging output and got:

 

00_001A_01C763DE.F1090C20--\r\n'

Error: failure delivering message to command
"['/usr/local/tmda/bin/tmda-inject', '-c', '/home/ralph/.tmda/config',
'[email protected]']" (command "['/usr/local/tmda/bin/tmda-inject',
'-c', '/home/ralph/.tmda/config', '[email protected]']" exited 1
(Traceback (most recent call last):

  File "/usr/local/tmda/bin/tmda-inject", line 461, in ?

    main()

  File "/usr/local/tmda/bin/tmda-inject", line 452, in main

    log_msg)

  File "/usr/local/tmda/bin/tmda-inject", line 282, in inject_message

    action_msg = log_msg)

  File "./TMDA/MessageLogger.py", line 45, in __init__

IOError: [Errno 2] No such file or directory:
'/usr/home/root/.tmda/logs/outgoing'))

process_message raised an exception:

Traceback (most recent call last):

  File "/usr/local/tmda/bin/tmda-ofmipd", line 796, in found_terminator

    self.__auth_username)

  File "/usr/local/tmda/bin/tmda-ofmipd", line 1187, in process_message

    raise IOError, 'tmda-inject failed!'

IOError: tmda-inject failed!

error: uncaptured python exception, closing channel <__main__.SMTPChannel
connected 68.162.180.225:50923 at 0x828416c> (exceptions.IOError:tmda-inject
failed! [/usr/local/lib/python2.4/asyncore.py|read|69]
[/usr/local/lib/python2.4/asyncore.py|handle_read_event|391]
[/usr/local/lib/python2.4/asynchat.py|handle_read|137]
[/usr/local/tmda/bin/tmda-ofmipd|found_terminator|796]
[/usr/local/tmda/bin/tmda-ofmipd|process_message|1187])

 

Why is it looking for ROOT'S logs?

 

Among other things:  I have no logs set in the /etc/tmdarc (don't need all
the garbage).  And, I am sending the message us user "ralph", thus there
should be no attempt to look for anything in the root user's directory.

 

Any clue, guys?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.