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
