Stephen, Thanks for your reply. Here is some more information that may help:
- We are running TMDA on a slackware mail server onsite. Our new ISP is authoritative for our domain. The only dns changes that have taken place is our alias for our mx record (mail.domainname) points to the new ip address of the mail server (actually it points to a linksys vpn endpoint and port forwarding is enabled, but you get the idea.) I have apache running on this slackware mail server and I can actually hit the address from inside and outside the network @ http://mail.domainname/cgi-bin/tmda.cgi . It looks like authentication is working because when I enter a bad username/password it tells me. The problem is when I enter a valid username / password it gives me this: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [EMAIL PROTECTED] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Apache/1.3.33 Server at mailhost.wwscusa.com Port 80 I know that tmda is working because I can send a message to it and do a tail -f /etc/mail/maillog and I see the message being queued for delivery. I also can see each user's pending messages in /STORAGE/home/user/.tmda/pending . I have tried to recompile tmda-cgi and I don't think I am answering the interactive questions correctly. Do you have any ideas? Thanks, Rob -----Original Message----- From: Stephen Warren [mailto:[EMAIL PROTECTED] Sent: Monday, February 06, 2006 11:12 AM To: tmda-users@tmda.net Cc: Rob Huffman Subject: Re: MX Record Change Broke My TMDA Rob Huffman wrote: > I just recently changed my ISP. As a result, I needed to change the ip > address on the Alias that pointed to my MX record. Since that change > has taken place, I am unable to login to my web interface for TMDA (ex. > http://mail.domainname/cgi-bin/tmda.cgi ) Is there a setting in the > TMDA configuration somewhere that needs to be changed when the IP > Address of your mx record changes? You need to give a little more information. Specifically, what did you change in your DNS? It's best to give the complete MX record, and any referenced A/CNAME records both before and after the change. (Although I don't think MX is allowed to reference CNAME technically) Also, describe what your mail-flow is. Are you running the TMDA system on a machine you administer, or was your ISP running it for you? What happens when you try and login. Can you connect to the site. Does TMDA-CGI simply reject the login/password? What do the log files say? _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users