That's if the hardware has a problem with POP only.  I haven't seen a hardware problem like that before.

At 03:40 PM 8/23/2004, you wrote:
If stopping/starting the service doesn't clear this then I would have to look at hardware, typically network subsystem (NIC) and you have to reset the server to reset the hardware
 
Eric S
----- Original Message -----
From: Mark
To: [EMAIL PROTECTED]
Sent: Monday, August 23, 2004 3:07 PM
Subject: RE: [IMail Forum] pop3d problems

One problem solved.  The client that couldn't send but could receive finally called his ISP who had just moved to another provider themselves.  They were trying to route all email through their own mail servers.  Once the DNS was fixed on their side everything worked ok.

That still doesn't answer the problem with POP not working at other clients from time to time until I reboot the server.  A simple stop/start of the service doesn't fix that problem.

Mark


At 01:52 PM 8/23/2004, you wrote:
If that is the case and  they cannot establish a SMTP session it is being blocked wither by your firewall or theirs.
 
Travis
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark
Sent: Monday, August 23, 2004 11:44 AM
To: [EMAIL PROTECTED]
Subject: RE: [IMail Forum] pop3d problems
 
That is the extent to the entries in the log.  We have SMTP and POP3 both in the same log.

Mark

At 12:59 PM 8/23/2004, you wrote:

What does the SMTP log file say?
 
Travis
 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark
Sent: Monday, August 23, 2004 10:12 AM
To: [EMAIL PROTECTED]
Subject: [IMail Forum] pop3d problems
 
I currently have 8.05 fully patched on a win2k server.  We have a Sonicwall Pro 330 firewall with cisco routers and switches.  We get our bandwidth from Sprint, and MCI.

For some time I have experienced an intermittent problem with some, not all, of my clients being able to access pop3 from their client programs (outlooks).

They typically can receive email but cannot send email.

This will happen to 2 or 3 of my client domains that reside on my server.

This is the entry for one of our clients today that nobody in their office can send email via the client.



08:23 11:46 POP3D



(00000570) logon success

for


sashwill
 


mail.somecompany.com

from


xx.xxx.xxx.xxx
 


 
 


08:23 11:46 POP3D


(00000570) logoff for

sashwill R:0,
D:0,


P:0
 


 
 


 


This is the entire entry for this persons attempt to send an email to me on the server.

I do not have their IP listed in SMTP security and do not want to.

I had another client early in the morning with the same problem.  I rebooted the server and their problems cleared up but this client is still having the problem.

Has anybody else seen problems like this and if so what solution was found if any?

Since this is only happening upon occasion I am inclined to believe the problem is somewhere outside our network.  Also since it doesn't impact our clients severely I have ignored the problem for the most part.

We will be upgrading to the latest version soon and I wanted to at least find out where the problem is coming from.
Mark

Reply via email to