KY wrote: > What it means is when you press "release" button in TMDA-CGI, the > message is being moved to the very bottom of the screen under the > list of pending e-mails and the following message: > > Note: Marked messages are being processed by the mail server. > They will be removed from the pending list when relea ...
This is due to the way CGI applications work. The request to 'release' a message is executed, and there is a good chance that the HTML page will be generated before the message is actually released from the pending queue. To show this, we mark any messages that have been 'released' but not yet actually removed from the pending queue at the moment of HTML generation so there is indication that something is happening. We call this the "in process" state. > What I have figured out is if I just reload pending list then this > message continue to stay, but if I relogin then it goes away, but the > message that is supposed to be released comes back to the "Pending" > list and is not forwarded to my Inbox. Yes. This "in process" state is saved in your session, so it will exist until any of the following happen: - You logout - Your session expires - The message is actually handled by TMDA and removed from the pending queue Since the message you whitelist is receiving this "in process" state, I believe it's safe to assume TMDAcgi thinks it's doing the right thing, and so I would think that your problem is actually something to do with the way TMDA is configured. > What is the way to debug what happens when TMDA tries to use sendmail > to forward released e-mail? Can I see the error message if it does > not work? > > my .tmda/logs/tmda.debug is always empty. The debug log is only used if TMDA itself suffers a more fatal error, which apparently is not happening in your case. You should also take a close look at your INCOMING log. The way TMDA actually performs a release of a message is: - It adds a special magic header to the message to mark it as "okay to go through" - It submits the message with this new header back to your MTA. - Your MTA sends it to you again, and the message gets sent to TMDA - TMDA sees this magic header that it added previously and allows deleviry to continue, so your MTA delivers it to your inbox. When this happens, you should see the following action in your INCOMING log from TMDA: Actn: OK good_confirm_done_cookie This means the message should be on its way to your inbox. I would recommend you start: tail -f /home/vpopmail/domains/domain.com/user/.tmda/logs/tmda.in And also watch your MTA's log (usually among many other messages in /var/log/messages, but this depends on what MTA you're using and how you have it set up). Then try releasing a message via TMDAcgi. You should see: The MTA sending a message, and delivering that message to TMDA. Then you should see the corresponding entry in TMDA's INCOMING log. Hopefully something in there will help you find out what's going wrong with your setup. -- Jim Ramsay "Me fail English? That's unpossible!"
signature.asc
Description: PGP signature
_____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
