Forum Tips » This forum is for users to discuss their software problems and suggestions for improvement.
Remember that only a tiny percentage of our users experience such problems (To be precise less than 0.7% have ever posted on this forum)
» Include your software version number (as displayed in the About Box)
» Check the FAQ before posting as most common questions have already been answered
» You don't need to also e-mail us separately as our support team will respond to all questions on this forum
I recently had a problem with maillistking being unable to locate attachments when sending and a error coming up. When I looked in the temp folder (C:\Users\mail.RDAA\AppData\Local\Temp) I found about 11500 folders had been created with names like ~mlk672010-165647. When I deleted these folders maillist king worked fine again. Any ideas on how I can stop these folders being created. I am using ver 9.21r Steve
Generally MLK will automatically delete all temporary files and folders when it is done with them, so I'll need to investigate how you were left with so many remnants.
Was the file one of the ones you deleted from your temp folder?
The "Chinese Characters" are due to an issue in Microsoft Exchange (on the recipients end). You can resolve the problem by ensuring you specify the character encoding for the message.
To do this click the Edit button on the Message Sending Toolbar then specify your desired Encoding option. For those of us in the English speaking world it is Western European (Windows).
I tracked down the problem with chinese charactors, it could not be fixed by changing outlook settings because we use Microsoft Office Outlook Web Access (OWA) on Exchange 2003 when sending from home etc. The problem occurs when mail is sent via OWA and Exchange 2003 and a Exchange 2007 server. We had this problem where we sent the mail and another organisation used Exchange 2007 and the message ended up be garbled. Microsoft have a hot fix available - Article ID: 935489 - An e-mail message is corrupted after the Disclaimer rule is enabled on an Exchange Server 2007-based server. I also suspect if the mail was sent via the internal SMTP it may not occur.