Known Problems


Uninstalling PYTHEAS MailGate v. 2.x using Control Panel/Programs and Features does not work as expected

Applies to PYTHEAS MailGate 2.x.
Problem You try to uninstall PYTHEAS MailGate using the Control Panel / Programs and Features applet. However, the uninstallation procedure does not complete.
Fix Please use the full 2.x-setup program which you can still find in the \Program Files (x86)\Common Files\Pytheas\PmgSetup folder.
Top of page Top of page

Messages sent to a Microsoft Exchange 2007/2010 distribution list are not distributed

Applies to All releases of PYTHEAS MailGate, running with Microsoft Exchange 2007/2010.
Problem You configure a mail-enabled distribution list in Microsoft Exchange 20xx. When you send a message to the SMTP address of the distribution list, none of the members receives the message.

You can reproduce this problem with the Send test message function on the Recipient property page of the Recipient pointing to the distribution list. The SMTP dialog completes normally.

Please note that this is a Microsoft Exchange 20xx feature, not a PYTHEAS MailGate problem.

Fix Please check in the Exchange Management Console, Recipient Configuration / Distribution Group properties, Mail Flow Settings / Message Delivery Restrictions / Properties, that the checkbox Require that all senders are authenticated is unchecked.
Since v. 2.70, PYTHEAS MailGate can authenticate before sending mail to the Microsoft Exchange server, so you should no longer have this problem after configuring authentication.
Top of page Top of page

You get a 554 Maximum hop count exceeded... or 552 - header size exceeds fixed maximum size error for incoming messages

Applies to All releases of PYTHEAS MailGate, running with Microsoft Exchange 2007/2010/2013.
Problem Certain incoming messages are not accepted by your Microsoft Exchange Server.

In case of the 554-error: Looking at the Received header lines of such a message, you find out that there are a certain number of Received header lines (more than 30), but they do not correspond to a mail loop.

In case of the 552-error: the information which has been added to the message headers makes it exceed the maximum size which your Microsoft Exchange server is willing to accept.

Fix By default, Microsoft Exchange fixes the maximum number of Received headers to a value of 30. If a message has more Received headers, it considers that there is probable mail loop producing these lines. However, depending of the architecture of the mail servers which the message runs through, this limit may be exceeded, even without a mail loop.

We recommend to first check (and count) the Received message header lines of one of such messages. As these are not transmitted successfully to the Exchange server, they remain in the POP3 mailbox, and you can read the message headers after opening the Properties pages of the POP3 account, Delete/Cleanup page, View Delete Messages form, View message headers button. If you do not find any evidence of a loop, proceed as indicated below.

The maximum number of Received headers corresponds to the MaxHopCount parameter of the Exchange Receive Connector listening on port 25 (by default, its name is Default <YourServerName>). To check the current value, issue this Exchange Management Shell command:
[PS] C:\>get-receiveconnector -identity "Default YourServerName" | Format-List
Look for the MaxHopCount value.
To change the value, use the following command:
[PS] C:\>set-receiveconnector -identity "Default YourServerName" -MaxHopCount:40

In case of the 552-error, you may want to set a higher value for the MaxHeaderSize-parameter.

Top of page Top of page

Incoming messages from certain POP3 accounts are not correctly decoded by Microsoft Exchange 20xx

Applies to All releases of PYTHEAS MailGate, running with Microsoft Exchange 20xx
Problem Certain POP3 servers add a header line with illegal format (according to RFC822) to the beginning of each message. For this reason, Microsoft Exchange 20xx rejects the message headers of such messages altogether, and hence the message and its attachments are not decoded at all, leaving them in an unusable state most of the time.
Most of the time a header line is added to the top of the message source:
From xxxxx@yyy.zzz Thu Nov 11 10: 07:44 2007
Note that this line is not a valid line in the header part of a message according to RFC2822. Header lines must begin with a keyword (containing no white space) followed by a colon.
Fix Strictly speaking, this is not a PYTHEAS MailGate problem. However, for your convenience, a patch which circumvents the problem is integrated into PYTHEAS MailGate (beginning with the Communication Task release 2.12c).
To activate the patch, it is required to have the word BTConnect either in the Comment property of the PYTHEAS MailGate POP3 entry, or in the hostname of the POP3 server.

Historical note: this problem has been observed first with British Telecom BTConnect POP3 accounts, hence the choice of the keyword.

Top of page Top of page

The PYTHEAS MailGate Communication Task does not work as expected when running as a service, but works as expected when launched from the Start menu

Applies to All releases of PYTHEAS MailGate v. 3.10 and earlier.
Problem When started as a Windows service, the Communication Task does not work as expected (remember that you can use the PYTHEAS MailGate Remote Control program to supervise the operation of the Communication Task). On the other hand, after stopping the PYTHEAS.Mailgate service, and after being launched from the Start menu, the Communication Task works as expected. Most of the time, this problem has been observed on Windows Server 2003.
Fix Use the Windows Services applet to make the PYTHEAS.MailGate service run within the context of a user session, as opposed to run it within the Localsystem context, which is the default.
Top of page Top of page

PYTHEAS MailGate does not correctly recognize outgoing message priority

Applies to All releases of PYTHEAS MailGate.
Problem All outgoing messages are handled as "normal priority".
Fix Open PMailGat.INI, and modify the following lines in the [Outgoing mail] section, to configure how to recognize high and low priority messages. For example, with Microsoft Exchange 2007, modify them so that they read as follows:
Delivery priority header=Importance
High priority delivery value=high
Low priority delivery value=low
To find the appropriate values for your mail server, send high and low priority messages and have a look at the message headers of the outgoing messages. You may catch them in the PytheasMailgate\Outgoing folder while they are in the queue of outgoing messages. Restart PYTHEAS MailGate after modifying PMailGat.INI.
Top of page Top of page

The PYTHEAS MailGate service does not start at system start-up

Applies to All releases of PYTHEAS MailGate
Problem The PYTHEAS.MailGate service does not start at system start-up, in spite of being configured for automatic start-up. An event log entry reports that this service did not respond in a timely fashion.
Fix This can happen if the server is very busy at system start-up. Set up the service in "delayed start"-mode, or have a look at,
Top of page Top of page