Sign up members		Welcome to SMACKMYPAPPY.COM your one stop for email
	Message Board		Top Sites		outlook express outlook express outlook express
	Welcome to smackmypappy.com.      One of the best deals on the internet!! Full walkthru with outlook express and SMACKMYPAPPY.COM.... We are always trying to make     things nicer for you the user.  We aren't one of those big companies     that want your money and leave you with little service options.  Sign     up today for only $2 a month, with your membership you will get: 1 pop email address something@smackmypappy.com , access to our smtp authentication server.  20 Megs of email space.  Access to the members area.  The chance to earn free months with our referral program.  And we promise to keep bringing more features to you very soon, some are already in the works!

Welcome to smackmypappy.com.  One of the best deals on the internet!! Full walkthru with outlook express and SMACKMYPAPPY .... We are always trying to make things nicer for you the user.  We aren't one of those big companies that want your money and leave you with little service options.  Sign up today for only $2 a month, with your membership you will get: 1 pop email address something@smackmypappy.com access to our smtp authentication server. 20 Megs of email space. Access to the members area. The chance to earn free months with our referral program.  And we promise to keep bringing more features to you very soon, some are already in the works!		Welcome to SMACKMYPAPPY.COM your one stop for email ... Currently we are working on full walkthrus for all the major email clients, we currently show you how to setup outlook express , outlook express is one of the most popular mail clients being used today. The walkthru shows you how to setup outlook express so that you can use your smtpauth server that is provided for you. What that means to you is that you will be able to authenticate no matter what connection you are using with your smackmypappy smtp authentication server. Outlook express isn't the only mail client that does this feature we will also in the near future have walkthrus for outlook , eudora , netscape , and any others that people request us to setup . This walkthru along with any of the others will make setting up your smackmypappy email account easy . Combined with the cheap cost of 2 dollars a month makes smackmypappy.com one of the best deals on the internet....If you are seing this message it means that you do not have the pluggin needed to view this item you might want to think about updating your system to fully enjoy this site.				Smackmypappy.com Email Service, one of the best email service around - 20 meg email service     Smackmypappy.com Email hosting - email services - email hosting services - email service providers     Welcome to SMACKMYPAPPY.COM your one stop for email service
	members		Sign Up		Help

			Full walkthru with outlook express and SMACKMYPAPPY.COM
	Please take time to vote for us at the following sites.....

his is a site that I really thought was a good resource for Outlook Express check it out.

Outlook Express Backup Wizard The world's most popular utility to create complete backup copies of Outlook Express database.

You are here: Outlook Express Backup Wizard

Download the Free Trial Version: oebw.exe (858 KB)   Buy the Full Version - $39.95 Click Here to Buy Now !   Product Information Homepage Screenshots System Requirements Version History Ordering Buy Now - $39.95 Money Back Guarantee Volume Discounts Educational Discounts Link to Us & Get a Free Copy Support Online Help Contact Us Resources Related Sites Outlook Express FAQ     ThunderCloud.Net The largest free email stationery archive: www.thundercloud.net

What is Outlook Express Backup Wizard? Outlook Express Backup Wizard is the world's most popular software utility to create backup copies of the Outlook Express email database. Viruses, software failures, or power outages can destroy your Outlook Express and all your email. Outlook Express Backup Wizard helps you secure your Outlook Express: in the event of a crash, the wizard will bring it back to life in no time! Backup Outlook Express in minutes: Email messages, folders and attachments Address book Email and news accounts Identities Message rules Signatures Click Here to Download Free Trial Version:     How Can the Wizard Secure My Outlook Express? The wizard creates a complete backup copy of your Outlook Express. This backup copy is the only way to restore your Outlook Express after a crash. The backup file contains everything in your Outlook Express: email messages, attachments, identities, address book, message rules, list of blocked senders, accounts, and signatures. If your Outlook Express crashes, the wizard will restore it from the backup file. The procedure is very simple: run the wizard, select the backup file, and choose which items you want to restore (email messages, accounts, rules, etc). In a minute, your Outlook Express is up and running! The wizard also helps you move Outlook Express data between computers. Use the wizard to backup Outlook Express on the first computer, copy the resulting backup file to your second PC, and use the wizard again to restore the backup file there.   Features of Outlook Express Backup Wizard The wizard backs up everything in your Outlook Express: Email and news messages (including Hotmail messages) Email folder structure and attachments Identities Address book Message rules Blocked senders list Email and news accounts (including Hotmail accounts) Signatures (including signatures stored in external files) Features: Easy-to-use interface that guides you through the process steps: see screenshots Password-protected backup files Automatic Zip compression of backup files Support for Outlook Express 5.0, 5.01, 5.5, and 6.0 Ability to backup multiple identities to a single backup file Ability to append the backed-up messages to your current Outlook Express database   Download the Free 30-Day Trial Version: oebw.exe (858 KB) Click Here to Buy the Full Version: $39.95 - Buy Now!   Note: Microsoft® Outlook® Express is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Outlook Express Backup Wizard is a product of QSX Software Group and is not affiliated with Microsoft in any way. QSX Software Group is independent from Microsoft Corporation and not affiliated with Microsoft in any manner. Copyright © 2002-2003 QSX Software Group. All Rights Reserved.

Also this page is a really great informative page!

Computer users today have no shortage of information, but finding a specific piece of information can be difficult. Information resides in paper calendars or planners, e-mail folders, personal information managers and group schedulers, collaboration applications, custom browsers, file servers, and on the Internet and intranets — everywhere and anywhere, but not often enough where it can be found when users need it. To compound the problem, with multiple tools, users must learn to use different applications and commands for finding, entering, displaying and organizing information. They must remember not only where they last saw a piece of information but also what application they were running. With the Microsoft® Outlook® 97 messaging and collaboration client, Microsoft Corp. delivered a breakthrough product, uniquely addressing these requirements and combining industry-leading support for the following capabilities:Electronic mail, Personal calendar and group scheduling,Personal information such as contacts and tasks, Custom collaboration and information-sharing applications, Outlook helps users organize, find and view all of this information — all in one place — using a consistent interface. Outlook 2000 builds upon this product vision, particularly in the areas of Internet standards support, ease of use and simplicity, and support for collaborative solutions. Outlook 2000 offers industry-leading e-mail and collaboration features when used with Internet-based messaging systems and even more advanced functionality when used on a business intranet with Microsoft Exchange Server.

How to set up SMTP AUTH

Last Update June 24, 2003

What is this?

This is a simple "how to." This is for anyone out there who has ever wanted to simply add authentication to sendmail. All this page will do is show you one way to configure sendmail and Cyrus SASL libraries to set up a mail server that requires client authentication to send e-mail. This is not a detailed tutorial of either sendmail nor Cyrus SASL. For more detailed sendmail help, I strongly recommend going to the Official Sendmail Website or the comp.mail.sendmail newsgroup. For more in-depth discussion of SMTP AUTH with sendmail, try http://www.sendmail.org/~ca/email/auth.html.

It's somewhat ironic that I recommend that latter site (http://www.sendmail.org/~ca/email/auth.html). It was because of this site that I decided to write this site. Anyone I talked to about SMTP AUTH referred me to this site. I mean absolutely no disrespect to Claus Aßmann, but I read and re-read this site many times. It was only marginally helpful.

To Claus' credit, I ascribe the reason that it was only marginally helpful to the fact that I was unfamiliar with Cyrus SASL and only at a beginner-to-intermediate level with sendmail. Claus is clearly a sendmail guru of highest degree. This page is submitted as an SMTP AUTH Guide for the Rest of Us. At the simplest level, this is simply "What I Did."

So,... what are you assuming?

If this is just about what I did, I used the following ingredients:

• SuSE Linux 7.3 (with the 2.4.19 kernel)
• sendmail 8.12.9
• cyrus-sasl 1.5.28
• db 3.1.17 (The Berkeley DB)
• either Microsoft Outlook Express 5.0.2 (for MacOS) or Microsoft Entourage v.X

Get to the point, will ya?!

Okay, okay! What I set out to do was to set up sendmail to use SMTP authentication to allow users to relay mail on my server. I run a family server, and my family is spread out over several ISPs. Allowing relays based on IP addresses wasn't really practical (especially since most of them were dial-up). For simplicity, I wanted to use the same username and password accounts that my family uses to access their mail (via POP3). These accounts are just the standard /etc/passwd and /etc/shadow logon accounts (using, say, useradd to have created them). I didn't want to try anything fancy (say, SSL, or anything like that). I wanted simple.

This is how I did it:

Step 1 - Check to see what's already installed

At this point, I had already installed SuSE Linux 7.3 (with the 2.4.19 kernel) on the machine I was working on. I had also installed db 3.1.17. I mention the Berkeley DB because this has come up in a couple of e-mails. I swear that I read somewhere in my mad pursuit of this project that Berkely DB 4.x does not play nice with cyrus-sasl 1.5.28. I can't find this now. If anyone out there has a reference URL for me, let me know. Anyway, I didn't realize that this had an affect on my install, but it appers to have had. I did not compile the source for this. I simply installed the db-3.1.17 RPM (as well as the db-devel-3.1.17) RPM that came with SuSE. I'm sure you could download the source and compile it, but I'm not sure where to get that, and I've never done it before.

The key here is, don't use Berkeley DB 4.x with the other product versions I've mentioned. I can't verify where I read this, but I'm pretty sure, without doing any kind of special patching, it won't work.

Also, check your version of GCC. According Lawrence Sheed, Cyrus-SASL does not compile properly with gcc version 3.2 (which comes with RedHat 8). He succeeded by upgrading to gcc 3.2.2. I used gcc 2.95.3 (the version that comes with SuSE Linux 7.3).

Step 2 - Build the Cyrus SASL libraries

Download the source for the last version of the Cyrus SASL 1.x libraries (yes, the 2.x libraries are out, but I didn't use those; as I understand it, without additional tricks, the 2.x libraries are not compatible). This can be done at ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-sasl-1.5.28.tar.gz

Again, I put the cyrus-sasl-1.5.28.tar.gz file in /usr/local/src. I then extracted the archive by typing tar xzvf cyrus-sasl-1.5.28.tar.gz

I entered the archive - cd /usr/local/src/cyrus-sasl-1.5.28 - and I followed the steps specified in the INSTALL file. The important element here is that AUTH LOGIN functionality is not included by default (A big thank you goes to Ken Murchison from the comp.mail.sendmail newsgroup for pointing this fact out to me). This is important because Microsoft Outlook and Entourage cannot use AUTH PLAIN or any of the other default methods. I configured it with this command:

./configure --prefix=/usr --enable-login

I chose the /usr prefix so that it would install the libraries in /usr/lib/sasl (which is where SuSE normally installs them). I originally tried using an RPM from SuSE to install the Cyrus SASL libraries, but again, the RPM's compilation does not support AUTH LOGIN either.

I finished the compilation by typing these two commands:

make
make install

Step 3 - Set up sendmail

Download the source for the latest version of sendmail. This can easily be done via ftp at ftp://ftp.sendmail.org/pub/sendmail/sendmail.8.12.9.tar.gz.

I put the sendmail.8.12.9.tar.gz file in /usr/local/src. I then extracted the archive by typing tar xzvf sendmail.8.12.9.tar.gz

I entered the archive - cd /usr/local/src/sendmail-8.12.9 - and I followed the steps specified in the INSTALL file.

First you need to create a site.config.m4 file. This is just a text file that you can create with whatever editor you like (vi, pico, emacs, etc.). With whatever you put in there, you will at the very least need to add these lines:

APPENDDEF(`conf_sendmail_ENVDEF', `-DSASL')
APPENDDEF(`conf_sendmail_LIBS', `-lsasl')
 

Notice the strange way that the quotes are used. They are single quotes, but there are actually open (`) and close (') quotes. The open quote is to the left of the "1" key on most keyboards. The close quote is to the right of the ":" key on most keyboards. I saved this file in /usr/local/src/sendmail-8.12.9/devtools/Site/

Second, you need to build sendmail. I did this by typing:

cd /usr/local/src/sendmail-8.12.9/sendmail
sh Build
 

Remember, if you're rebuilding sendmail, type sh Build -c

Third, I created a sendmail.mc file. I'll let you read up at sendmail.org as far as what should be added to this file, but you must have these three lines in there:

define(`confAUTH_OPTIONS', `A')dnl
define(`confAUTH_MECHANISMS', `LOGIN PLAIN')dnl
TRUST_AUTH_MECH(`LOGIN PLAIN')dnl
 

Fourth, I built the sendmail config files by typing:

cd ../cf/cf
sh Build sendmail.cf
 

Fifth, I installed the sendmail config files by typing sh Build install-cf

Lastly, I installed sendmail by typing:

cd /usr/local/src/sendmail-8.12.9/sendmail
sh Build install
 

One more note, you should not have sendmail configured to run as an unprivileged user for this configuration. Sendmail typically defaults to run as root, which, for this situation, will be fine. If you really want to run sendmail as a different user, you will need to make sure that this user has privileges to read the /etc/shadow file. Thanks to Ryan Alder for making a note of this.

Step 4 - Configure the SASL libraries for sendmail

Here, you need to create a configuration file for SASL. Once again, use your favorite text editor. This file needs to be named Sendmail.conf (notice the capital 'S'; that's deliberate), and it must be placed in your SASL libraries directory. In my compile, this directory was /usr/lib/sasl. If you didn't specify a prefix when you compiled SASL, they are likely to have been put in /usr/local/lib/sasl.

The Sendmail.conf only needs one line:

pwcheck_method: shadow

Step 5 - Try it out

If you haven't already, start (or restart) sendmail. You're now ready to try authenticating to send mail. I typically used my e-mail clients in my situation. Both Outlook Express and Entourage allow you to set up SMTP authentication by choosing Accounts from the Tools menu. In the Accounts window, double-click on the account you wish to change. In the Edit Account window at the bottom is the Sending mail section. You will have already entered your mail server's name or IP address in the SMTP server: field. Click on the "button" that says Click here for advanced sending options.

In the sub-window that appears, click on the check box entitled "SMTP server requires authentication." For convenience, click on the radio button that says "Use same settings as receiving mail server." Then, click back in the Edit Account window, and click "OK" to save your changes. Feel free to close the Accounts window at this point.

Now, send a message from your client. If it reaches its destination, life is good. If it doesn't, check your logs (for me, it is /var/log/mail).

You can also try to test it manually. Here is a dialog from my system (properly garbled for security reasons). The green text is what you would type. The blue text is what the server displays.

> telnet localhost 25
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 something.fake ESMTP Sendmail 8.12.9/8.12.9/SuSE Linux 0.6; Wed, 2 Apr 2003 15:13:01 -0700
EHLO localhost
250-something.fake Hello localhost [127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH LOGIN PLAIN
250-DELIVERBY
250 HELP
AUTH LOGIN
334 VXNlcm5hbWU6
a4msl9ux
334 UGFzc3dvcmQ6
ZvVx9G1hcg==
235 2.0.0 OK Authenticated
MAIL FROM: me@something.fake
250 2.1.0 me@something.fake... Sender ok
RCPT TO: you@nowhere.land
250 2.1.5 you@nowhere.land... Recipient ok
DATA
354 Enter mail, end with "." on a line by itself
This is a test
.
250 2.0.0 h12MD1qV026715 Message accepted for delivery
QUIT
221 2.0.0 something.fake closing connection
Connection closed by foreign host.

The line a4msl9ux is a user name encoded in Base64. Likewise, the line ZvVx9G1hcg== is the password to that account also encoded in Base64. As most people don't know their usernames or passwords encoded in Base64 off the top of their heads, you can either use ed64 by downloading the contents of that link and compiling it with cc -o ed64 ed64.c OR you can simply go to the Base64 Encoder and Decoder web page and use their interface (Major thanks go to Bryan Halvorson for finding this information for me, and for not giving up on me).

If you really want to just use your client, though, you can watch this same output by stopping sendmail and starting it using these tags:

sendmail -O LogLevel=14 -bd -X /tmp/output.log

(A grand round of applause is due to Claus Aßmann for giving me this information)

If you use this method, you'll want to stop sendmail after you've tried to send from your client (and start it up again the way you normally would, if you want). This generates a log file located at /tmp/output.log and it should show a very similar output to the manual example I gave earlier.

Final thoughts

If you still need help, feel free to e-mail me. Personally, I don't feel that I would be nearly as big a help as the comp.mail.sendmail newsgroup, but I would be happy to help where I can.

If you notice any spelling or grammatical errors, please e-mail me. I'm fairly anal about such things, and would like to keep this looking good.

If you notice any technical errors in my data, please e-mail me, but keep in mind that I never intended this to be an all-encompassing tutorial. These may not be appropriate instructions for someone running, say, Solaris 2.5 and sendmail 8.8. I specified precisely what I used, and it works. That's the only certification you get.

I don't want any lectures about features that are available that I didn't talk about. I didn't talk about them for a reason. I either don't know how to use them or don't care to know how to use them.

I don't want any lectures about security. AUTH LOGIN uses Base64 encoding to transfer the username and password. Is this as secure as, say, SSL? Absolutely not. Is it better than setting up sendmail as an open relay? Absolutely! Besides, as I alluded earlier, my users also use POP3 to retrieve their e-mail which, of course, sends their username and password information in clear text, so the security of the Base64 encoding for my SMTP AUTH is the least of my concerns.

I don't want any religious lectures (e.g., sendmail vs. postfix, MacOS vs. Windows, etc.). You may think that you can convince me of the "errors of my ways," but the fact that you should keep in mind is: I don't care. Save your rants for your website.

Lastly, I sincerely hope that this helps people to lock down their sendmail servers. I am a great loather of spam, and I will do anything that I can to help eliminate the proliferation of such garbage. I hope that there is at least one person that found this useful, and that this saves someone the month-long struggle that I endured.

SMTP authentication for Qmail

While SMTP authentication?

Almost all SMTP servers do not permit SMTP relay - it is defense again spam. If somebody alternate between more IP providers (typically  "free Internet" dialup access users) and needs SMTP server for sending mail, he can:

• either set different SMTP server in his mail client configuration every time when he change dialup number 
• or set one SMTP server with SMTP authentication (more comfortable solution)

Administrator troubles with SMTP auth 

It seems that SMTP authentication is the best solution for users and for administrators too (users stop require to permit relay). I use SMTP authentication for Qmail from www.nimh.org (http://www.nimh.org/hacks/qmail-smtpd.c). It works fine (thanks to author), but I discovered some problems:

1. Netscape mail client try authentication whenever it find that SMTP server support SMTP AUTH (from EHLO dialog) and asks user for password. Client use the same login as for POP. There is not possible to set anything. 
   MS clients MS Outlook and Outlook Express are different - it is possible to set everything (use authentication or not, use the same login and password as for POP or another...).
   Problems with Netscape mail clients users after SMTP authentication was implemented:
   • user must enter one more password. Also user must enter password when SMTP authentication is not necessary (his computer is in domain from which SMTP relay is permitted - e.g. our LAN).
   • if user use different POP server (e.g. remote) and SMTP (our) server with different login names, he can not send mail when SMTP authentication on our SMTP server is implemented
2. Netscape SMTP servers supports SMTP authentication. It seems to me that similar as Netscape client Netscape server try authentication whenever it find that second SMTP server supports SMTP AUTH. Because server does not know any password and use blank login (or anything else, e.g. "root"), our server ends SMTP connection. Probably not only Netscape servers know SMTP authentication today.
   Problems with Netscape servers (a another SMTP servers which supports SMTP authentication on sending):
   • it try authentication every time. Because it fails, our server ends SMTP session. Because SMTP session start at all, Netscape server does not try our MX server and leave message in queue. After few days server send message back as undelivered.
   • these servers administrators are not able to change their server behavior (or they do not know about this problem). And our users do not receive their mail.

Solving

I use SMTP authentication for Qmail from www.nimh.org (http://www.nimh.org/hacks/qmail-smtpd.c) with minor changes:

1. Server hide its SMTP AUTH support (in EHLO command) when relay is permitted for remote computer (it solve problems with Netscape clients from LAN - the clients do not try to authenticate and do not ask user for password). 
2. When SMTP AUTH fail, server do not terminate connection - only waits 2 seconds and do not permit relay for messages (it solve problems with Netscape servers).
3. Server write to syslog about authentication.

Modified qmail-smtpd.c

qmail-smtpd.c for Qmail 1.03

Installation

• install Qmail 1.03
• replace file qmail-smtpd.c with modified version, compile Qmail and install again (make setup check)
• install and test checkpassword.
  • Checkpassword exists in more variations and depends on type and configuration of your unix server.
  • Original version and description: http://cr.yp.to/checkpwd.html.
  • Alternative Checkpassword Implementations: http://qmail.ruk.cuni.cz/#checkpassword.
     (version for OSF/Dec UNIX/Compaq Tru64 with enhanced security: http://www.cuni.cz/~vhor/qmail/checkpassword.c  )
• modify qmail-smtpd startup. In case of
  • inetd: use anything like
    "smtp stream tcp nowait qmaild /usr/sbin/tcpd /var/qmail/bin/tcp-env /var/qmail/bin/qmail-smtpd /bin/checkpassword /bin/true"
  • Xinetd:
    ###############################
    #/etc/xinetd.d/qmail-smtp
    ###############################
    service smtp
    {
     socket_type = stream
     wait = no
     user = qmaild
     server = /var/qmail/bin/tcp-env
     server_args = -R /var/qmail/bin/qmail-smtpd sever.com /bin/checkpassword /bin/true
     nice = 10
    }
    (thanks cameron (at) omigos (dot) ca)
     
• test:
  • From computer, which has not rely permitted, try
    • telnet server 25
    • EHLO
    • 250 AUTH=LOGIN should be in answer
  • From computer, which has not rely permitted, try send mail from client with SMTP authentication enabled (Netscape use authentication whenever, ms outlook need settings)
    • look at syslog
      • Jun 22 08:43:42 servername qsmtpd: auth ok for login: login  - OK
      • Jun 21 16:38:24 servername qsmtpd: auth fail for login: login - bad password
      • no record - client did not use authentication

Known problems

• modified qmail-smtpd.c tests (for security reason), if  login contains only alphanumeric characters. Unknown characters it replace with "X". In case that your login names contains other characters ("-" etc.) or you are using vpopmail, modify or comment this part of source code:
  /* vhor */
  for(i=0;i<strlen(smtpauthlogin);i++) {
  if (! isalnum(smtpauthlogin[i]) ) {
  smtpauthlogin[i] = 'X';
  }
  }
  
  (thanks Jonas Pasche jonas (at) domke (dot) de for warning).
   
• if authentication does not works, check permissions of your program for password check:
  • /bin/checkpassword: owner root.nofiles, permissions 4110 (run only owner and group, suid bit)
  • vchkpw must be SUID'ed and GUID'ed, owner vpopmail.vchkpw
    (thanks Joan Valduvieco joan (at) laigu (dot) net)

SMTPAuth

Overview

SmtpAuth is a small program which is to be used in conjunction with email clients that do not support smtp authentication, but whose smtp server requires it. It runs in the background on the client's machine, accepting incoming unauthenticated smtp requests, and forwarding these to the smtp server, adding in authentication using a username and password supplied during installation. It runs as a service on Windows NT, or as a startup program on Windows 95/98.
Note : SmtpAuth only supports the plain-text authentication method. SmtpAuth assumes that the server will advertise that it supports plain-text authentication in reponse to a ehlo command.

Download

SmtpAuth 1.04 - Windows NT/2000/2003/95/98/ME/XP (62 kbytes)

Installation

1. SmtpAuth consists of a single executable file smtpauth.exe. Download this, and run it either by double clicking on it or by typing "smtpauth" at the command prompt. It then prompts your mail server name, followed by your user name and password. Pressing < Enter > for the mail server name will use the default value of "mail".
2. Once SmtpAuth is running, you must change your email client settings to indicate that your outgoing (smtp) mail server is now "127.0.0.1"
3. Note: while SmtpAuth is installed, it will automatically restart whenver your computer restarts.
4. To uninstall SmtpAuth, just run SmtpAuth again, and choose the delete option.

Configuration

In order to change the settings at a later date just run SmtpAuth again and choose the reconfigure option. By default, SmtpAuth assumes that your smtp mail server will be on port 25. If this is not the case, you will find a file "smtpauth.ini" in your windows system directory ("winnt\system32" on nt, or "windows\system" on win95) . Change the line that reads "mail_port 25" to whatever port your smtp server is on. SmtpAuth also assumes that it should listen on port 25 on the system that it is running on. This can also be changed by modifying the "port 25" setting in "smtpauth.ini". After modiying anything in "smtpauth.ini", you must restart SmtpAuth. This can be achieved by running SmtpAuth and choosing the restart option.

 

Example of What SmtpAuth does

The following are 2 examples of what a client might say and receive from SmtpAuth, together with what SmtpAuth actually sends on to the server. After the authentication has taken place, SmtpAuth simply forwards whatever the client and server say on to each other. SmtpAuth will hold off from responding to the initial helo, or ehlo command until it has received confirmation from the server that the authentication was successful.

Client to SmtpAuth Data, Example 1:
220 matt.netwin.co.nz DSMTP ESMTP Mail Server
helo matt
250 matt.netwin.co.nz. Hello matt (127.0.0.1)
.
.
.

Client to SmtpAuth Data, Example 2:
220 matt.netwin.co.nz DSMTP ESMTP Mail Server
ehlo matt
250-matt.netwin.co.nz. Hello matt (127.0.0.1)
250-ETRN
250-DSN
250 HELP
.
.
.

Here is what SmtpAuth would say and receive from the server for either of the above cases:
220 matt.netwin.co.nz DSMTP ESMTP Mail Server
ehlo matt
250-matt.netwin.co.nz. Hello matt (127.0.0.1)
250-ETRN
250-DSN
250-AUTH PLAIN LOGIN
250 HELP
auth PLAIN AHRlc3QxAHRlc3Q=
235 Authentication succeeded
.

outlook