SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My new project is getting Sendmail to work like I want it to. I'm a big fan of taking the path of least resistance, and so far doing a full Slackware install has provided me with everything I want with only little tweaks to configuration files and such. I'm hoping it will be relatively easy to get Sendmail doing what I want.
I'm running Slackware 9.1, upgraded to -current via SWareT, with the 2.6.5 kernel. Everything is pretty stock. I am using dyndns.org to make sure username.dyndns.org always points to my computer. There's no problem with that, as all of the dyndns.org updating is handled automatically by my router.
Sendmail is started up automatically via /etc/rc.d/rc.sendmail. In /etc/inetd.conf I uncommented the line
(I am hoping this allows me to use encrypted authentication.) I installled cyrus_sasl-2.1.18-i486-1jgr.tgz from http://www.linuxpackages.net . Made a symbolic link from /usr/local/lib/sasl2 to /usr/lib/sasl2 . I rebooted.
Date: Wed, 28 Apr 2004 22:54:18 -0700 (PDT)
From: User <firstname.lastname@example.org>
Oops!!! Have no idea what that's about. Any ideas?
Next, I go to work and try to set up Outlook Express to use my handy-dandy new mail server. I set the SMTP server to username.dyndns.org and the POP3 server also to username.dyndns.org . I click on (sic) "Server requires Authenication" and, feelibng lucky, I click on the (sic) "Server Requires SSL". Doesn't work. I get rid of the (sic) "Server Requires SSL" and try again. Looks like we are in cooking now. So I decide to test it out.
I get the error message "Relaying Denied". DOH!!! So now, here's my questions. Why doesn't the SSL work? What am I missing? I am sure it is simple, but I'm new to the whole sendmail thing. Also, how do I make it so that I can use my mail server to send messages to remote hosts. I don't want to simply add my works host to a list of those allowed, as I would like for anyone I give an account to to be able to use my SMTP server from wherever they are at. The prefered solution seems to be something called SMTP AUTH, but it doesn't seem to be compiled into the Slackware version of Sendmail. I would really prefer not having to recompile Sendmail if at all possible.
Any help would be greatly appreciated. I have tried to give all of the important details, but I would be happy to supply any more necessary to figure out how to get this thing working.
I am having some problems with sendmail and dynamic DNS also. I am using using no-ip.com as my provider. I think that my ISP is blocking port 25 which is common from what I understand. I am not 100% but I am almost sure that is what my problem is. So you may want to look into that!
Thanks for the tip. That isn't my problem, though, as I can verify from my work computer. I just fire up Windows Telnet (or HyperTerminal) and point it to username.dyndns.org port 25. I can connect with either of those to my home computer on port 25. You can check the same for yourself to see if the port is blocked. Another thing you might want to check, if you are using a router, is that port 25 is being forwarded to your linux box.
Thans for trying to help, though. Any other ideas?
I did see a How-to on your exact set-up that I have saved on my other computer, but I do remember that it talked about changes that need to be put in your:
etc/mail/access file and
what changes have you made there?
and when I get to my other system I will post the exact link
I didn't make any changes to the /etc/hosts.allow and /etc/mail/access . My understanding is that I would have to enter the ip addresses or hostnames that are allowed to relay. Though that would be one solution, I am thinking it won't be the optimal one. It gets really messy when you plan on having many roaming users and you don't know what hosts they will be coming from. I'm more than willing to try the HOW-to, though.
Thanks for the post. I'll check it out. Did you try out the telnet to see if your port was actually blocked? Try it from own computer telnet localhost 25 and try it from your work computer telnetuser.no-ip.com25. If it works from your own computer, but not from another, then maybe port 25 is blocked. If it doesn't work from either, port blocking isn't the problem.
Doh!! I had already seen that post. That's where I figured out that I needed to use netconfig to change my hostname and domain name. My problem, and I could be wrong here, is that the article also recommends
to the "access" file
additional step I've found necessary add
Though I believe that this would solve my problem, I believe it would also make my mailserver a huge spam relay. Please let me know if I am wrong in that regard. That has been why I am looking for an alternate secure solution.
Port 25 is blocked from my host. I actually asked them and they said that it was. no-ip.com will except my mail on port 25 and then forward it to another port number that I choose, but I have not played with that yet.
In terms of opening your box up to spam, While I am no sendmail expert by a long shots, I can tell you what I have come accross, and this is another thread that speaks to the antispam thing. I do not know if you have seen this, but it also may help:
Now some more of my problem. I nstalled the cyrus_sasl-2.1.18-i486-1jgr.tgz package, and part of my question was, why doesn't SSL seem to be working. I checked my /etc/var/maillog file and found the following:
Apr 30 13:32:53 username sm-mta: STARTTLS=server: file /etc/mail/certs/smtp.cert.pem unsafe: No such file or directory
Of coarse it doesn't work, I don't have any certificates! DUH on my part. So how so I make certificates so that there IS a file /etc/mail/certs/smtp.cert.pem ?
So part of my problem is solved. Someone pointed out to me that the returned email I received from email@example.com indicates that their mail server just doesn't like me. Still working on the rest, though. Any advice always appreciated.
So I'm still looking for answers. Here's what I did next.
/usr/bin/saslauthd -a shadow
Don't really know if that is something I was supposed to do or not. It made three files in /var/state/saslauthd , namely mux, mux.accept, and saslauthd.pid . I notice that when I reboot, those three files are gone. Am I getting somewhere? Didn't seem to change anything for me.
I don't believe it sbcglobal.net problem. Because, I'm also trying to setup sendmail on my Fedora Core 1 system. I got my to send out mail to my firstname.lastname@example.org account. The only problem I have is when my email arrived to my sbcglobal account. My email address show this "cojo@JServer.jndipietri.com.gateway.2wire.net"
Thanks for the tip. I haven't updated this thread in awhile. I've got sendmail working pretty much how I want it. My problem with sbcglobal.net was resolved by enabling relaying. The problem was that sbcglobal.net doesn't accept mail from my server. They do accept mail from my ISP's mail server (comcast.net) though, so I just had to set up relaying.
correction to the sbcglobal.net problem. I do get Fatal Error problem with sbcglobal.net now. I called SBC about it and they don't know what to do. I also found lot of people have the same problem and still don't have a fix to it yet.
BTW, I get my email address problem fixed. All I have to do was change my hosts file to this:
Is bad, Sendmail checks this file to to find out which domain it is responsible for, in your case mydomain is it's host name and .com is the domain it is responsible for which is all of .com, open relay, not good, should read
To over come this add your domain name to /mail/local-host-names
as 'mydomain.com' no www
You should also have an entry in /mail/access
Plus any IP addresses of local machines, if you have any, as 192.168.0.5 RELAY obviously use your own IP's
You should'nt need to modify, except /mail/sendmail.mc, any other Sendmail files, don't forget to navigate to your mail directory, in my case /etc/mail and type 'make' to make the files readable to Sendmail
Your problem with sbcglobal.net could be a DNS issue Sendmail checks every email it sends against DNS if the domain name can't be resolved it won't send it
In a terminal enter
]$ dig sbcglobal.net mx
See if your DNS servers can resolve the domain, if they can't that's your problem
Sorry if I've hijacked your thread, just trying to help