> http://code.google.com/p/android/issues/detail?id=4761

Thanks for this - that's an interesting thread, and highlights just how difficult it is to write an IMAP implementation that correctly deals with every possible combination of commands the protocol allows. In this particular case, the issue is clearly a bug in my code rather than anything the Android code is doing, but it's fascinating that the approach the Android developer has taken has exposed similar problems in a wide range of other IMAP servers too.

Cheers!

-- David --

Thank's for help.

It was an old version of clamav! After update all work's fine.

Thank's for the help!

Matthias Schlegel

Hi!

I've hit some problems when upgrading popfile to 1.1.1. and don't really know where to begin looking to sort them out and since all I really want to do is upgrade Mercury... do I need to upgrade popfile to the latest version in order to run the latest version of Mercury or would the latest version of Mercury work with popfile 0.21.1?

The issue I'm having with the popfile upgrade is that popfile crashes whenever I open the "security" or "configuration" tabs in the UI (in case anyone here has seen that issue before).

EDIT:

In case anyone else runs into this... the problem was that the old popfiled merc.pm module was still in the proxy directory of popfile. I removed the file (...\popfile\proxy\merc.pm) and could once again access all the tabs in the GUI. Upgrading to the latest version of popfiled was then easy. 

Yesterday ClamAV released a signature that disabled all versions of the program older than 0.95. If you are running ClamWall this will cause the daemon to try to start clamd for every message. The resulting timeouts will more or less make Mercury core stop working even though it indicates that it's active.

Thanks to Grant Root for pointing this out!

Thanks Rolf.  I checked this file with the service here:

 http://virusscan.jotti.org

 and it was clean.  I've reported it to AVG.  Hopefully they can fix/correct it.

Mark

A MILLION THANKS, PAUL!!!  I had no idea it was that easy. 

I'm on my way!

Thanks again!!!

Thanks for your fast reply and pointing me to the right direction [:)]

This is really confusing stuff, but i guess it be more clearer the more time i spend with it.

This is what i did, and it works just fine.

From: admin@~N (=?UTF8?Q?Administrat=C3=B6r?=)
To: ~T
Subject: =?UTF8?Q?Bekr=C3=A4ftelse_av_E-post_leverans?=
Date: ~D

Ditt support ärende har mottagits, och kommer så snart som möjligt att behandlas.

not really a big message, around 350kb, timeout 30, and the problem is, that everything since last backup is lost. i was able to download bigger mails by isdn conection and now by dsl.

Hi!

the same problem exists if one of those users wants to use the REVIEW command. The mail is processed by the core and that is the result:

I 20100413 2126 MG000B1A hpr@domain                    Maiser                         560
I 20100413 2126 MG000B1B Maiser@domain                 :hpr                           35176

But, HPR should be resolved to both users, right? That part is missing and no list review is send to the original user...

Best,

Konrad

Works quite well for English speakers when processed through Google Translate.

[quote user="gromit"]Understood. However, you can't get to my gateway, it's locked down for any type of acccess

 [/quote]Not quite. You must at least be allowing access to port 25, or else how can you receive any mail?

He is not going to "access your server". What he is suggesting is connecting to your MercS , as per anyone who sends you mail, issuing a RCPT TO: command for a bogus local address and examining the servers reply for a clue.

[quote]The QCF file looks like this:

ST: R 100420162000 05 000001 000000 000000
FR: <yesmail@email-yesmail.p0.com>
DF: MG0010C0.QDF
FL: 256       
OS: 100420134853
BA: <info@domainremoved.com>
ES: R 100420155000
RI: 000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
DI: MD00224F.QIF
EA:

 The addresses come to info@domainremoved.com, marketing@domainremoved.com, addresses we do not have.

[/quote]

What does this .qif file contain?

This problem may be related to your Pmail thread, where is your queue located?

Thanks, Thomas.  I'll try to get us on 4.41. No Windows 7 systems, yet!

Regards

I think the important thing to realise is that unlike many mail systems, Mercury has no rigid link between user name and email address. This took me a while to get used to, and I'm still not sure I have it completely clear - but as I understand it there's no need to change mailbox or user name, nobody but the user herself will know she's using the old user name.

 Chris

This site http://mystyleit.com/blogs/mystyleit/archive/2009/06/15/running-mecury-mail-as-a-service.aspx says: "Be careful not to start Mercury in the native app mode while the service is running, or you might make it angry. The best way to do it is to stop the service, launch Mercury, make your configuration changes, close Mercury, restart the service."

So, don't just start the GUI while the service is running. You should you the use the 'annoying' feature that you might have disabled to make configuration changes. Or stop the service prior to opening the GUI.

thank you its now working great thanks to your help [:)]

done

Check that the user you're running Mercury as has permission to create and delete files in the Mercury folder.

Chris

Thanks for confirmation. It is hard to tell if it is Mercury or Popfile but I do suspect Popfile.

I did find out in another post that I can copy back the files to the Queue and get them to process by restarting Mercury so that helps when the problem occurs. It hasn't happened in a week but I am keeping an eye on it so see if I can discover anything else.

 thanks again

davew

Open the Windows registry with RegEdit and check for a key containing "MS Sans Serif" in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes. If it exists then delete that key.

Note: Modifying the Windows registry can cause big problems if any mistake is made, so make sure you understand how to use the program before deleting anything.

/Rolf 

As you are relying on ASSP Antispam for spam fighting you will probably have to seek the solution there. It puts itself between Mercury and the Internet, and makes several of the antispam features in Mercury useless. You could run SpamHalter as well or hope this specific type of spam will be caught by Mercury content control, but I doubt it would help much in this case.

/Rolf