RE: pop won't authenticate my password

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Wow ...
this thread has just blown into something gargantuan hasn't it?  :D

Ed (first Ed), you might want to give us some history about mccorduck.ws so
we can understand the bigger picture.  And also let us know what it is you
want to do. For example:

1) where/how did you register the name?
2) is the company you registered the name with going to house your primary
DNS?  Or is that something you wnated to do on your machine ? If the answer
is that you don't know, that's fine.  We might be able to answer from
knowing the answer to #1
3) did you want to serve the mail from your own machine? (and house the
incoming mail of mccorduck.ws on your own machine?)

>From all the emails, it seems the answer to 3) would be yes.

It looks like network solutions whois only recognizes that the domain is
taken but it doesn't seem like there is any name server entries set up.  On
nslookup from my machine it recognizes that there is a mccorduck.ws. address
(24.24.15.155)  and the NS record points back to itself.  So my guess is
that you have only just registered your name and somehow managed to get an
address record in there and that's it.  This means that mccordck.ws. has not
been set up to recognize mail seriving or DNS serving.

The NS record I had from nslookup for your domian (from my work PC) was:

mccorduck.ws. IN NS mccorduck.ws.

anyway, what this means is :

To serve and read mail from your machine you'd need to
1a) register your machine mccorduck.ws. as a valid nameserver
OR
1b) find someone to be your primary nameserver (there are a lot of companies
who will do this, including possibly the company you registered your domain
with)

If 1a) and not 1b), then
2) run a nameserver (most likely BIND) on your machine


Finally, you also need to:
3) Include an MX record for your domain to point to your machine.
4) then run sendmail (which it seems you are doing) to accept mail as
mccorduck.ws. (Cw definition)
5)then run pop3 so you can access the email (this is surprisingly the
easiest part)

It seems like only step 5 is  finished and step 4 is half-way finished
(sendmail is running, not sure if it will accept as mccorduck.ws.).  And it
also seems like steps 1 through 3 have not been attempted yet.

Let me know if this sounds correct. Sorry for the confusing style of my
post.  Hopefully it makes sense.


Ben Yau




-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux