The only problem is when I use netstat -l | grep -e "domain" -e "54" i
get "warning, got duplicate tcp line.
a netstat -l gets me the folowing.
Is this ok?
yes. BIND simply bound :-) to all IP's.
-ken
___
CentOS mailing list
CentOS@centos.or
Ken,
Thanks.
I followed you instrustions and it installed fine.
I started up bind and can now dig @127.0.0.1 whatever.com and get a
response.
The only problem is when I use netstat -l | grep -e "domain" -e "54" i
get "warning, got duplicate tcp line.
a netstat -l gets me the folowing.
[EMA
You are correct, resolve.conf does list my isp's dns 250.171.3.65 which
is qwest. The internal windows workstations also point o the isp's dns
server.
Can I setup a cashing dns server on the mail server itself??
Absolutely. Assuming that none is running already:
#> netstat -l | grep -e "domai
Ken,
You are correct, resolve.conf does list my isp's dns 250.171.3.65 which
is qwest. The internal windows workstations also point o the isp's dns
server.
Can I setup a cashing dns server on the mail server itself??
PS: I just wanted to say thanks to everyone who has helped me so far.
-jr
Jason,
This has nothing to do with AUTHORITATIVE dns. I'm speculating this
is a problem with your choice of RECURSIVE (caching) name servers.
Realize, however, that without being on the box and looking at your
configuration, all I can do is speculate.
Mail .medvoice.com actually
Rick,
The reason i used top was because I noticed that mailscanner and smtpd
were always on the list UNLESS the issue was occurring.
I will try ps + grep next time as well.
As for the ips they resolve quickly however they are all listed in
/etc/hosts as we do not have an internal DNS.
-jr
[
ps: I forgot to mention,
the number of users does not seem to have an impact on this.
I was here over the weekend when there is no one but me here and still
saw the issue.
-jr
Lanny Marcus wrote:
On 09 August 2007, Ken Price <[EMAIL PROTECTED]> wrote:
I'll give my two cents and
Mail .medvoice.com actually resolves to the mail server inside through
port forwarding.
It's not really named that just everything going to the mail ports ends
up there.
Would DNS still be an issue for sending internal mail.
I ran top during one of these unresponsive email spats and noticed th
On 09 August 2007, Ken Price <[EMAIL PROTECTED]> wrote:
> I'll give my two cents and retire for the evening. I've tried
> multiple times from 3 different locations (Atlanta & Seattle) to
> connect to MAIL.MEDVOICE.COM on port 25 ... which I'm assuming is your
> problem server. I get inconsis
Jason Ross spake the following on 8/9/2007 4:56 PM:
> Scott,
>
> Sorry 'bout that I thought I was missing something.
> spamassassin-3.0.6-1.el4
>
> Just have 3 more questions.
> Should I use the graphical update or just yum update?
> Also are there any updates I should be concerned about?
> Shoul
Should I use the graphical update or just yum update?
Also are there any updates I should be concerned about?
Should I update now, or after I resolve the smtp issue?
RHEL has a decent GUI, however you will be better off ignoring it and
getting familiar with administering the box via the comman
Scott,
Sorry 'bout that I thought I was missing something.
spamassassin-3.0.6-1.el4
Just have 3 more questions.
Should I use the graphical update or just yum update?
Also are there any updates I should be concerned about?
Should I update now, or after I resolve the smtp issue?
Thank you for
Ken,
I dont know that there is a specific error, it acts the same as if you
put in a bad password.
Once I restart postfix, it goes right through.
jason
Ken Price wrote:
I am currently running
Centos 4.3
postfix-2.2.10-1.RHEL4.2
mailscanner-4.57.6-1
Your OS is out of date, but not
Jason Ross spake the following on 8/9/2007 4:18 PM:
> I am currently running
> Centos 4.3
> postfix-2.2.10-1.RHEL4.2
> mailscanner-4.57.6-1
>
> The problem is I'm not yet smart enough to patch it quickly.
>
> But would patching it fix the issue or create more???
>
> If so how would I roll back q
I am currently running
Centos 4.3
postfix-2.2.10-1.RHEL4.2
mailscanner-4.57.6-1
Your OS is out of date, but not terribly in the grand scheme of
things. This list probably remembers running CentOS 4.3 for quite a
bit and it was rock solid. I'd start with the SMTP error message.
I am currently running
Centos 4.3
postfix-2.2.10-1.RHEL4.2
mailscanner-4.57.6-1
The problem is I'm not yet smart enough to patch it quickly.
But would patching it fix the issue or create more???
If so how would I roll back quickly?
Scott Silva wrote:
Jason Ross spake the following on
Jason Ross spake the following on 8/9/2007 3:36 PM:
> No I have not. We are a small company and the owner freaks out when it
> comes to any down time of email so I have just maintained the original
> install.
> No updates.
Can you give some more details, like OS type/version, postfix version,
MailS
No I have not. We are a small company and the owner freaks out when it
comes to any down time of email so I have just maintained the original
install.
No updates.
Scott Silva wrote:
Jason Ross spake the following on 8/9/2007 1:39 PM:
Hey all,
For the last 8 months I have been run
Jason Ross spake the following on 8/9/2007 1:39 PM:
> Hey all,
>
> For the last 8 months I have been running a postfix / mail scanner setup
> based on Johnny Hughes' excellent tutorial.
> For the firs 7 months I have had no issues. This past month I have been
> having instances where the user gets
19 matches
Mail list logo
