Mailinglist Archive: opensuse (3666 mails)

< Previous Next >
Re: [SLE] SMTP Auth howto for 8.2 Professional.
  • From: Preston Kutzner <grdnwsl@xxxxxxxxxx>
  • Date: Sun, 27 Mar 2005 01:00:41 -0600
  • Message-id: <42465A19.9020209@xxxxxxxxxx>
Sandy Drobic wrote:
> Carlos E. R. wrote:
>> I can not certify that this is the case, but if it is, you have no
>> option. At some point, the developers or suse decided that plain
>> passwords were simply not acceptable, and compiled several packages
>> removing plain password support. If you insist, you have to recompile.
>> I'm not sure if that happened since SuSE 8.2 or 9.0.
> Can't remember for sure if I set up TLS first or if SASL worked before I
> integrated TLS. Though it won't do harm.
> Just put the IP address of your test client in the mynetworks in
> so you won't have to worry about SASL while you set up TLS.
> Then, when you have successfully set up TLS you can return to the task
> to make SASL work.
> If that does the trick please post the solution to the list. (^-^)
> Sandy

Well, I suppose this is a workable solution, but somewhat of a pain from
an administration standpoint. I'm looking trying to set up the internal
mail server the same way as the gateway server (for sending mail anyhow)
so that my users don't have to change their client configurations
depending on whether or not they're in the office or on the road.
Unless this option will work if the client is also configured to use

I guess, seeing as how I haven't set up authentication up until now, I'm
not quite sure if the client software, upon connecting to a server that
doesn't support authentication, will just ignore that fact and try to
send without authenticating.

I guess I'm just looking at this from an administration standpoint, and
a "can I keep my users from 'seeing the man behind the curtain'?"
< Previous Next >