On Sun, Jan 12, 2003 at 09:36:39PM -0500, Mark Weaver wrote: > On Sunday 12 January 2003 09:25 pm, [EMAIL PROTECTED] scribbled incoherently: > > > Hi Ric, > > > > > > The very first thing I'd do is turn PS completely off. Better yet...just > > > take the little bugger outa there cause in the long run that app is more > > > trouble at times then it's worth. Once that thing isn't present to muck > > > up the works you may have an easier time debugging the situation. > > > > > > I was running into that for a while some time back and got so sick of PS > > > doing that very thing to me I just took it out. I've not been having any > > > troubles like it since. And I'm still able to keep track of connections > > > to the box just as well. It just gets done a little differently now. > > > -- > > > Mark > > > > Hi Mark; > > Thank you for the reply. > > > > Ok, I just shut off portsentry (service portsentry stop). Bastille-firewall > > is still running. (I'm open to suggestions on better firewalls... Been > > running Bastille for a while now. Never had any problems in the past. But > > this one is hair puller.. > > > > Ok, so after shutting down portsentry, I still can't get my e-Mail. I > > get a "Failure to connect to server" error at the client end. Nothing in > > the logs on the server. imap is listed in the Bastille config file. > > > > But the port seems blocked. If it's not bastille, what is it? > > > > Ric > > Ok...just to make sure, do a restart on both the Postfix service and the > xinetd service to ensure they're running. This is usually the #1 cause of > that particular error message when trying to connect to the imap service. It > goes without saying that you've already got port 143 open for imap > connections since you were connecting in that manner before. > > I too use Bastille, and haven't had any troubles with it. If you're still > unable to connect just give a holler cause there's something tickling at the > back of my neck for this, but I just can't put my finger on it. I'm sure > though as we go through this it'll come to me. > -- > Mark
GOT IT! (I hope!). Ok, I restarted both xinted, and postfix, and it works now! (whew). So now I need to check the runlevels to be sure xinetd & company are in there. msec cleaned a bunch of stuff out for me... (grr...). In putting things back, I missed xinetd, hence the source of this round of troubles. But I think I'm about there now. (whew!). imap connections work from both inside, and outside, and the other services have come to life again. I was digging too deep into the problem. Xinetd was not running... Missed the obvious one.. Thank you! Thank you! Thank you! Ric
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
