Pegasus Mail & Mercury

Hi,

I've been using Mercury for a few years now and never come accross a major problem I've been unable to fix without the aid of the internet or my friendly IT chappy... however, today I've experienced just that.

When the POP3 Distrubution connects, I am alsmost immediately getting a message return -

TCP/IP Communication Error. Network Error; Delivery Anway

Which makes little sense, this was working with no problems this morning until about 10:00. This error has occured in the past, but has always gotten rid of itself within a 15mins, 60mins on the outside. This time that is not happening.

I've searched the internet and here for answers, and where a solution has been given, I'm told it's due to the timeout, as I get the error less then a second in I doubt it's that, but have tried it at 3 minutes just in case. Finally, I've been told their are no problems with the mail host we are trying to connect to. I've also tried rebooting the machine, and I even tried it on another machine, which gave me the same error. I'm fairly sure the error is with the mail host as opposed to the mercury machine, but if anyone can enlighten me, that would be great. Thanks for your time.

My session log -

13:07:41.468: --- Tue Aug 19 13:07:41 2008 ---

13:07:41.468: Connect to 'XX', timeout 30.

13:07:42.656: >> +OK dovecot ready.<cr><lf>

13:07:42.656: << USER XX<cr><lf>

13:07:42.703: >> +OK<cr><lf>

13:07:42.703: << PASS XX<cr><lf>

13:07:43.765: >> +OK Logged in.<cr><lf>

13:07:43.765: << STAT<cr><lf>

13:07:43.859: >> -ERR No INBOX for user.<cr><lf>

13:07:43.859: << QUIT<cr><lf>

13:07:43.859: --- Connection closed normally at Tue Aug 19 13:07:43 2008. ---

13:07:43.859:

try deleting the pop3 cache file, newmail.cac. You don't have to re-boot the machine, just quit and restart Mercury.

---

Kind regards / Peter

Thanks for the quick response :D

I wasn't able to find the newmail.cac file, searching for *.CAC didn't return the file anywhere on my local disk either...

Is the local userbase intact?

Can you reach the mail directories?

What if you send a message using Mercury/32 directly to the local user name - does it get there?

// the file newmail.cac resides in the mailbox directory of each user //

---

Kind regards / Peter

All outgoing mails are working fine, and I can send locally to each user with no problems.

I've also sent a mail from the mercury console to myself, and this came through just fine.

In the mailbox for each user I found a MERCURYP.CAC file, I moved them out to my desktop (didn't want to outright delete it, just in case) and restarted Mercury, again to no avail.

I'm not sure of the relevance, but this is a new installation on a new machine. However the old machine is producing the same error and it was working on the new machine this morning. SMTP is having no problems, although I did have to change the port settings of the SMTP client from 25 to 2500.

Can you try using a different POP3 server to verify your Mercury setup? Looks to me like the dovecot server is telling you that it can't find the users mailbox. 

 

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I tried another POP3 server, no problems at all. So, should I assume the people on the mail host are telling me porkies and it is indeed a problem their end?

Aha, we're talking about MercuryD - then my advice on the cache files were not in play - sorry.

---

Kind regards / Peter

It looks very much like a problem with the remote mail host. Try connecting to it directly with your email client program and see what happens.

/Rolf 

Thanks to you all for the assistance. I got back on to the mail host this morning who told me I just needed to reboot the machine, when I explained that hadn't work, with a little reluctance he went away to check on the thing. In the end the file at his end had become corrupted with two funky characters in one of the headers. It is now fixed and I've got several thousand spam mails to compete with... I'm not so sure fixing it was that great now... lol

 

Thanks again