LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Sendmail SMART_HOST + SMTP AUTH Howto (http://www.linuxquestions.org/questions/slackware-14/sendmail-smart_host-smtp-auth-howto-210883/)

SiegeX 07-28-2004 11:39 PM

Sendmail SMART_HOST + SMTP AUTH Howto
 
*********************************************************

This Post is outdated, please see my more complete Howto on SMTP AUTH located here http://www.linuxquestions.org/questi...43#post1144343

**********************************************************









If you are like me and you run your own sendmail server using a dynamic residential IP, chances are 80% of your mail is going to be either bounced or plain out dropped due to SPAM filters running on most enterprise SMTP servers. Fortunatly there is a way around this and that is by relaying all your outgoing mail to your ISP's SMTP server and have them send the mail on your behalf.

Unfortunatly the way to configure sendmail to accomplish this depends on whether or not your ISP's SMTP server requries SMTP AUTH or not. If you are of the lucky type and don't require SMTP AUTH ( most cable modem users seem to belong here) the configuration is fairly simple and Shilo has written an excellent FAQ on how to do this here => http://shilo.is-a-geek.com/slack/sendmail18.html

However for most of us DSL users (and SBC Yahoo DSL is even trickier) we arn't so lucky and we must use SMTP AUTH in order to get our mail to sucessfully relay. After much googling and some trial and error, I finally got it working and I will attempt to break down the necessary steps to get SMART_HOST + SMTP AUTH to work in Slackware 10. These instructions will probably work with 9.1 as well but I don't guarentee it.

Unfortunatly the version of sendmail that comes with Slackware 10 does *not* have SASL support compiled into it, nor does Slackware 10 come with the SASL libraries which is required to get SMTP AUTH to work.
Fortunatly the nice folks over at linuxpackages.net have done the hard work for us and have made slackpacks for sendmail with SASL support and the SASL libraries. You can find these packages here:

sendmail + SASL support
SASL Libraries

Before we do any uninstalling I suggest you make a backup of your current /etc/mail directory by running the following command and storing the tarball in a safe place:
Code:

tar cfvj mail.tar.bz2 /etc/mail/
Now lets make sure our sendmail server isnt running before we uninstall it by running this command (I usually run it twice just to make sure its really stopped) :
Code:

/etc/rc.d/rc.sendmail stop
Now we are in good shape to uninstall the default sendmail package. Please be extra carefull when running this command because Slackware installs two sendmail packages with very similar names. One contains the sendmail binary itself (we will remove this one), and the other contains the sendmail configuration files ( leave this alone!).
Code:

removepkg sendmail-8.12.11-i486-2
After running this command, look for any "Warnings", most likly you will get one for /etc/mail if you have edited any files in that directory. If after you remove the original sendmail and you still have the /etc/mail directory, go ahead and run:
Code:

rm -rf /etc/mail
Don't worry, we made that backup remember!

Now that we have cleanly removed the old sendmail from our system, its now time to install the new sendmail with SASL support along with the SASL libraries. Run the following commands from the directory in which you saved these slackpacks.
Code:

installpkg cyrus-sasl-2.1.19-i486-1sub.tgz
installpkg sendmail-sasl-8.13.0-i486-2sub.tgz

I hope you are still with me because all that was the easy part. Now we are going to configure our sendmail.mc file to enable our new SASL capability along with a few other things.

Before we start changing things its always a good idea to make a backup, so lets make a copy of our default sendmail.mc file by running the following command:
Code:

cd /usr/share/sendmail/cf/cf
cp sendmail-slackware.mc sendmail-slackware.mc.orig

Now that we have a backup, open sendmail-slackware.mc with your favorite editor and lets make some changes!

Below I have copy and pasted my sendmail-slackware.mc file and I have highlighted the parts I changed in green, parts I added in red and parts that are specific to your system in blue. Please read through this carefully and make sure you make all the necessary changes and additions.

Code:

dnl# This is the default sendmail .mc file for Slackware.  To generate
dnl# the sendmail.cf file from this (perhaps after making some changes),
dnl# use the m4 files in /usr/share/sendmail/cf like this:
dnl#
dnl# cp sendmail-slackware.mc /usr/share/sendmail/cf/config.mc
dnl# cd /usr/share/sendmail/cf
dnl# sh Build config.cf
dnl#
dnl# You may then install the resulting .cf file:
dnl# cp config.cf /etc/mail/sendmail.cf
dnl#
include(`../m4/cf.m4')
VERSIONID(`default setup for Slackware Linux')dnl
OSTYPE(`linux')dnl
dnl# These settings help protect against people verifying email addresses
dnl# at your site in order to send you email that you probably don't want:
define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun,goaway')dnl
dnl# Uncomment the line below to send outgoing mail through an external server:
define(`SMART_HOST',`[smtp.sbcglobal.yahoo.com]')dnl
dnl# No timeout for ident:
define(`confTO_IDENT', `0')dnl
define(`confAUTH_OPTIONS', `A')dnl
define(`confAUTH_MECHANISMS', `DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
TRUST_AUTH_MECH(`DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl

dnl# Enable the line below to use smrsh to restrict what sendmail can run:
dnl FEATURE(`smrsh',`/usr/sbin/smrsh')dnl
dnl# See the README in /usr/share/sendmail/cf for a ton of information on
dnl# how these options work:
FEATURE(`authinfo',`hash -o /etc/mail/authinfo.db')dnl
FEATURE(`use_cw_file')dnl
FEATURE(`use_ct_file')dnl
FEATURE(`mailertable',`hash -o /etc/mail/mailertable.db')dnl
FEATURE(`virtusertable',`hash -o /etc/mail/virtusertable.db')dnl
FEATURE(`access_db', `hash -T<TMPF> /etc/mail/access')dnl
FEATURE(`blacklist_recipients')dnl
FEATURE(`local_procmail',`',`procmail -t -Y -a $h -d $u')dnl
FEATURE(`always_add_domain')dnl
FEATURE(`redirect')dnl
dnl# Turn this feature on if you don't always have DNS, or enjoy junk mail:
dnl FEATURE(`accept_unresolvable_domains')dnl
EXPOSED_USER(`root')dnl
dnl# Also accept mail for localhost.localdomain:
LOCAL_DOMAIN(`localhost.localdomain')dnl
MAILER(local)dnl
MAILER(smtp)dnl
MAILER(procmail)dnl

Before we move on, I want to bring special attention to the following line
Code:

define(`SMART_HOST',`[smtp.sbcglobal.yahoo.com]')dnl
If you look closely, you will notice that the name of my ISP's SMTP server is surrounded in brackets [ ]. If you are using Yahoo DSL! then these brackets must be included. Reason being is that Yahoo has decided to spoof their MX record to point to a relay that drops all mail, most likly in attempts to foil zombified spammers. Well, we wan't to ignore this bogus MX record and that's exactly what the brackets do for us.

Now that our config is properly setup, its time to convert it to the sendmail.cf file that we all know and love. But before we do, yup you guessed it, lets back it up first. Run this command
Code:

cp /etc/mail/sendmail.cf /etc/mail/sendmail.cf.orig
Ok now lets convert our new config, run this:
Code:

m4 /usr/share/sendmail/cf/cf/sendmail-slackware.mc > /etc/mail/sendmail.cf
Now that we have our config file in place, all that is left is to tell sendmail what user and password to use when authenticating. To do this we must first create the file /etc/mail/authinfo and then open it up in your editor of choice.

Below is the contents of my authinfo file, to keep with the convention I have highlighted the parts that are specific to your system in blue.
Code:

AuthInfo:yahoo.com "U:siege.x@sbcglobal.net" "P:pAsSWoRd" "M:PLAIN"
AuthInfo: "U:siege.x@sbcglobal.net" "P:pAsSWoRd" "M:PLAIN"

In case its not apparent, the text after U: is the username, after P: is the password and after the M: is the mechinism which is used to login, valid types are DIGEST-MD5, CRAM-MD5, LOGIN, PLAIN. Since I use SBC Yahoo DSL! I know for a fact that they use PLAIN, if you are not sure which one your ISP uses try PLAIN and see if it works, if not give tech support a call.

Note that the second line is almost exactly the same as the first line except its missing yahoo.com and there is a space after the colon. Im not exactly sure why this line is needed, but thats how it was presented to me and since it works, im not about to change it.

Once you have saved your changes to authinfo, we are going to set the correct file permissions on it so that only root can view it. This is a necessary security step as this file contains your password. Run the following command:
Code:

chmod 660 /etc/mail/authinfo
Like most of the files in /etc/mail, we must first convert them over to a .db file so sendmail will recognize our new settings, we will do this to authinfo using the following command:
Code:

makemap hash /etc/mail/authinfo < /etc/mail/authinfo
Remember that backup we made of the /etc/mail directory way in the beginning, well now its time to use it. First lets extract our original files by running this command in the directory which contains the mail.tar.bz2 file.
Code:

tar xfvj mail.tar.bz2
Now if you had sendmail working before this Howto, you definitely made changes to some of the files in /etc/mail and if this is your first time getting sendmail to work, you'll want to at least make changes to access, local-host-names and probably aliases. So now is the time to copy your original files over, or make the neccessary changes if this is your first time.

You'll also want to make sure that all the necessary files have their coresponding .db file so that sendmail will take your changes. Below I listed the commands needed to make the .db files. I recommend running all these commands even if the non-db file is empty.
Code:

makemap hash /etc/mail/access < /etc/mail/access
makemap hash /etc/mail/authinfo < /etc/mail/authinfo
makemap hash /etc/mail/domaintable < /etc/mail/domaintable
makemap hash /etc/mail/mailertable < /etc/mail/mailertable
makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable
newaliases

Note that I highlighted the newaliases command in red because unlike all the other files, the aliases file uses this command to create its db file.

Well, we finally made it, all that is left to do is to restart the sendmail server. PS, sacrificing a virgin to the Linux gods might not be a bad idea at this point ;).
Code:

/etc/rc.d/rc.sendmail start
With any luck, the server should start up cleanly with no errors and you can now send mail through your ISP's SMTP server.

I hope this FAQ was helpfull to more than just me ;). All comments welcome

shilo 07-29-2004 02:58 PM

No replies to this yet? Man, I gotta bump this up. This is one of best tutorials that I have read. I got the smart hosts working on mine already, but I never got around to doing the SASL/SMTP AUTH. Now I've got another thing to add to my "Do this real soon" list.

Again, great job. Hope more people read this.

SiegeX 07-29-2004 03:45 PM

Hey thanks for the bump, your site is what inspired me to post this howto. I should clairify one thing, this howto tells you how to make Sendmail an SMTP AUTH client not a server. You would only need this howto if your ISP's SMTP server requires you to authenticate before you can relay mail through it.

My next task is to set up Sendmail as an SMTP server, it shouldn't be too much difficult now that I have SASL all set up, but then again we are talking about sendmail :)

gargamel 07-29-2004 04:53 PM

Big thanks from me, too!
A couple of days ago I threw away the idea to make SMTP-AUTH working with Sendmail, and went away with Postfix (compiled from source). With your tutorial I would have stuck with Sendmail as this is what Slackware comes with.

As it seems, I'm not the only person needing SASL support in the MTA, so I think it might be helpful to have it compiled into the 'official' Sendmail package delivered with future Slackware versions... That would really make life easier!

gargamel

gargamel 07-31-2004 06:22 AM

Ok, now, I'm giving it a try.
I followed your tutorial step by step, and it all had some effect, but currently it's not
working completely, and I have a few questions. Maybe you have another couple of tips
for me. ;-)

First of all, here's my environment, and how I use it.
I haven't used aliases, and there's no restriction (so far) for users of the local machine
in sending or receiving mail. Currently the machine is operated standalone and connected
to the internet through a DSL modem/switch that also serves as a basic firewall.
I'm using masquerading in order to cut off the local host name from the sender address,
so that alex@orion8.iverbi.de become alex@iverbi.de.
To this end I added a few lines to sendmail.mc.

Towards the end my sendmail-slackware.mc looks like this:

Code:

FEATURE(`redirect')dnl
FEATURE(`masquerade_envelope')dnl
FEATURE(`genericstable',`hash -o /etc/mail/genericstable.db')dnl
GENERICS_DOMAIN(`orion8')
GENERICS_DOMAIN(`orion8.iverbi.de')
GENERICS_DOMAIN(`iverbi.de')
define('confCON_EXENSIVE', 'True')
define(SMTP_MAILER_FLAGS, e)
define('confTO_QUEUEWARN', '16h')
define('SMART_HOST', 'smtp.1und1.de')
dnl# define('TRUST_AUTH_MECH(`AUTH GSSAPI DIGEST-MD5 ')dnl
dnl# define(`confAUTH_MECHANISMS', `AUTH GSSAPI DIGEST-MD5')dnl
define(`confDEF_AUTH_INFO', `/etc/mail/auth/auth-info')dnl
FEATURE(`no_default_msa')dnl turn off default entry for MSA
DAEMON_OPTIONS(`Port=587, Name=MSA, M=E')dnl
dnl# Turn this feature on if you don't always have DNS, or enjoy junk
dnl # mail:
dnl FEATURE(`accept_unresolvable_domains')dnl
EXPOSED_USER(`root')dnl

The lines with genericstable and masquerading are for mapping local users to 'official' mail
addresses. But I wonder what the lines with msa and DAEMON_OPTIONS are good for ---
you don't have them in your configuration, apparently, so for you it's working without them,
it seems.

But probably this all has nothing to do with my three major problems.

***
* PROBLEM 1: I CANNOT SEND MAIL
***

I can't send mail as an unprivileged user. Using Mutt in Slackware 10.0 (unmodified
configuration) I get error messages like these when I press Y (for sending a message):

Code:

collect: Cannot write ./dfi6UCuaZ2003491 (bfcommit, uid=1001, gid=25):
Permission denied
queueup: cannot create queue file ./qfi6UCuaZ2003491, euid=1001, fd=-1,
fp=0x0:
Permission denied

In /var/log/maillog I see this:

Code:

sendmail[3491]: dangerous permissions=40755 on queue
directory /var/spool/clientmqueue/
sendmail[3491]: i6UCuaZ2003491: SYSERR(alex): collect:
Cannot write ./dfi6UCuaZ2003491 (bfcommit, uid=1001, gid=25):
Permission denied
sendmail[3491]: i6UCuaZ2003491: from=alex, size=292, class=0,
nrcpts=1, relay=alex@localhost
sendmail[3491]: i6UCuaZ2003491:  0: fl=0x0, mode=100600:
dev=3/9, ino=202746, nlink=0, u/gid=1001/100, size=292
sendmail[3491]: i6UCuaZ2003491:  1: fl=0x401, mode=100600:
dev=3/9, ino=221027, nlink=1, u/gid=1001/100, size=89
sendmail[3491]: i6UCuaZ2003491:  2: fl=0x401, mode=100600:
dev=3/9, ino=221027, nlink=1, u/gid=1001/100, size=89
sendmail[3491]: i6UCuaZ2003491:  3: fl=0x2, mode=140777: SOCK
localhost->[[UNIX: /dev/log]]
sendmail[3491]: i6UCuaZ2003491:  4: fl=0x1, mode=20666: CHR:
dev=0/11, ino=1695, nlink=1, u/gid=0/0, size=0
sendmail[3491]: i6UCuaZ2003491: SYSERR(alex): queueup:
cannot create queue file ./qfi6UCuaZ2003491, euid=1001, fd=-1,
fp=0x0:
Permission denied

When I try to send mail using mutt as root, I read this in /var/log/maillog:

Code:

sendmail[3508]: dangerous permissions=40755 on queue
directory /var/spool/clientmqueue/
sendmail[3508]: i6UCxOad003508: from=root, size=287, class=0,
nrcpts=1, msgid=<20040730125924.GA3505@orion8.iverbi.de>,
relay=root@localhost
sendmail[3508]: i6UCxOad003508: to=comet.friend@gmx.net,
ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:00, mailer=relay,
pri=30287, relay=[127.0.0.1]
[127.0.0.1], dsn=4.0.0, stat=Deferred:
Connection refused by [127.0.0.1]

Now, Sendmail is pretty mysterious to me, and I really don't understand what's wrong here. Can anyone provide a clue?


***
* PROBLEM 2: I CANNOT RECEIVE MAIL
***
Well, I was able to receive Email before trying to get SASL authentication
configured in Sendmail... I have a file containing all the authentication and
protocol data for my mail accounts. In order to collect my mail I call:

# fetchmail -f /etc/fetchmailrc; sendmail -q

With the standard Sendmail configuration supplied by Slackware 10.0 and
with Postfix compiled from source this was working fine. Now I get this:

Code:

# fetchmail -k -f /etc/fetchmailrc
13 messages for comet.friend@gmx.net
at pop.gmx.net (711694 octets).
reading message comet.friend@gmx.net@pop.gmx.net:
1 of 13 (2149 octets)
fetchmail: SMTP connect to localhost failed
fetchmail: SMTP transaction error while fetching from pop.gmx.net
fetchmail: Query status=10 (SMTP)

In /var/log/maillog I have:

Code:

sm-msp-queue[3510]: i6UCdvU5003430:
to=comet.friend@gmx.net, ctladdr=root (0/0), delay=0  3:04,
xdelay=00:00:00,
mailer=relay, pri=120281, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0,
stat=Deferred:
Connection refused by [127.0.0.1]

sm-msp-queue[3510]: i6UCxOad003508: to=comet.friend@gmx.net,
ctladdr=root (0/0), delay=0  3:37, xdelay=00:00:00, mailer=relay,
pri=120287, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred:
Connection refused by [127.0.0.1]

sm-msp-queue[3510]: i6UCKA3S003366: to=comet.friend@gmx.net,
ctladdr=root (0/0), delay=0  2:51, xdelay=00:00:00, mailer=relay,
pri=210297, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred:
Connection refused  by [127.0.0.1]

sm-msp-queue[3510]: i6UC9k8j003294: to=comet.friend@gmx.net,
ctladdr=root (0/0), delay=0  3:15, xdelay=00:00:00, mailer=relay,
pri=300284, relay=[127.0.0.1], dsn=4.0.0, stat=Deferred:
Connection refused by [127.0.0.1]


What does that mean?



***
* PROBLEM 3: DANGEROUS PERMISSIONS
***

In /var/log/maillog I see this warning many times:

Code:

Jul 30 14:56:36 orion8 sendmail[3491]:
dangerous permissions=40755 on queue directory
/var/spool/clientmqueue/

Now, what would be sensible permission settings for that directory?

Clues, hints, notes and tips to all three problems are most welcome!!!
Thanks for your help in advance!!!

gargamel

SiegeX 07-31-2004 11:32 PM

I dont use mutt because like you, my Sendmail server is on the gateway/firewall box. So most of the time I compose mail on my Windows XP box using Outlook Express. However for testing purposes I ssh'd into my box and ran mutt and tried to send a test email to another account I have and low and behold I came up with the same exact errors as you. I did some searching on google and came upon a guy with the same problem and the response was to make sure that your sendmail permissions are set according to sendmail/SECURITY. Here are the following permissions that need to be set:

Code:

-r-xr-sr-x        root  smmsp        ... /PATH/TO/sendmail
drwxrwx---        smmsp  smmsp        ... /var/spool/clientmqueue
drwx------        root  mail        ... /var/spool/mqueue
-r--r--r--        root  mail        ... /etc/mail/sendmail.cf
-r--r--r--        root  mail        ... /etc/mail/submit.cf

If you look at this closely and compare it to the permissions that are actually on your box, you'll notice that /var/spool/clientmqueue is NOT group writable and this is where the problem is comming from. So the easy fix is to type as root:
Code:

chmod g+w /var/spool/clientmqueue
You might also want to run these commands as well, but they arnt showstoppers like the last one was.
Code:

chmod 444 /etc/mail/*.cf
chown root.mail /etc/mail/*.cf

As far as Masquerading goes, I dont have this anywhere in my sendmail.mc file and the email I send out does NOT have the hostname
portion in the email so I dunno if you even need it?

Also, Ive been busy the last day or so trying to make Sendmail act as an SMTP AUTH Server and again after much googling and trial and errors I came
upon the solution not too long ago. So Im going to post how to do that as well as soon as I get time.

By the way, can you do me a favor and edit your post, particularly the [code] sections such that it doesnt screw up this thread by making each line 2 feet long. Thanks!

shilo 08-02-2004 08:43 AM

Quote:

I dont use mutt
Me either. I use pine. I don't know if it makes a difference for you guys, but I've never had a problem getting pine to work. See if it works for you.

SiegeX 08-02-2004 10:27 AM

I tried it with both pine and mutt and they both give nearly the same error, but the fix I gave above does the job. I also took the liberty to contact the package author for sendmail+sasl and told him about the bug, he contacted me back thanking me and said it will be fixed in the next iteration.

gargamel 08-03-2004 06:21 PM

Quote:

Originally posted by SiegeX
I dont use mutt because like you, my Sendmail server is on the gateway/firewall box. So most of the time I compose mail on my Windows XP box using Outlook Express. However for testing purposes I ssh'd into my box and ran mutt and tried to send a test email to another account I have and low and behold I came up with the same exact errors as you. I did some searching on google and came upon a guy with the same problem and the response was to make sure that your sendmail permissions are set according to sendmail/SECURITY. Here are the following permissions that need to be set:

Code:

-r-xr-sr-x        root  smmsp        ... /PATH/TO/sendmail
drwxrwx---        smmsp  smmsp        ... /var/spool/clientmqueue
drwx------        root  mail        ... /var/spool/mqueue
-r--r--r--        root  mail        ... /etc/mail/sendmail.cf
-r--r--r--        root  mail        ... /etc/mail/submit.cf

If you look at this closely and compare it to the permissions that are actually on your box, you'll notice that /var/spool/clientmqueue is NOT group writable and this is where the problem is comming from. So the easy fix is to type as root:
Code:

chmod g+w /var/spool/clientmqueue
You might also want to run these commands as well, but they arnt showstoppers like the last one was.
Code:

chmod 444 /etc/mail/*.cf
chown root.mail /etc/mail/*.cf


THANKS VERY MUCH. I really appreciate that you took the effort and came up with this quick solution (the research wasn't that quick, I know, as I had asked Vivisimo (which I prefer over Google due to the time-saving pre-categorisation of hits) myself, and was unable to pick the solution you present here. (Well, I'm low on time, otherwise I would have extended my own search of the web, instead of bothering you; one good thing about this, anyway, is the fact that now other people can benefit from this thread).

Quote:


As far as Masquerading goes, I dont have this anywhere in my sendmail.mc file and the email I send out does NOT have the hostname
portion in the email so I dunno if you even need it?

Yes, because my internal domain name is different from my 'official' internet domain.

Quote:


Also, Ive been busy the last day or so trying to make Sendmail act as an SMTP AUTH Server and again after much googling and trial and errors I came
upon the solution not too long ago. So Im going to post how to do that as well as soon as I get time.

Looking forward to it!

Quote:


By the way, can you do me a favor and edit your post, particularly the [code] sections such that it doesnt screw up this thread by making each line 2 feet long. Thanks!

Done.

THANKS again, it really works now the way it should!

gargamel

gargamel 08-03-2004 06:27 PM

Quote:

Originally posted by shilo
Me either. I use pine. I don't know if it makes a difference for you guys, but I've never had a problem getting pine to work. See if it works for you.
I guess it doesn't matter which MUA you use, as long as it does not try to send the message itself, and does no address re-writing. Any mail client that just hands the message over to the MTA will probably run into that problem. So if your Sendmail configuration is like mine, you can see the error message with Pine and KMail, as well as with Mutt, I think.

BTW, I could have opted for a workaround, by configuring Mutt to send mail itself, but that's not what I wanted. And yes, Pine is good too, like Elm. Mutt is the mutt of both, which is why I like it. ;-)

gargamel

Sierra8 08-09-2004 04:12 AM

Thanx...
 
I've been searching the web for a couple of weeks off and on now looking for this info and finally ran across this post. I got my relay up and running in about 10min after reading this.....May you truly "Live Long and Prosper". ;)

SiegeX 08-09-2004 11:25 AM

Im glad you found it usefull and more importantly easy to follow. Im currently working on a "Sendmail Bible" for Slackware 9.1/10 that will not only cover everything in this thread but also how to make Sendmail the SMTP server so that anybody with a valid account can relay through it no matter what network they are on, also I will do my best to try to explain what the various /etc/mail files do with some examples.

Wolfy 09-05-2004 09:32 PM

Wow!!!!!!!!!!!!!:D
Great, absolutely great.
Thank you so much for this info. It works like a charm.:)
Shilo told me to come to your post for this and it was well worth it.
Very detailed, and accurate following your steps exactly allowed me to do what I've been trying to do for months.
Thanks again SiegeX for you help.:)
P.S.
They should put this in the top of the Slackware Distro. forum for easy access and viewing for everybody.

SiegeX 09-05-2004 10:08 PM

Thank you, I appreciate the compliment and am glad everything worked out for you. I should mention that this post is actually rather outdated, and I have posted a new one which comes the same exact information but adds much more onto it, like setting up server-side SMTP AUTH. I also go into detail on how to compile Sendmail yourself to include STARTTLS and SASLv2 support rather than having to download a premade binary.

Please take a look at http://www.linuxquestions.org/questi...43#post1144343

shilo 09-05-2004 10:14 PM

SeigeX-

When are you gonna start a web site with all of your great guides? You've got some of the best guides, and it's not just a bunch of beginner stuff. It's always the stuff that you try to figure out after you get the basics of installing Slackware. Sure would be a good site. I especially like the way you do things the "smart" way, like using checkinstall to install packages so that they are easy to upgrade and remove. A site with your guides would go a long way towards showing people the "right" way to do stuff. It always seems like you take your time in making these guides up.

Just a thought.


All times are GMT -5. The time now is 04:41 AM.