LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Adding accounts in the integrated pop3 server of slackware 13 (https://www.linuxquestions.org/questions/linux-newbie-8/adding-accounts-in-the-integrated-pop3-server-of-slackware-13-a-876381/)

Norwegian 04-21-2011 12:52 PM
Adding accounts in the integrated pop3 server of slackware 13
 
Quote:
Originally Posted by http://salcedoweb.com/rds/server.html
Uncomment or add line in /etc/inetd.conf:

# Post Office Protocol version 3 (POP3) server:
pop3 stream tcp nowait root /usr/sbin/tcpd /usr/sbin/popa3d
How do I add an account so I can access my mailbox from M$ Outlook from a Windows 7 machine?
I am planning on using my ISPs smtp server for sending mail.

Or is there anything else I should be aware of?

http://www7.pic-upload.de/21.04.11/ieg6wv3qx6g.jpg

bathory 04-23-2011 08:24 AM
Hi,

Every user you add in your system can use pop3 through a client like Outlook to access his mailbox.
You said that for outgoing mail you'll use your isp smtp server, but in order to receive mail, you'll need the email for your domain to be forwarded to your smtp server (the one in the screenshot). This can be done in the name server that is authoritative for your domain

Regards

Norwegian 04-27-2011 03:25 AM
Is there an easy to follow step by step instructions on how to do this?

bathory 04-27-2011 04:59 AM
If you want to add a user in Slackware, run:
Code:
adduser
and follow the instructions

Norwegian 04-29-2011 02:21 AM
I getting further, now I get this problem when trying to mail my server from gmail.com:

Code:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.7.1 <user@domain.com>... Relaying denied (state 14).

bathory 04-29-2011 03:23 AM
Take a look again at my 1st post.
You need to setup:
1. The dns that is authoritative for your domain, so the MX record points to your smtp server
2. Your smtp server to accept mail for your domain.

Norwegian 04-29-2011 11:47 PM
@bathory

Thanks for trying to help me, but i need more detailed instructions on how to do this.

Quote:
Originally Posted by http://www.linuxquestions.org/questions/linux-newbie-8/slackware-mx-record-28450/#post131793
You just add it to your domain. In your domain config file (usually somewhere in /var/named), after NS declarations, add a new line, something like
MX 10 yourmailserver
The 'named' directory does only contain a directory 'caching-example'.
Could you tell me in detail how to do this like.
1. Go to the following directory.............
2. In there you find a file names ..... and change the following text, and or add the following .........

Or is there a tutorial on how to do this somewhere?

bathory 04-30-2011 03:26 AM
Hi,

I don't think you're running the authoritative dns for your domain. This dns is the one (or more) that you've defined when you registered your domain. You can check it here
Maybe you can access if through a control panel to add/change records. Or you need to talk with the admin of that dns server

Norwegian 05-04-2011 02:41 PM
Code:
Work in progress!

Follow IntoDNS on Twitter


Category        Status        Test name        Information send feedback
Parent        Info        Domain NS records        Nameserver records returned by the parent servers are:

dns2.registrar-servers.com.  ['173.224.125.12', '69.64.46.77', '85.25.136.102']  [TTL=172800]
dns1.registrar-servers.com.  ['209.239.127.155', '69.16.244.24']  [TTL=172800]
dns3.registrar-servers.com.  ['188.138.96.213', '67.228.121.98']  [TTL=172800]

a.gtld-servers.net was kind enough to give us that information.
Pass        TLD Parent Check        Good. a.gtld-servers.net, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Pass        Your nameservers are listed        Good. The parent server a.gtld-servers.net has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
Pass        DNS Parent sent Glue        Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
Pass        Nameservers A records        Good. Every nameserver listed has A records. This is a must if you want to be found.
NS        Info        NS records from your nameservers        NS records got from your nameservers listed at the parent NS are:

dns1.registrar-servers.com  ['69.16.244.24', '209.239.127.155']  [TTL=1800]
dns5.registrar-servers.com  ['95.211.9.35']  [TTL=1800]
dns3.registrar-servers.com  ['67.228.121.98', '188.138.96.213']  [TTL=1800]
dns2.registrar-servers.com  ['69.64.46.77', '173.224.125.12', '85.25.136.102']  [TTL=1800]
dns4.registrar-servers.com  ['184.171.163.90']  [TTL=1800]

Pass        Recursive Queries        Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
Pass        Same Glue        The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
Information        Glue for NS records        INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
67.228.121.98
85.25.136.102
69.16.244.24
You can fix this for example by adding A records to your nameservers for the zones listed above.
Pass        Mismatched NS records        OK. The NS records at all your nameservers are identical.
Pass        DNS servers responded        Good. All nameservers listed at the parent server responded.
Pass        Name of nameservers are valid        OK. All of the NS records that your nameservers report seem valid.
Pass        Multiple Nameservers        Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Pass        Nameservers are lame        OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Error        Missing nameservers reported by parent        FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
dns4.registrar-servers.com
dns5.registrar-servers.com
Pass        Missing nameservers reported by your nameservers        OK. All nameservers returned by the parent server a.gtld-servers.net are the same as the ones reported by your nameservers.
Pass        Domain CNAMEs        OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass        NSs CNAME check        OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass        Different subnets        OK. Looks like you have nameservers on different subnets!
Pass        IPs of nameservers are public        Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
Pass        DNS servers allow TCP connection        OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
Pass        Different autonomous systems        OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Pass        Stealth NS records sent        Ok. No stealth ns records are sent
SOA        Info        SOA record        The SOA record is:
Primary nameserver: dns1.registrar-servers.com
Hostmaster E-mail address: hostmaster.registrar-servers.com
Serial #: 2008080813
Refresh: 10001
Retry: 1801
Expire: 604801  1 weeks
Default TTL: 3601
Pass        NSs have same SOA serial        OK. All your nameservers agree that your SOA serial number is 2008080813.
Pass        SOA MNAME entry        OK. dns1.registrar-servers.com That server is listed at the parent servers.
Pass        SOA Serial        Your SOA serial number is: 2008080813. This appears to be in the recommended format of YYYYMMDDnn.
Pass        SOA REFRESH        OK. Your SOA REFRESH interval is: 10001. That is OK
Pass        SOA RETRY        Your SOA RETRY value is: 1801. Looks ok
Pass        SOA EXPIRE        Your SOA EXPIRE number is: 604801.Looks ok
Pass        SOA MINIMUM TTL        Your SOA MINIMUM TTL is: 3601. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 3601 is OK.
MX        Info        MX Records        Your MX records that were reported by your nameservers are:

10  eforward3.registrar-servers.com  205.251.134.191 (no glue)
10  eforward2.registrar-servers.com  69.160.33.82 (no glue)
10  eforward1.registrar-servers.com  50.30.32.27 (no glue)

[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Pass        Different MX records at nameservers        Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
Pass        MX name validity        Good. I did not detect any invalid hostnames for your MX records.
Pass        MX IPs are public        OK. All of your MX records appear to use public IPs.
Pass        MX CNAME Check        OK. No problems here.
Pass        MX A request returns CNAME        OK. No CNAMEs returned for A records lookups.
Pass        MX is not IP        OK. All of your MX records are host names.
Pass        Number of MX records        Good. Looks like you have multiple MX records at all your nameservers. This is a good thing and will help in preventing loss of mail.
Pass        Mismatched MX A        OK. I did not detect differing IPs for your MX records.
Pass        Duplicate MX A records        OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Pass        Reverse MX A records (PTR)        Your reverse (PTR) record:
27.32.30.50.in-addr.arpa ->  eforward1.registrar-servers.com
82.33.160.69.in-addr.arpa ->  eforward2.registrar-servers.com
191.134.251.205.in-addr.arpa ->  eforward3.registrar-servers.com
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW        Info        WWW A Record        Your www.dataduden.com A record is:
www.dataduden.com  [81.166.129.183]
Pass        IPs are public        OK. All of your WWW IPs appear to be public IPs.
Pass        WWW CNAME        OK. No CNAME

Processed in 1.752 seconds.
What does this have to do with anything?

bathory 05-04-2011 04:33 PM
Hi,
Quote:
10 eforward3.registrar-servers.com 205.251.134.191 (no glue)
10 eforward2.registrar-servers.com 69.160.33.82 (no glue)
10 eforward1.registrar-servers.com 50.30.32.27 (no glue)
The above means that these are the smtp servers that can accept mail for your domain. You should edit this though your registrar and change it to point to your server.

Norwegian 05-13-2011 12:35 PM
Quote:
Originally Posted by bathory (Post 4346677)
Hi,
The above means that these are the smtp servers that can accept mail for your domain. You should edit this though your registrar and change it to point to your server.
The smtp server accepts mail? Aint that server for _sending_ mail?
Is there a script, or some easy to install software that does this work for me..?
I'm getting confused about this.

bathory 05-13-2011 03:28 PM
Hi,

The smtp server accepts mail and it can either deliver it locally if the recipient is local, or forward (send) it to the mail server of the recipient.
Slackware's default smtp server is sendmail. Doing a google search, you can find lots of howtos about configuring sendmail as a MX server for a domain.
Regarding a config tool, the only one that comes in mind is webmin.

Since you're new to this stuff, I suggest you to look at google apps and use google as the smtp server of your domain. So you don't have to bother configuring sendmail.

Regards


All times are GMT -5. The time now is 11:15 PM.