Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

impout006 error message - was working then didn't

  • 2 Antworten
  • 1 hat dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von JavaMeister

more options

Away from home, sending email okay. Suddenly quit working. Error message titled "Alert" and reading "An error occurred while sending mail: The mail sent an incorrect greeting: impout006 charter.net ESMPT server not available." Charter no help! Outgoing server set to "mobile.charter.net", port 587, Normal password, SSL/TLS. Receiving email okay.

Away from home, sending email okay. Suddenly quit working. Error message titled "Alert" and reading "An error occurred while sending mail: The mail sent an incorrect greeting: impout006 charter.net ESMPT server not available." Charter no help! Outgoing server set to "mobile.charter.net", port 587, Normal password, SSL/TLS. Receiving email okay.

Alle Antworten (2)

more options

I suggest charter DO need to help. No one here can get their mail server "mobile.charter.net t5o stop announcing itself as impout006 charter.net nor can we make it available.

My guess is your encountering some sort of DNS issue because you not using the charter network to access the internet. But I am really only guessing.

more options

Thank you, Matt. It works fine when I am at home. My guess is that there is something about the ISP at my away location that is messing things up. Next time I am there, I am going to check with them, if the problem persists, and I have no reason to think that it won't.