[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: RFC: TLS default enabled/disabled?
From:       Michael Haeckel <Michael () Haeckel ! Net>
Date:       2001-05-18 10:16:44
[Download RAW message or body]

On Friday, 18. May 2001 10:59, Alex Zepeda wrote:
>
> Seeing that kmail implements everything on its own, this doesn't really

I know, you don't like KMail.

> surpise me.  However, configuring stuff on the URL makes a world of hurt
> for people trying to be flexible.  Evidence the imap ioslave in which the
> SASL stuff still isn't implemented properly.

Could you please be more specific, what you understand with "not properly"?

At least I switched that last night to use the sasl code from kdelibs. 
However KSASL does not support LOGIN and ANONYMOUS, therefore basically only 
CRAM-MD5 can be done by KSASL up to now. I don't know, why DIGEST-MD5 does 
not work.

> This is inflexible how?  You can create more than one profile.  This makes
> no sense to me at all.  What's the point of having a profile if you're
> going to put multiple servers under the same name?  The logic behind a
> profile as I see it is to separate stuff into groups of icm/ogm info for a
> given mail account.  And actually, no, it's designed to combine an
> incoming mailbox, with an outgoing service, and add in an email address
> and "real name".  The incoming mbx doesn't have to be POP3 or IMAP, it
> could be a local spool or whatnot.  Similarly the outgoing mail could be
> sendmail or whatever.

Ok, its not really inflexible, but in some cases it is required to enter a 
lot of information several times.

At least I for example have a lot of POP accounts configured of which at 
least 4 I really use actively and also 4 IMAP accounts and a local account.
However I use only one single SMTP server. With the current KEMailsetting 
concept I would have to enter this SMTP server and also my name and e-mail 
address in all something around 12 profiles which is a lot of useless work. 
When I am connected to a different network, where I have to use a different 
SMTP server, I have to change that server in all 12 profiles.

Also my indentities are by no means related to any POP are SMTP servers. I 
simple use them for different kind of stuff, for example KDE mail, sending 
newsletters, etc.

> Basically put up or shut up.  The reason KEMailSettings came into
> existance was because the (profile bits of the) KMail code is ugly, hard
> to understand and inflexible (of course this is pretty much what everyone
> else has told me as well).  Well that, and it was specific to kmail and

Could you please tell me, what is unflexible with that?

> made every effort separate itself from the current KDE configuration
> tools.  If you have a better set of classes that can be extracted from
> KMail, I'm all ears.  A solution that is specific to KMail is not a
> solution at all.  I've yet to see KMail adapt to the KCodecs class...

This stuff is in mimelib currently, as long as no one removes it from there I 
think it doesn't matter, which library we use.

But maybe RFC2045 and RFC2133 encoding stuff could go to KCodecs?

Regards,
Michael Häckel
_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]