Sep 18, 2020 
Support Center » Knowledgebase » VisNetic MailServer » Client session Delivery error permanent problems with the remote server
 Client session Delivery error permanent problems with the remote server
Solution This article applies to VisNetic MailServer 9.x.x. It's possible that VisNetic MailServer will not retry delivery when non-permanent delivery errors are returned by a receiving server. For example, lets say that VisNetic MailServer is sending mail to a remote server that rejects the message with a 4xx error. 4xx errors are temporary rejections (such as 451) that forces the mail server to retry message delivery. Greylisting is a good example of when a 4xx error is returned by a remote server, here's an example log,

Client session <<< 451 4.7.1 Please try later
Client session *** < sender@senderdomain.com > < user@remotedomain.com > 3 910011 00:00:02 ERROR
Client session >>> QUIT
221 2.0.0 remotedomain.com closing connection

Message retry intervals are determined by the Delivery settings in VisNetic MailServer. There are two settings, undeliverable and warning messages. Open the VisNetic Admin and select Mail Service, SMTP Service, Delivery tab. The default settings are,

Undeliverable after: 4 days, and Warning after: 6 hours

If 'Undeliverable' is less than the 'Warning', for example,

Undeliverable after: 4 minutes, and Warning after: 6 hours

The system will retry the message for a period of 4 minutes. After 4 minutes the next delivery failure, regardless of the error returned, will be consider permanent and result in the following log entry,

Client session <<< 451 4.7.1 Please try later
Client session *** < sender@senderdomain.com > < user@remotedomain.com > 3 910011 00:00:02 ERROR
Client session >>> QUIT
221 2.0.0 remotedomain.com closing connection
Client session Delivery error permanent problems with the remote server remotedomain.com
Client session Disconnected

To fix this problem set your Delivery settings to,

Undeliverable after: 4 days, and Warning after: 6 hours

As a side note, when setting the undeliverable interval make sure it's always after the warning message delivery time.


Article Details
Article ID: 633
Created On: Mar 12, 2008 04:10 PM

 This answer was helpful  This answer was not helpful

 Back
 Login [Lost Password] 
Email:
Password:
Remember Me:
 
 Search
 Article Options
Home | Register | Submit a Ticket | Knowledgebase | News | Downloads
Language: