Hello Peter,
we do not use any special characters of our german language in any folder.
BTW - we have had this problem for a very long time, it has been there before v4.01c of the IMAP module AND it was reproducable with Thunderbird 1.5.x as well.
We have another problem for which I already gave up to search for the reasons: when we scan documents with out Lexmark X 630 MFP we are able to send this a scanned image as a PDF, TIFF or JPG-attachment to an SMTP-Server. I get those mails in my inbox, but most of the times the attachments are "broken". I tried all combinations of resolutions and available file-formats, no chance. Sometimes it works for one page, and then it doesn't for the next ten scans or so. We investigatd with Lexmark-Support, changed settings, updated the firmware - no change.
To me this seems like a "timing problem" with Mercury/32, but we have a fast Gigabit-Network here, a very fast and underutilized server-machine, I never got any errors in any log from Mercury (yes, I tried transaction logging), so I am helpless. I really like Mercury/32, but if these errors stay unresolved, we will have to switch to Postfix or something like that... sigh !
Shy question: WHEN do you expect Mecury/32 v4.5 to be available in the public or even as beta?
Philipp
<p>Hello Peter,</p><p>we do not use any special characters of our german language in any folder.</p><p>BTW - we have had this problem for a very long time, it has been there before v4.01c of the IMAP module AND it was reproducable with Thunderbird 1.5.x as well.</p><p>We have another problem for which I already gave up to search for the reasons: when we scan documents with out Lexmark X 630 MFP we are able to send this a scanned image as a PDF, TIFF or JPG-attachment to an SMTP-Server. I get those mails in my inbox, but most of the times the attachments are "broken". I tried all combinations of resolutions and available file-formats, no chance. Sometimes it works for one page, and then it doesn't for the next ten scans or so. We investigatd with Lexmark-Support, changed settings, updated the firmware - no change.</p><p>To me this seems like a "timing problem" with Mercury/32, but we have a fast Gigabit-Network here, a very fast and underutilized server-machine, I never got any errors in any log from Mercury (yes, I tried transaction logging), so I am helpless. I really like Mercury/32, but if these errors stay unresolved, we will have to switch to Postfix or something like that... sigh !
</p><p>
Shy question: WHEN do you expect Mecury/32 v4.5 to be available in the public or even as beta?</p><p>&nbsp; Philipp</p>