Known Problems
|
|
|
 |
|
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. Please
have a look at
http://support.microsoft.com/kb/922918, or it may help to make the Pytheas.MailGate service dependent on some other
service which starts up late; you may want to have a look at the application
event log to get an idea which one to choose for this purpose. If PYTHEAS
MailGate is installed with a Microsoft Exchange 2003/2000 server, its
POP3 service (POP3Svc) may be a good candidate. We pick this one as an example
here. To configure the dependency, proceed as follows:
- Open Regedt32.exe (not Regedit.exe);
- Go to HKEY_LOCAL_MACHINE/System/Currentcontrolset/Services/Pytheas.MailGate
- Open the DependOnService value. By default, it has 3 lines:
Eventlog, RpcSc, TcpIp.
- Add the line: POP3Svc to the end of the list. This
will make the Pytheas.Mailgate service dependent on this service.
|
|
|
|
|
|
Messages sent to public folders by PYTHEAS MailGate
are stored as a post (IPM.Post), not as a message (IPM.Note) as expected
|
Applies to |
All releases of PYTHEAS MailGate, running with Microsoft
Exchange 200x |
|
Problem |
As explained in the title of the article. Please note that - strictly
speaking - this is not a PYTHEAS MailGate problem. |
|
Fix |
Please see the Microsoft knowledgebase,
article 817809. |
|
|
|
|
|
Messages sent to a Microsoft
Exchange 2007 distribution list are not distributed
|
Applies to |
All releases of PYTHEAS MailGate, running with Microsoft
Exchange 2007 |
|
Problem |
You configure a mail-enabled distribution list in Microsoft Exchange
2007. 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 2007 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. |
|
|
|
|
|
Incoming messages from certain POP3
accounts are not correctly decoded by Microsoft Exchange 200x
|
Applies to |
All releases of PYTHEAS MailGate, running with
Microsoft Exchange 200x
|
|
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
200x 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. |
|
|
|
|
|
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. |
|
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. |
|
|
|
|
|
The PYTHEAS MailGate
Communication Task stops working unexpectedly
|
Applies to |
All releases of PYTHEAS MailGate. A real-time virus scanner is
working on the same machine. |
|
Problem |
When downloading a particular message, the Communication Task
(or the Pytheas.Mailgate service) quits unexpectedly. Restarting it does
not fix the problem.
This probably happens because temporary files created by the
Communication Task are blocked by the virus scanner because they
are considered infected. You may want to check the virus scanner log if
you find a trace of such events. |
|
Fix |
Please read the blue box on the top right on
this page. |
|
|
|
|
|
Certain kind of attachments in
outgoing messages appear to be corrupted (with Microsoft Exchange 5.x server)
|
Applies to
|
Microsoft
Exchange server v .5.0 or v. 5.5 |
|
Problem |
Certain kind of attachments (for example files in Adobe
Acrobat format) are MIME encoded "quoted printable" format by the Microsoft
Exchange Internet Mail Service. Certain mail programs have problems decoding
such attachments, so they appear corrupted. |
|
Workaround |
The Microsoft Exchange Server (v. 5.0
or v. 5.5) can be forced to do the MIME encoding in base64 which is widely supported.
To change the default behaviour you need to edit the registry (please be
careful using the registry editor...)
Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\...
...Services\MSExchangeIS\ParametersSystem\...
...InternetContent
Add the value ForceBase64 of data
type REG_DWORD with value 0x1. Then
restart the Microsoft Exchange server Information Store service (and any
dependent services).
From: Microsoft Knowledge Base, Article ID: 182307 (Article last modified
on 05-Nov-2004).
|
|
|
|
|
|
Timeout error with empty POP3 mailbox
|
Applies to |
All releases of PYTHEAS MailGate |
|
Problem |
With a certain type of POP3 server, you systematically get
a Timeout error when the Communication Task connects
to the POP3 server. Messages in the maildrop are correctly downloaded. |
|
Explication (not the solution) |
The POP3 server does not conform to RFC 1939. Use the
Try connection button of the Configuration Program,
POP3 account property page, to see the POP3 dialog when the mailbox is empty.
Check if you get a dialog like:
+OK IMS POP3 Server 0.87 Ready
USER username
+OK username is welcome here
PASS xxxxxxxxxxx
+OK username's mailbox has 0 message(s) (0 octets)
LIST
+OK 0 message (0 octets)
0 messages (0 octets)
The problem is that the "0 messages (0 octets)" line should not be there,
and that the response to the "LIST" command is not terminated by a single
point on a line.
Here is what RFC 1939 (POP3, May 1996) says on the subject (we did the bold
typesetting):
(...)
Responses to certain commands are multi-line. In these cases, which are
clearly indicated below, after sending the first line of the response and
a CRLF, any additional lines are sent, each terminated by a CRLF pair. When
all lines of the response have been sent, a final line is sent, consisting
of a termination octet (decimal code 046, ".") and a CRLF pair.
(...)
LIST [msg]
Arguments: a message-id (optionally) If a message-id is given, it may NOT
refer to a message marked as deleted.
Restrictions: may only be given in the TRANSACTION state.
Discussion:
If an argument was given and the POP3 server issues a positive response
with a line containing information for that message. This line is called
a "scan listing" for that message.
If no argument was given and the POP3 server issues a positive response,
then the response given is multi-line. After the initial +OK, for each message
in the maildrop, the POP3 server responds with a line containing information
for that message. This line is called a "scan listing" for that message.
If there are no messages in the maildrop, then the POP3 server responds
with no scan listings--it issues a positive response followed by a line
containing a termination octet and a CRLF pair.
|
|
Workaround |
None. Besides setting timeouts for the Communication
Task to a low value, and setting the error retries to 0. |
|
|
|
|
|
The PYTHEAS MailGate Communication
Task stops working randomly after finishing mail download from the last POP3
account
|
Applies to |
All releases of PYTHEAS MailGate prior to, and
including, v. 2.21e |
|
Problem |
The problem occurs randomly when both of the following conditions
are met:
- a Session Log message is sent to both local and remote Recipients,
- outgoing mail is not handled by PYTHEAS MailGate. |
|
Fix |
The problem has been fixed in v. 2.21f. |
|
|
|
|
|
Messages delivered to a mailbox abnormally
grow in size
|
Applies to |
PYTHEAS MailGate prior to, and including, v. 2.30 |
|
Problem |
This problem has been observed on very sporadically, for
HTML formatted messages of a size around 30...70 kb. If it occurs, certain
inner parts of the occur repeatedly which makes the message grow in size.
The problem has never been observed with binary attachments. |
|
Fix |
The problem has been fixed in v. 2.30c. |
|
|
|
|
|
Virus scanner interface: disabled
size limit does not work as expected
|
Applies to |
PYTHEAS MailGate v. 2.30, Virus scanner interface |
|
Problem |
If the size limit for messages to be submitted to the virus
scanner is disabled (the corresponding check box has been unchecked), no
virus check takes place. |
|
Workaround |
Set a size limit. Setting a high value virtually disables
the limit anyway. |
|
Fix |
The problem has been fixed in v. 2.30c. |
|
|
|
|
|
Problem sending outgoing messages to
a server which does not support ESMTP protocol extensions
|
Applies to |
PYTHEAS MailGate release 2.13 |
|
Problem |
The problem occurs when the SMTP relay server
does not accept the ESMTP logon (the server issues a 502 reply). PYTHEAS
MailGate should switch to a SMTP logon and work in SMTP mode. Unfortunately,
this does not work as expected :-(. |
|
Fix |
The problem has been corrected in
release 2.13a. |
|
|
|
|
|
Session log messages sent to
remote locations grow in size
|
Applies to
|
PYTHEAS MailGate v.2.20. |
|
Problem |
The problem occurs when both of the following conditions
are met:
- the product is configured to take care of outgoing mail
- a session log message is sent to a remote location (as configured
on the Logging tab of the Configuration Program).
|
|
Fix |
The problem has been fixed in v. 2.21. |
|
|
