www.safe-mail.net" mail server?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Libetpan-users mailing list
Libetpan-users@...
https://lists.sourceforge.net/lists/listinfo/libetpan-users

www.safe-mail.net" mail server?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Libetpan-users mailing list
Libetpan-users@...
https://lists.sourceforge.net/lists/listinfo/libetpan-users

libetpan and SASL

Sorry for not searching the lists, but I get a search server error. If this 
has already been answered, please point me in the right direction.

I would like to know what types of SASL does libetpan support. I need to use 
these types and am not trying to implement anything new but I've been looking 
through the code to get some answers (libetpan-0.49, NOT the latest sources). 
My investigations have lead me to the following conclusions:

POP3 and IMAP: call the pop3_mailstorage_init_sasl and 
imap_mailstorage_init_sasl with NULL for auth_type and related arguments 
which cause the auth_type to fallback to plaintext. Is this correct?

I suppose that SMTP does the same. Am I correct in assuming this?

Thank you for your time!

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: libetpan and SASL

On 7/24/07, Horia Olaru <horia.olaru@...> wrote:
> Sorry for not searching the lists, but I get a search server error. If this
> has already been answered, please point me in the right direction.
>
> I would like to know what types of SASL does libetpan support. I need to use
> these types and am not trying to implement anything new but I've been looking
> through the code to get some answers (libetpan-0.49, NOT the latest sources).
> My investigations have lead me to the following conclusions:
>
> POP3 and IMAP: call the pop3_mailstorage_init_sasl and
> imap_mailstorage_init_sasl with NULL for auth_type and related arguments
> which cause the auth_type to fallback to plaintext. Is this correct?
>
> I suppose that SMTP does the same. Am I correct in assuming this?

SASL supports what cyrus libsasl support.
Note that SASL includes some kind of authentication that are plain
text (or plain text-like).

for POP3 and IMAP, NULL will fallback on plain text authentication at
src/driver level.
at src/low-level, this will not fallback on plain text authentication.

To be consistent with the previous described API behavior, since SMTP
is at src/low-level, this will not fallback on plain text
authentication.

however, the content of the following function should be interesting for you :
int mailsmtp_auth(mailsmtp * session, const char * user, const char * pass)

for plain text login, there is a function available but it is internal to SMTP.
Maybe I should make it public.
static int mailsmtp_auth_login(mailsmtp * session,
    const char * user, const char * pass)

--

-- 
DINH Viêt Hoà

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[ libetpan-Bugs-1760246 ] libetpan 0.50 doesn't compile

Bugs item #1760246, was opened at 2007-07-25 11:59
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429696&aid=1760246&group_id=41064

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Latest stable - libEtPan!
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: anosek (anosek)
Assigned to: Nobody/Anonymous (nobody)
Summary: libetpan 0.50 doesn't compile

Initial Comment:
Compiler says:

mailsmtp.c:1260: error: 'f' undeclared (first use in this function)

I attached the patch.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429696&aid=1760246&group_id=41064

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[ libetpan-Bugs-1675390 ] --with-openssl=DIR make fails, patch for configure.in

Bugs item #1675390, was opened at 2007-03-07 02:31
Message generated for change (Settings changed) made by hoa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429696&aid=1675390&group_id=41064

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Configuration
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: --with-openssl=DIR make fails, patch for configure.in

Initial Comment:
When doing ./configure --with-openssl=/dir where /dir is some valid directory that contains
lib/libssl.so file the configure is successful, but the LDFLAGS does not have -L/dir/lib in
src/Makefile ... 

The following shell script patches the configure.in of libetpan version 0.49 so that you can use the
--with-openssl=/dir and make OK:

#!/bin/bash

patch configure.in << EOF
93a93
> TKKLIBS=""
99a100
>     TKKLIBS="-L\$with_openssl/lib"
116c117,119
<   SSLLIBS="-lssl \$SSLLIBS"
---
>   SSLLIBS="-lssl \$SSLLIBS \$TKKLIBS"
>   AC_MSG_NOTICE("OpenSSL LDFLAGS is \$LDFLAGS")
>   AC_MSG_NOTICE("OpenSSL SSLLIBS is \$SSLLIBS")
EOF

----------------------------------------------------------------------

Comment By: DINH V. Hoa (hoa)
Date: 2007-04-03 20:29

Message:
Logged In: YES 
user_id=201468
Originator: NO

I don't understand why it does not work.
LDFLAGS should be properly set.
If you send a diff, could you use unified diff (-u) ?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429696&aid=1675390&group_id=41064

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[ libetpan-Bugs-1760246 ] libetpan 0.50 doesn't compile

Bugs item #1760246, was opened at 2007-07-25 13:59
Message generated for change (Comment added) made by hoa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429696&aid=1760246&group_id=41064

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: Latest stable - libEtPan!
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: anosek (anosek)
Assigned to: Nobody/Anonymous (nobody)
Summary: libetpan 0.50 doesn't compile

Initial Comment:
Compiler says:

mailsmtp.c:1260: error: 'f' undeclared (first use in this function)

I attached the patch.

----------------------------------------------------------------------

>Comment By: DINH V. Hoa (hoa)
Date: 2007-07-25 18:40

Message:
Logged In: YES 
user_id=201468
Originator: NO

Thanks. This has been committed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429696&aid=1760246&group_id=41064

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: libetpan and SASL

On 7/24/07, DINH Viêt Hoà <dinh.viet.hoa@...> wrote:
> On 7/24/07, Horia Olaru <horia.olaru@...> wrote:
> > Sorry for not searching the lists, but I get a search server error. If this
> > has already been answered, please point me in the right direction.
> >
> > I would like to know what types of SASL does libetpan support. I need to use
> > these types and am not trying to implement anything new but I've been looking
> > through the code to get some answers (libetpan-0.49, NOT the latest sources).
> > My investigations have lead me to the following conclusions:
> >
> > POP3 and IMAP: call the pop3_mailstorage_init_sasl and
> > imap_mailstorage_init_sasl with NULL for auth_type and related arguments
> > which cause the auth_type to fallback to plaintext. Is this correct?
> >
> > I suppose that SMTP does the same. Am I correct in assuming this?
>
> SASL supports what cyrus libsasl support.
> Note that SASL includes some kind of authentication that are plain
> text (or plain text-like).
>
> for POP3 and IMAP, NULL will fallback on plain text authentication at
> src/driver level.
> at src/low-level, this will not fallback on plain text authentication.
>
> To be consistent with the previous described API behavior, since SMTP
> is at src/low-level, this will not fallback on plain text
> authentication.
>
> however, the content of the following function should be interesting for you :
> int mailsmtp_auth(mailsmtp * session, const char * user, const char * pass)
>
> for plain text login, there is a function available but it is internal to SMTP.
> Maybe I should make it public.
> static int mailsmtp_auth_login(mailsmtp * session,
>     const char * user, const char * pass)

In fact, to use a plain text authentication, using SASL for SMTP, you
have either authentication type "LOGIN" or "PLAIN".

--

-- 
DINH Viêt Hoà

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

MIME, attachments, and few more things

Hello,

In a few areas of my code I use the lower level libetpan functions to  
pull data from the IMAP server. However, once I've pulled the data I  
still want to be able to use some of the high level functionality  
because of it's convenience.

In particular, I do a mailimap_fetch, and then I use  
uid_list_to_env_list to convert my results to a mailmessage_list. In  
order to do this I've had to copy the uid_list_to_env_list code into  
my file. Would it be a good idea to expose some functionality in  
libetpan to make it easier to go from the lower level to the higher  
level? Would it be OK to expose uid_list_to_env_list?

Another low level to high level function I've had to copy as well, is
imap_flags_to_flags, would it be possible to expose something like this?

What are your thoughts on this Hoa?

Another question, I noticed that in a number of places,  
mailmime_fields_new_encoding(MAILMIME_MECHANISM_8BIT); is used. Why is  
8BIT always used? What if the client and server doesn't support 8BIT?

I've also been working on adding support in my code for sending  
attachments, and I'm a little bit confused. When I send text I use,  
mailmime_set_body_text, but now I want to send binary data. Can I  
still use mailmime_set_body_text? I can't seem to find another  
function to use in it's place. Of course, I also plan to use base64  
for my mime.

Finally, is there any code in etpanX or in libetpan that is used to  
determine what MIME type should be used for an attachment? IE: Like if  
the file is *.jpg then it will know to use image/JPEG.

Whew, that was a lot of questions.

Thanks in advance,
--
Matt Ronge

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: libetpan and SASL

On 7/30/07, Horia Olaru <horia.olaru@...> wrote:
>
> Thank you for the information. Just to be sure I got it clearly. I want to
> use pop3 and imap from the driver level and want to use SASL. Let's take the
> pop3 (because imap is analogous from what I've seen):
>
>  pop3_mailstorage_init calls pop3_mailstorage_init_sasl with NULL arguments
> for sasl authentication and thus falls back to plaintext. In order to use
> SASL authentication I should call pop3_mailstorage_init_sasl direcly
> providing the argumets for the SASL authentication myself. Am I correct in
> assuming this? If so, then it should be the same for imap.
>
> Also, you said that, in terms of SASL, libetpan supports whatever Cyrus-SASL
> supports. In the pop3driver_types.h as well as in imapdriver_types.h at
> driver level, there are two enums with POP3_AUTH_TYPE_ and respectively
> IMAP_AUTH_TYPE_ which contain varous types of SASL authentication.

Those are deprecated. I should document this in the headers.
Use plain text or whatever value. That was there before really
implementing SASL.

> I would
> like to point out to you that among these types there is none corresponding
> NTLM which according to the Cyrus-SASL website is supported by their
> library. This is just one example and there may also be various other
> supporte authentication types I have not mentioned here that are not
> included in the enums. From what I can tell, either I am not using the
> correct enums for auth types or these need revising. Of course I am talking
> strictly of the version of libetpan 0.49 and in more recent source files,
> this may not be the case.

You have to use a string to describe SASL authentication mechanism.

--

-- 
DINH Viêt Hoà

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/