Just as a test - I uninstalled James 2.3.1 on this server and reinstalled 
James 2.2.0 and installed it as a service and port 25 got recognized right 
away and email starting flowing back and forth. This was done after a 
reboot of the server and port 25 still was not listening. Netstat -AN 
shows port 25 listening now when James 2.2.0 is running. 

Does this imply a configuration issue with our new James 2.3.1 
installation? If so, I would assume email wouldn't have ever worked since 
James 2.3.1 got installed nearly three weeks ago. That is not the case. We 
have been sending and receiving emails for the last three weeks. Only in 
the last couple of days have been having problems with port 25 and there 
have been no configuration changes to James 2.3.1 since it first got 
installed. 

I neglected to mention in my first posting that we are running James 2.3.1 
on three identical servers. Two servers are running fine with no issues. 
It is only the one server (which does by far the most volume) that we are 
having the issue with. 

Any insight would be helpful.

Thank you. 

John Rose
Database Administrator






Norman Maurer <[EMAIL PROTECTED]> 
09/24/2007 09:33 AM
Please respond to
"James Users List" <[email protected]>


To
James Users List <[email protected]>
cc

Subject
Re: Port 25 stops responding






Well nothing special ;-) Just post us the last lines after it stops
workin...

bye
Norman


Am Montag, den 24.09.2007, 09:29 -0500 schrieb John Rose:
> I have logging at a DEBUG level so the log file is pretty large - too 
> large to post here. Anything in particular you are looking for?
> 
> John Rose
> Database Administrator
> 
> FoundationIP - Part of CPA Software Solutions
> 
> Direct Dial:  +1 612-236-9917
> Email: [EMAIL PROTECTED]
> Fax: +1 612-332-0080
> 
> Computer Patent Annuities North America LLC / FoundationIP
> 900 Second Avenue South Suite 1700
> Minneapolis, MN 55402
> 
> CPA is the world's leading provider of outsourced IP services, For 
further 
> information about our products and services go to www.cpaglobal.com.
> 
> 
> 
> 
> 
> Norman Maurer <[EMAIL PROTECTED]> 
> 09/24/2007 09:20 AM
> Please respond to
> "James Users List" <[email protected]>
> 
> 
> To
> James Users List <[email protected]>
> cc
> 
> Subject
> Re: Port 25 stops responding
> 
> 
> 
> 
> 
> 
> Hi John,
> 
> can you show us your smtpserver-*.log ?
> 
> bye
> Norman
> 
> Am Montag, den 24.09.2007, 09:09 -0500 schrieb John Rose:
> > We have just implemented James 2.3.1 on our Windows 2003 server and 
> > several times now in the last couple of weeks Port 25 does not 
respond. 
> > When doing a telnet to XX:XX:XXX:XXX 25 from a cmd prompt  we get a 
> > message cannot open connection to the host, on Port 25: Connection 
> failed. 
> > When I do a netstat -an command, port 25 does not show up as a 
listening 
> 
> > port. 
> > 
> > This sort of behavior did not happen when we were on James 2.2.0. 
> However, 
> > it may be a coincidence. 
> > 
> > We have no other services or programs listening on port 25. Can anyone 

> > assist with helping us determine why port 25 goes down. Also, is there 

> any 
> > way to get it to accept connections again without rebooting the 
server. 
> > 
> > Thank you. 
> > 
> > 
> > John Rose
> > Database Administrator
> > 
> > FoundationIP - Part of CPA Software Solutions
> > 
> > Direct Dial:  +1 612-236-9917
> > Email: [EMAIL PROTECTED]
> > Fax: +1 612-332-0080
> > 
> > Computer Patent Annuities North America LLC / FoundationIP
> > 900 Second Avenue South Suite 1700
> > Minneapolis, MN 55402
> > 
> > CPA is the world's leading provider of outsourced IP services, For 
> further 
> > information about our products and services go to www.cpaglobal.com.
> > 
> > 
> > 
> > 
> > 
> 
********************************************************************************
> > The information in this message is confidential and may be legally
> > privileged. It is intended solely for the addressee; access to this
> > email by anyone else is unauthorized.
> > 
> > If you are not the intended recipient: (1) you are kindly requested
> > to return a copy of this message to the sender indicating that you
> > have received it in error, and to destroy the received copy; and (2)
> > any disclosure or distribution of this message, as well as any action
> > taken or omitted to be taken in reliance on its content, is prohibited
> > and may be unlawful.
> > 
> 
********************************************************************************
> > 
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 
********************************************************************************
> The information in this message is confidential and may be legally
> privileged. It is intended solely for the addressee; access to this
> email by anyone else is unauthorized.
> 
> If you are not the intended recipient: (1) you are kindly requested
> to return a copy of this message to the sender indicating that you
> have received it in error, and to destroy the received copy; and (2)
> any disclosure or distribution of this message, as well as any action
> taken or omitted to be taken in reliance on its content, is prohibited
> and may be unlawful.
> 
********************************************************************************
> 
> 
> !DSPAM:1,46f7ca48283437275418602!


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorized.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************

Reply via email to