Here is another thing I just found out. I decided I'd point my computer to use my NS as the DNS and then run a portable SMTP on my computer to send through it and log what happens. The following is the error from this one. Interestingly, it mentioned postini first and then psmtp in the error. This is all going from the first MX record which is pointing to "quantumtechnology.com.au.s8a1.psmtp.com", the first MX record in the original DNS.
Attempting to connect to: mail.quantumtechnology.com.au sucessful o:HELO SMarTPost i:250 Postini says hello back o:MAIL FROM: <[EMAIL PROTECTED]> i:250 Ok o:RCPT TO: <[EMAIL PROTECTED]> i:451 Can't connect to quantumtechnology.com.au - psmtp >From this I draw another question that I want to find the answer to. If this portable SMTP can send HELO,etc to the mail server, why can't I telnet and do the same? You just get Request Timed Out when you ping it and you get host not found when you telnet it. Is it so closed off that it only allows port 25? -Seth >>> Kevin <[EMAIL PROTECTED]> 21/07/2007 8:23 pm >>> Seth Mayo wrote: > This isn't about ASSP but when I set up ASSP a month ago, people on > here helped a lot with my configuration and mail server. > > Here I am, running into yet another problem - this time on a new > server though. > > Recently I bought a virtual dedicated server from GoDaddy. It was in > order to host one of my clients websites. The client had experienced > problems with their current host and wanted to switch to use me. > However previously I had used shared hosting accounts for my client > and I've always wanted to consolidate them into a single server that > I manage. So I thought I'd give it a go. Hmm can't say I've heard anything good about godaddy hosting. Your issue is most likely caused by postini, my advice is to LEAVE the MX records alone and just change the A record for the website to your servers ip. If you absolutely insist on hosting their DNS yourself I would then advise you to simply duplicate the MX records as they are "quantumtechnology.com.au.s8a2.psmtp.com" and not change them to your own names. I do find it interesting that the error came from "64.18.3.101" which does not match any of your MX records. Did you ask postini why you were getting that error? Kevin P.S. - PLEASE PLEASE use that huge key on your keyboard labeled "Enter" it makes those loooooooong lines not so long. P.P.S - The MX record order term is "Preference" not "Priority", though if thats the term godaddy uses....I'm not surprised they got it wrong :) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
