What’s new in Narawen Inox POP3 Connector 5.4 SR-1

Changes introduced in version 5.4 SR-1:

• fixed problem with accessing POP3 mailbox filled over 2 GB of space

‘Can not retrieve mailbox statistics’ error while transferring the messages using Narawen Inox POP3 Connector

Symptoms
Messages are not transferred. Following error is reported into Event Log:

Can not retrieve mailbox statistics from xxxx.
Value was either too large or too small for an Int32.

Cause
Narawen Inox POP3 Connector could not handle properly POP3 mailboxes were awaiting messages occuppy more than 2 GB.

Solution
Upgrade to the latest release of Narawen Inox POP3 Connector.

Applies to
Narawen Inox POP3 Connector 5.4 (2011-07-27)
Narawen Inox POP3 Connector 5.3 (2010-01-11)
Narawen Inox POP3 Connector 5.2 SR2 (2009-10-23)
Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)
Narawen Inox POP3 Connector 5.1 SR1 (2006-09-25)
Narawen Inox POP3 Connector 5.1 (2006-06-14)
Narawen Inox POP3 Connector 5.0 (2005-11-10)

What’s new in Narawen Inox POP3 Connector 5.4

Changes introduced in version 5.4:

• supported secure (POP3S/SMTPS) connections using SSL 2.0, SSL 3.0 and TLS 1.0 protocols,
• fixed problem with crashing service.

InoxSvc.exe service crashes

Symptoms:
The service InoxSvc.exe crashes during operation without any information in Application event log.

Following error can be found in System event log:

The InoxSvc service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Cause
The problem occured due to background thread which improperly handled unexpectedly closed POP3 connections.

Solution
Upgrade to the latest release of Narawen Inox POP3 Connector.

Applies to
Narawen Inox POP3 Connector 5.3 (2010-01-11)
Narawen Inox POP3 Connector 5.2 SR2 (2009-10-23)
Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)

‘No such host is known’ warning while transferring the messages using Narawen Inox POP3 Connector

Symptoms
Messages are not transferred. Following warning is reported into Event Log:

Report for message xxx of xxx from xxxx.

Delivery report:
Status: Not completed
xxx@xxx:
Not delivered. No such host is known.

Cause
Narawen Inox POP3 Connector used reverse DNS lookup to retrieve mail host name. In some network configurations this query fails with error message ‘No such host is known’.

Solution
Upgrade to the latest release of Narawen Inox POP3 Connector.

Applies to
Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)
Narawen Inox POP3 Connector 5.1 SR1 (2006-09-25)
Narawen Inox POP3 Connector 5.1 (2006-06-14)
Narawen Inox POP3 Connector 5.0 (2005-11-10)

SMTP authentication error while dynamic addressing is in use

Symptoms
SMTP server reports authentication error despite correct credentials configured. It happens when dynamic addressing is in use.

Cause
There was a problem with Narawen Inox POP3 Connector. It was not sending authentication details to SMTP server when dynamic addressing was in use.

Solution
Upgrade to latest release of Narawen Inox POP3 Connector.

Applies to
Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)
Narawen Inox POP3 Connector 5.1 SR1 (2006-09-25)
Narawen Inox POP3 Connector 5.1 (2006-06-14)
Narawen Inox POP3 Connector 5.0 (2005-11-10)

Dynamic addressing does not recogize some mail headers

Symptoms
Messages are not delivered by Narawen Inox POP3 Connector when dynamic addressing is in use.

Cause
Narawen Inox POP3 Connector was case-sensitive while recognizing message headers which could cause them to be ignored.

Solution
Upgrade to latest release of Narawen Inox POP3 Connector.

Applies to
Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)
Narawen Inox POP3 Connector 5.1 SR1 (2006-09-25)
Narawen Inox POP3 Connector 5.1 (2006-06-14)
Narawen Inox POP3 Connector 5.0 (2005-11-10)

Support for BCC addresses in Narawen Inox POP3 Connector

What is BCC address
When the sender of the e-mail message decides to hide recipients from being aware of each other he can use BCC (Blind Carbon Copy) address field while editing the message.

The e-mail addresses put in BCC field are not stored inside message header set like regular “To:” or “CC:” fields.

This can cause the situation that POP3 mailbox will contain message without any recipient addresses specified. It means that the recipient was on BCC list.

Static addressing is not affected
There is no issue with static addressing offered by Narawen Inox POP3 Connector. It just grabs all the contents of mailbox and sends to target address regardless if the messages have any addressing information or not.

How to fix dynamic addressing for BCC addresses
For dynamic addressing Narawen Inox POP3 Connector must have valid recipient address available in order to route the mail properly.
Starting from version 5.2 SR2 this is supported by handling “x-rcpt-to” header added by some mail servers with hint what was the recipient e-mail address.

We recommend the upgrade to latest release to avoid problems with dynamic addressing caused by BCC field.

Applies to:

Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)
Narawen Inox POP3 Connector 5.1 SR1 (2006-09-25)
Narawen Inox POP3 Connector 5.1 (2006-06-14)
Narawen Inox POP3 Connector 5.0 (2005-11-10)

How to backup Narawen Inox POP3 Connector settings

To back up the configuration of Narawen Inox POP3 Connector use Registry Editor. All settings are stored at following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Virtual Moon\Inox

Just export it to REG file and import in case of need.

Exchange Server rejects huge e-mail messages

Symptoms:

Messages bigger than 10 MB are not transferred by Narawen Inox POP3 Connector. They are downloaded from POP3 mailbox and retried to be sent without effect.

Additionally in Application event log InoxSvc records following message:

Report for message 1 of 1 from xxx@xxx

Delivery report:
Status: Not completed
xxx@xxx:
Not delivered. Connection to smtp://exchange-server:25 reported protocol error. 552 5.3.4 Message size exceeds fixed maximum message size.

Message details:

The hint is “fixed maximum message size”. Usually the limit is set in recipient policy. In that case increasing limit at recipient policy will not help. To adjust “fixed maximum message size” proceed with following steps:

1. Exchange Server Management Console
2. Organization Configuration
3. Hub Transport
4. Locate the appropriate Receive Connector
5. Adjust the value of the Maximum Message Size (KB)