About mail server migration

I'm still not seeing any mail coming in. Not through my email client (Evolution on Ubuntu) or through my Droid, or through webmail.
 
fortress said:
Sorry, didn't realize it might be domain specific. I'll go update ticket with domain details.
Click to expand...
Most issues we are seeing here are domain specific DNS matters, not serverwise impact, EXCEPT web mail which is having some issues clogging its pipes making timeouts then to occur.
 
Have verified with clients that DNS is properly resolving to 173.0.129.9. DNS is not the
issue in this case.

E-mail forwarding is also failing. Client has an e-mail forward specified
in control panel, and that forwarding address also does not receive e-mail.

Webmail is also down with Error 502 - Bad Gateway.

If this was just a DNS propagation problem wouldn't e-mail forwarding still work?
 
I have entered several tickets and received ZERO response - I don't even have ticket #s to reference. One of my client sites is able to email internally, but not to anyone off their domain. They are also not receiving any e-mail.

What is the IP address for mail4 supposed to be at this point?
 
Ditto to everything that JoeS and Fortress have said. I was on a Live Chat earlier this morning, but quit after the rep stopped communicating for 45 minutes.

Still no email coming in even though I sent myself at least a half-dozen messages from accounts not connected with JodoHost. Internal mail seems to be coming through.
 
ok, mail4 has mails stuck in queue at this point, and being checked.

BTW we are replying to tickets, sonata has ticket replies for example. If you don't have a ticket Id there may be a mismatch on hsphere and the email address used (that is a known issue)
 
JoeS. said:
Thanks - I've never had a problem getting the ticket replies, until today.

Email.....
Click to expand...
If you are on mail4, you may be having delays hitting the queue making it delayed getting to us as well.

We are aware and working on that matter.
 
Stephen said:
We are working on it, and it isn't every domain it seems ones using gw-mail4 are going wrong, not all use that, and it is DNS matter, not actual mail server issue.
Click to expand...

Steve, this is the exact problem my client is having. Here is what I sent to support:

His mail server is mail.softechsystems.com

Here are some DNS research I have done:

For his main domain:
Searching for softechsystems.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 12 ms
Searching for softechsystems.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 173 ms
Searching for softechsystems.com. A record at ns4.starcityhosting.net. [173.0.138.5] ...took 131 ms

A record found: 64.187.101.31
Domain Type TTL Answer
softechsystems.com. NS 172800 ns3.starcityhosting.net.
softechsystems.com. NS 172800 ns4.starcityhosting.net.
softechsystems.com. A 86400 64.187.101.31

This is for his mx record:
Searching for softechsystems.com. MX record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 12 ms
Searching for softechsystems.com. MX record at m.gtld-servers.net. [192.55.83.30] ...took 149 ms
Searching for softechsystems.com. MX record at ns4.starcityhosting.net. [173.0.138.5] ...took 130 ms

MX record found: 10 gw-mail4.starcityhosting.net.
Domain Type TTL Answer
softechsystems.com. NS 172800 ns3.starcityhosting.net.
softechsystems.com. NS 172800 ns4.starcityhosting.net.
softechsystems.com. MX 86400 10 gw-mail4.starcityhosting.net.

I see his MX record shows gw-mail4.starcityhosting.net. When I resolve the A record for this I get:
Searching for gw-mail4.starcityhosting.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 12 ms
Searching for gw-mail4.starcityhosting.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 12 ms
Searching for gw-mail4.starcityhosting.net. A record at ns1.starcityhosting.net. [173.0.137.4] ...took 131 ms

A record found: 204.10.107.121
Domain Type TTL Answer
gw-mail4.starcityhosting.net. A 86400 204.10.107.121

Now the 204.10.107.121 is NOT what I get when I resolve mail.softechsystems.com. If I ping mail.softechsystems.com I am getting ip 173.0.129.9.

Not sure what is going on.
Click to expand...

The support ticket is SUW-41286-858.

Thanks
 
Any updates - it's now been 12+ hours for multiple mail 4 customers. changing to the ip address makes no difference -- the messages are not getting delivered to the mail server.
 
webconnect said:
Any updates - it's now been 12+ hours for multiple mail 4 customers. changing to the ip address makes no difference -- the messages are not getting delivered to the mail server.
Click to expand...
There are just over 3000 messages in queue to deliver but not going, and that is being worked on.
 
Stephen,

If you get a chance can you look at my reply just above and let me know if you see a problem in the DNS. I've got to head out, but will be back in about 45 minutes.

Thanks,

Greg
 
gsaunders said:
Stephen,

If you get a chance can you look at my reply just above and let me know if you see a problem in the DNS. I've got to head out, but will be back in about 45 minutes.

Thanks,

Greg
Click to expand...

there is an issue in the dns, but it should not be an issue, as it should work on the old still as well.
 
I haven't seen any updates on this. Will mail service be back up today? I've got clients yelling for email access. Are here any workarounds where we can use IMAP server to access even old emails?
 
All the test messages I sent today have started bouncing back to me with errors like the example below:

=======

Delivered-To: [email protected]
Received: by 10.151.6.3 with SMTP id j3cs221825ybi;
Fri, 8 Jul 2011 19:18:54 -0700 (PDT)
Received: by 10.150.49.18 with SMTP id w18mr2444563ybw.238.1310177934017;
Fri, 08 Jul 2011 19:18:54 -0700 (PDT)
MIME-Version: 1.0
Return-Path: <>
Received: by 10.150.49.18 with SMTP id w18mr3649861ybw.238; Fri, 08 Jul 2011 19:18:54 -0700 (PDT)
From: Mail Delivery Subsystem <[email protected]>
To: [email protected]
X-Failed-Recipients: [email protected]
Subject: Delivery Status Notification (Failure)
Message-ID: <[email protected]>
Date: Sat, 09 Jul 2011 02:18:54 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Delivery to the following recipient failed permanently:

[email protected]

Technical details of permanent failure:=20
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 MTA inaccessible for too long for domain:sterlingquarterhorses.com - psmtp (state 14).

----- Original message -----

Received: by 10.150.49.18 with SMTP id w18mr2444559ybw.238.1310177933212; Fri, 08 Jul 2011 19:18:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.6.3 with HTTP; Fri, 8 Jul 2011 19:18:33 -0700 (PDT)
From: David Finster <[email protected]>
Date: Fri, 8 Jul 2011 21:18:33 -0500
Message-ID: <CA+e+KtmquqVCU4SRQsHtkgwXfrQcnj12vbYzHEYqEG5u5Xz+Aw@mail.gmail.com>
Subject: Testing
To: Office <[email protected]>
Content-Type: multipart/alternative; boundary=3D000e0cd6acb64d3d7a04a7999217

I've been told that e-mail is now working. Can you reply and let me know if
you receive this?
 
Still no access to webmail (which is what my clients use) and unable to get IMAP set up. I read Sachin's post about updating MX, but my client is on mail11 and DNS looks correct.
 
You must log in or register to reply here.
Back
Top