How to properly diagnose and fix a mail problem? Print

  • 0

Several different network protocols are involved in the operation of electronic mail (hereinafter: mail, E-Mail).
To send letters, the SMTP (Simple Mail Transfer Protocol) protocol is used.
To receive mail, the POP3 (Post Office Protocol version 3) protocol and, less commonly, the IMAP (Internet Message Access Protocol) protocol are usually used.
Various service programs are responsible for the operation of these protocols. If mail is not sent, the administrator must look for a problem in the program that services the SMTP protocol. If there is a problem with receiving mail, then you need to look for a problem in the program that serves the POP3/IMAP protocols. When contacting technical support, indicate what specifically does not work - sending or receiving (or both), this will help the administrator detect the problem. The SMTP protocol uses TCP port 25. The POP3 protocol uses port 110, the IMAP protocol uses port 143 .
Some Internet providers, in the fight against spam, block users from connecting to port 25. If, after setting up an email client, you cannot send mail, your provider may be blocking access to port 25.
You can find instructions for setting up email clients on our website (For Clients - Software Documentation). If you sent a letter and it did not reach the recipient, or a letter was sent to you, but you did not receive it, please inform technical support. support the following information:

1. from which email the letter was sent
2. to which address (e-mail) the letter was sent
3. indicate the departure time as accurately as possible

If an email arrives late, or an error message arrives, or any email makes you suspect that your mail is not working properly, forward it to tech. support the original text of this letter with all service headers.
This will help you find out the cause of the problem.
Example of the source text of a letter with service headers:

Return-path: <>
Envelope-to: user@domain.by
Delivery date: Sun, 29 Jun 2008 16:37:53 +0300
Received: from mailnull by mail.server.net with local (Exim 4.60)
id 1KCx6H-0004g4-3x
for user@domain.by; Sun, 29 Jun 2008 16:37:53 +0300
X-Failed-Recipients: manager@example.com
Auto-Submitted: auto-replied
From: Mail Delivery System
To: user@domain.by
Subject: Mail delivery failed: returning message to sender
Message-Id:
Date: Sun, 29 Jun 2008 16:37:53 +0300This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of it
recipients. This is a permanent error. The following address(es) failed:

manager@example.com
retry timeout exceeded

—— This is a copy of the message, including all the headers. ——

Return-path:
Received: from [127.0.0.1] (helo=[127.0.0.1])
by mail.server.net with esmtpsa (TLSv1:AES256-SHA:256)
(Exim 4.60)
(envelope-from)
id 1KBUwI-00059l-Dw
for manager@example.com; Wed, 25 Jun 2008 16:21:34 +0300
Message-ID: <4862465D.6040106@mail.server.net>
Date: Wed, 25 Jun 2008 16:21:33 +0300
From: Good User
Organization: Roga Kopyta
User-Agent: Thunderbird 2.0.0.14 (X11/20080421)
MIME-Version: 1.0
To: manager@example.com
Subject: - test -
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Was this answer helpful?

« Back