RE: [IMail Forum] pop3d problems

[Travis Rabe]

Then look at their firewall for outbond port 25 rules.  Can they telnet to the mail server via port 25?   Travis   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Mark Sent: Monday, August 23, 2004 11:55 AM To: [EMAIL PROTECTED] Subject: Re: [IMail Forum] pop3d problems   The only SMTP entries are: 08:23 01:28 SMTPD(029501CA) [61.171.181.41] RCPT TO: <[EMAIL PROTECTED]> They receive email just fine.  Just can't send it. Mark At 01:45 PM 8/23/2004, you wrote: Mark,   POP3 is a "retrieval" protocol and has nothing to do with the standard sending of mail. What do the SMTP logs show for this user?   Eric S ----- Original Message ----- From: Mark To: [EMAIL PROTECTED] Sent: Monday, August 23, 2004 1:12 PM 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