From: Paul Furness <paul.furness@vil.ite.mee.com>
To: David Limon Romero <dlr@mega.net.mx>
Cc: linux-admin@vger.kernel.org
Subject: Re: imap problem
Date: 05 Sep 2002 09:50:23 +0100 [thread overview]
Message-ID: <1031215823.8926.70.camel@Zebra> (raw)
In-Reply-To: <Pine.LNX.4.44.0209040126120.5074-100000@servidor.mega.net.mx>
David,
It's probably worth verifying if IMAP is actually available or not on
that machine.
There are a couple of things you can try:
First, check that IMAP is actually available as a service on the machine
by telnetting directly to the IMAP port. Say your machine is called
"Mailsvr" then at a command prompt (anywhere on the network) try this:
telnet mailsvr 142 #(I'm assuming IMAP2 - check your port number
with 'grep imap /etc/services' )
If IMAP is running and available you should get something like this (I
changed my server names and IP's to protect innocent bystanders):
Zebra$ telnet mailsvr 143
Trying 10.10.10.84...
Connected to mailsvr.
Escape character is '^]'.
* OK Courier-IMAP ready. Copyright 1998-2001 Double Precision, Inc. See
COPYING for distribution information.
If you get that, then IMAP is working, and you have a different problem
- such as usernames / passwords not working etc.
If, on the other hand, you get this:
Zebra$ telnet mailsvr 143
Trying 10.10.10.84...
telnet: connect to address 10.10.10.84: Connection refused
...then your IMAP server is for some reason not communicating with the
outside. In _that_ case, it may be that IMAP is not permissioned to work
on that machine. The thing to look at is xinetd (/etc/xinetd.conf and
/etc/xinetd.d). There is an easy way to do this, however:
As root at a command prompt, try:
setup
and on the menu it gives you, go to "system services" and then scroll
down to IMAP and make sure it's turned on. OK out of that. If it wasn't
turned on, and you just turned it on, you'll need to restart the xinetd
demon.
Incidentally, you don't _have_ to use the menu - you could create the
appropriate entry in /etc/xinetd.d and restart xinetd.d, but I like the
menu because it doesn't forget to add links or edit appropriate files
etc etc etc...
Hope this all helps you...
Paul.
On Wed, 2002-09-04 at 07:43, David Limon Romero wrote:
> Hello everybody
>
> Some days ago one of my servers was cracked, the intruder used a rootkit
> and did some nasty things on my server, I preferred to reinstall the
> server, it was a RH 7.2, and I upgraded to RH 7.3
>
> When the system was under attack, or some moments later, my users noticed
> that they couldn't enter anymore to read their email via webmail, I was
> using IMP via imap, after reinstalling, imap isn't working yet, my
> firewall rules are set for imap like this:
> ipchains -A input -s 0/0 -d 0/0 143 -p tcp -j accept
> for pop3:
> ipchains -A input -s 0/0 -d 0/0 110 -p tcp -j accept
>
> pop3 is working fine before and after the reinstallation, but imap isn't,
> I tested using an email client: Evolution, using imap, and doesn't work
> with imap, when I configure it for pop3 it works fine.
>
> I don't know what is wrong, in my hosts.[allow|deny] I don't have nothing
> reffering to that services, in my xinetd it is enabled.
>
> I've upgraded my IMP thinking about it could be the problem... it doesn't.
> I'm using imap-2001a-10, I hope someone could help me please.
>
> Thanks in advance.
> David
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Paul Furness
Systems Manager
2+2=5 for extremely large values of 2.
next prev parent reply other threads:[~2002-09-05 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 6:43 imap problem David Limon Romero
2002-09-05 8:50 ` Paul Furness [this message]
2002-09-05 17:11 ` David Limon Romero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1031215823.8926.70.camel@Zebra \
--to=paul.furness@vil.ite.mee.com \
--cc=dlr@mega.net.mx \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.