That is exactly what I want!
Splendid!
Thanx for the feedback on the SMTP AUTH. I've tried enabling SMTP AUTH on the client side using my mail.domain.co.za as an SMTP server and enabling the username and password same as POP, this however failed, then I tried using my root username and password for the mail server, also without any success.
I don't think SMTP AUTH is generally enabled by default on boxen. It's a potential hole, in a way.
The last thing I've tried was to log into the incoming mail server before sending e-mails (an option under Outlook's SMTP AUTH options), also this revealed only failure.
Yeah, that's known as POP-before-SMTP. It generally requires a daemon watching the POP logs, and modifying the MTA config to temporarily allow relay from the IP seen in the POP session. Also unlikely to be enabled by default, and IMHO a hack at best.
If you don't mind, can you please point me in the right direction for enable SMTP authentication either on the mailbox or on the client side or how to get this process working.
Note that it needs to be enabled on both sides: client and server.
What you said about the AUTH makes sense and I feel silly for not thinking of that in the first place
It's impossible for us to know things before we know them. At least in a Newtonian universe. The jury is still out on the whole new Quantum thing
If we can only now get the AUTH to work then my solution is around the corner. Again, thank you for all your help...
OK, let's give it a try.
Again, note that I'm more from a CentOS background. YMMV on SuSE, but it should be roughly the same.
You need to find the sendmail.mc for your system. It could be in
/etc/mail/sendmail.mc. Then, find your sendmail.cf. Likely in the same directory as the sendmail.mc.
For safety, make a copy of the sendmail.cf. Now, it we're lucky, you should be able to do a '
make sendmail.cf' in the directory that contains the sendmail.mc and sendmail.cf. This should regenerate the sendmail.cf, or it might come back with something like "sendmail.cf up to date". If it's the latter, then try '
touch sendmail.mc' and then repeat the '
make sendmail.cf'. This time it should rebuild the sendmail.cf.
If it failed in some other spectacular way, then you might not have the sendmail configuration package installed. On CentOS (3 & 5) it's called
sendmail-cf. Try installing it if that's the case, and retry. If not, we'll need to explore other avenues.
Now that we have a sendmail.cf that's built from the sendmail.mc (with any luck), it's a good time to do a
diff on the newly built sendmail.cf and the sendmail.cf you copied away in an earlier step. You should see no functional differences. There will be changes regarding when the file was built and so, but it should all be comments. If there's no serious functional changes, then we've established that we've got a baseline config from which to take things further.
Try adding the following to the sendmail.mc:
Code:
dnl #
dnl # The following allows relaying if the user authenticates, and disallows
dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS links
dnl #
define(`confAUTH_OPTIONS', `A p')dnl
dnl #
dnl # PLAIN is the preferred plaintext authentication method and used by
dnl # Mozilla Mail and Evolution, though Outlook Express and other MUAs do
dnl # use LOGIN. Other mechanisms should be used if the connection is not
dnl # guaranteed secure.
dnl #
TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')
It might already be in your .mc, and just need to be un-commented. (SIDENOTE: the .mc is an m4 macro file, which treats the characters 'dnl' as a comment indicator. It's read as "delete-until-end-of-line," or something like that. The same does not apply to sendmail.cf)
Rebuild your sendmail.cf ('
make sendmail.cf') and restart/reload sendmail if it was successful. Check the log for errors, if none, try to SMTP AUTH. Note that as per the comments, if your MUA uses AUTH PLAIN, it won't succeed unless you also use SSL/TLS.
Let us know how it goes, and we can take it further (if need be).
