Re: [Evolution-hackers] Panel notification applet (bug #127516) C interface

2004-08-23 Thread Plzik Milan
On Mon, Aug 23, 2004 at 11:41:29AM +0800, Not Zed wrote:
 
 Hi Plzik,
 
 On Sun, 2004-08-22 at 12:35 +0200, Plzik Milan wrote:
 
  Hi:)
  A few days ago I started writig the email panel notification applet. I'd 
  like to ask a few questions about the notification applet class interface. 
  (there is a request in bugzilla that it would be nice to hook other things 
  into it (comment #5) - f.x. for calendar notifications (#8)).
 
 Well, we already have a mostly finished crack at this bug from Miguel
 Angel Lopez Hernandez.  We are really only waiting for 2.0 to get out
 the door before we can commit it, since 2.0 code is in feature freeze.
 It just needs some minor changes to fit in with the plugin architecture.
 
 So keep that in mind with the comments below.  With the plugin system
 its possible to have both running anyway; of course it would help if the
 plugin stuff was finished but unfortunately it is still work in
 progress.
 

I think I'll stop fixing this bug, I would just do duplicate work. Anyway, 
I think the acceptance of patch (even if waiting for code freeze) should 
be mentioned in the bugzilla some way. Thanks for advices, anyway.

OT: My first name is Milan, surname Plzik. But at our school, everyone has 
his/her name in format surname name. I don't know why ...

Milan Plzik

P.S.: I think this is not my last email to this list. GNOME programming 
makes quite fun, so I'll try to find another bounty to fix:)
___
evolution-hackers maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers


[Evolution-hackers] ssl always/when-possible/never etc proposal

2004-08-23 Thread Jeffrey Stedfast




Since there was confusion again today on the difference between always/whenever-possible, I guess it's a good time to bring this up.

I was thinking in the future, we could re-work the UI for the SSL options to look something more like this:



This would make the backend logic a little simpler too, because we would haven't try and guess which SSL method to use based on trial-and-error.

DanW suggested that we default to Whenever Possible rather than Never when we get around to changing the UI.

this'd require some changes to all of the remote mail providers (smtp, imap, pop, nntp, etc) but I don't think it'd take more than a day or 2 to make the necessary code changes and test everything.

it'd also require an additional setting option in the uri/e-account stuff, but that should be trivial to add too?

Jeff





-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED] - www.novell.com








evo-ssl.png
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature


Re: [Evolution-hackers] ssl always/when-possible/never etc proposal

2004-08-23 Thread Dan Winship
On Mon, 2004-08-23 at 16:06 -0400, Jeffrey Stedfast wrote:
 Since there was confusion again today on the difference between
 always/whenever-possible, I guess it's a good time to bring this up.
 
 I was thinking in the future, we could re-work the UI for the SSL
 options to look something more like this:

   Use SSL: [Whenever Possible]
   [ ] This server uses the SSL port rather than STARTTLS

Most users will have no clue what that means though.

 This would make the backend logic a little simpler too, because we
 would haven't try and guess which SSL method to use based on trial-
 and-error.

It would be nice if it could just try both possibilities the first time
you connect and then just remember (in gconf) which one worked, and use
that in the future. The same thing could be done for authentication
type. Instead of making the user choose between plaintext and CRAM-MD5
and NTLM and LOGIN, just assign a strength level to each SASL type, and
have the provider try each of the available ones in decreasing order of
strength until one of them works (only throwing CANT_AUTHENTICATE if
they all fail). Then remember the one that works and use that in the
future. (This is bug 10522.)

-- Dan


___
evolution-hackers maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers


Re: [Improved patch!] Was: Re: [Evolution-hackers] [PATCH] Fix OpenSSL certificate validation in Evolution (1.4.4 and 1.4.6)

2004-08-23 Thread Anton Altaparmakov
On Mon, 23 Aug 2004, Jeffrey Stedfast wrote:

 the OpenSSL code no longer even compiles and is no lonegr available in
 configure.in. that said, I'll add that function call if for some reason
 this code is ever revived, but that is highly doubtful.

Great, thank you.

Best regards,

Anton

 On Sun, 2004-08-22 at 06:45 +0100, Anton Altaparmakov wrote:
  On Sat, 21 Aug 2004, Jeffrey Stedfast wrote:
   On Thu, 2004-08-19 at 05:05, Anton Altaparmakov wrote:
On Thu, 2004-08-19 at 09:07, Frederic Crozat wrote:
 Le jeu 19/08/2004 à 09:54, Anton Altaparmakov a écrit :
  Further to my previous post, here is a much improved and this time final
  patch replacing the previous one (attached).  It changes the call from:
  
  SSL_CTX_load_verify_locations(ssl_ctx, NULL, /etc/ssl/certs);
  
  to:
  
  SSL_CTX_set_default_verify_paths(ssl_ctx);
  
  Which asks the OpenSSL library to use the default path for the
  certificates (configured at compile time when building openssl so on
  each distribution it can be different, for suse it is /etc/ssl/certs and
  for redhat it is /usr/share/ssl I am told).
  
  This thus removes the hardcoded /etc/ssl/certs and is hence much better
  and always going to work on a system with a properly installed openssl
  library.
  
  I know at least some of you Ximian Developers don't like OpenSSL, but
  other people, in particular distributions like it, and you will find
  that distros always compile evolution with openssl support, like it or
  not.  It also happens to work beautifully with my patch so why not
  include it?  If you don't use openssl fine, but at least allow everyone
  else to use it without having to apply a patch first...  Thank you.
 
 Ahem, I think at least RH, Mdk and Debian are not using OpenSSL enabled
 Evolution. You should check facts before writing such claims..

Well, having just checked RedHat 9.0 I can tell you for a fact that both
RedHat 9.0 and SuSE 9.0/9.1 all use OpenSSL for their Evolution builds. 
That covers the two largest distributions so my statement was not wrong.
   
   OpenSSL is *only* used by OpenLDAP in those distributions. SuSE (which,
  
  Sorry but this is wrong.  Both RedHat 9 and SuSE 9.x Evolution RPMS use 
  OpenSSL and NOT Mozilla-NSS.  That is how they are built and that is how 
  they work.  Look at the source and binary rpms, look at what the binary 
  rpms depend on, use strace to see what libraries are loaded on 
  evolution startup.  I _have_ done all this and guess what, OpenSSL is 
  used.
  
  Also, if you were right, how can you explain that adding my patch fixes 
  the certificates problem when using SuSE 9.0 (I haven't managed to 
  compile the SuSE 9.1 source rpm for evolution 1.4.6 on SuSE 9.1 yet!), 
  even though it only touches the Evolution OpenSSL code?
  
   btw, is part of Novell) uses Mozilla-NSS, as does RedHat 9.0, Fedora
   Core 1  2, and Mandrake.
  
  I know Ximian and SuSE are now Novell.  We have a full sitelicense for 
  Novell (because of using Netware extensively) and hence are probably going 
  to get all Ximian and SuSE products for free.  (-:  (Novell are still 
  debating exactly what to do there...  So far we know we have full 
  sitelicenses for the SuSE OpenExchange server but we are waiting to hear 
  about the rest.)
  
   OpenSSL will not work for more than just what your patch covers (I'll
   look it over on monday) - for starters, the code is unmaintained and
   doesn't even compile anymore.
  
  Makes Evolution 1.4.4 work anyway...
  
  Best regards,
  
  Anton

-- 
Anton Altaparmakov aia21 at cam.ac.uk (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/  http://www-stu.christs.cam.ac.uk/~aia21/

Re: [Evolution-hackers] Panel notification applet (bug #127516) C interface

2004-08-23 Thread Not Zed




On Mon, 2004-08-23 at 18:58 +0200, Plzik Milan wrote:


On Mon, Aug 23, 2004 at 11:41:29AM +0800, Not Zed wrote:
 
 Hi Plzik,
 
 On Sun, 2004-08-22 at 12:35 +0200, Plzik Milan wrote:
 
  Hi:)
  A few days ago I started writig the email panel notification applet. I'd 
  like to ask a few questions about the notification applet class interface. 
  (there is a request in bugzilla that it would be nice to hook other things 
  into it (comment #5) - f.x. for calendar notifications (#8)).
 
 Well, we already have a mostly finished crack at this bug from Miguel
 Angel Lopez Hernandez.  We are really only waiting for 2.0 to get out
 the door before we can commit it, since 2.0 code is in feature freeze.
 It just needs some minor changes to fit in with the plugin architecture.
 
 So keep that in mind with the comments below.  With the plugin system
 its possible to have both running anyway; of course it would help if the
 plugin stuff was finished but unfortunately it is still work in
 progress.
 

I think I'll stop fixing this bug, I would just do duplicate work. Anyway, 
I think the acceptance of patch (even if waiting for code freeze) should 
be mentioned in the bugzilla some way. Thanks for advices, anyway.


Ok, sorry about any work you did on this. Its really up to the contributors themselves to update the bugs or even 'own' them like the rest of the developers do, although i don't know if any have been very good at it.



OT: My first name is Milan, surname Plzik. But at our school, everyone has 
his/her name in format surname name. I don't know why ...



Sorry Milan!



P.S.: I think this is not my last email to this list. GNOME programming 
makes quite fun, so I'll try to find another bounty to fix:)


Cool, I hope the plugin stuff will make adding things to evolution itself a lot easier too.




-- 






Michael Zucchi [EMAIL PROTECTED]
born to die, live to work, it's all downhill from here
Novell's Evolution and Free Software Developer








attachment: zed-48.small.jpg


Re: [Evolution-hackers] ssl always/when-possible/never etc proposal

2004-08-23 Thread Not Zed




On Mon, 2004-08-23 at 16:06 -0400, Jeffrey Stedfast wrote:

Since there was confusion again today on the difference between always/whenever-possible, I guess it's a good time to bring this up.

I was thinking in the future, we could re-work the UI for the SSL options to look something more like this:



This would make the backend logic a little simpler too, because we would haven't try and guess which SSL method to use based on trial-and-error.


This seems very technical/meaningless, i dont even know what it means.

IMHO we should have SSL and TLS separated, they're different. whenver possible makes absolutely zero sense technically or visibly since it doesn't relate to what it appears to be at face value.

i.e. something to the effect of:

Security: None / TLS / SSL

which is what we really mean.

Users will NEVER understand the difference since the system is ill-defined and ambiguous to start with. But having 'ssl' when we really mean 'tls' will never help. If we use the ssl port rather than starttls then we're doing ssl, not tls.

I think adding another option will just make it more confusing, it should be in the dropdown menu.

DanW suggested that we default to Whenever Possible rather than Never when we get around to changing the UI.

this'd require some changes to all of the remote mail providers (smtp, imap, pop, nntp, etc) but I don't think it'd take more than a day or 2 to make the necessary code changes and test everything.

it'd also require an additional setting option in the uri/e-account stuff, but that should be trivial to add too?

Jeff





-- 
Jeffrey Stedfast
Evolution Hacker - Novell, Inc.
[EMAIL PROTECTED] - www.novell.com








-- 






Michael Zucchi [EMAIL PROTECTED]
born to die, live to work, it's all downhill from here
Novell's Evolution and Free Software Developer








attachment: zed-48.small.jpg


evo-ssl.png
Description: Binary data


Re: [Evolution] Exporting addressbook

2004-08-23 Thread Andre Klapper
Am Sonntag, den 22.08.2004, 23:04 -0500 schrieb Jerry Sloan:
 Is it possible to export my contact list to a csv file?

hi jerry,

mark all your contacts (e.g. by ctrl+a) and then select save as vcf
file from the main menu.

cheers,
andre
-- 
 mailto:[EMAIL PROTECTED] | failed!
 http://www.iomc.de


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Re: [Evolution] Exporting addressbook

2004-08-23 Thread guenther

  Is it possible to export my contact list to a csv file?
 
 mark all your contacts (e.g. by ctrl+a) and then select save as vcf
 file from the main menu.

Which will save in VCard (vcf) rather than the desired Comma Separated
Value (csv) format...


'$prefix/libexec/evolution/1.5' advertises to be able to export to csv
format, although it failed for ma on a quick test. See --help for more
options.

As you are using Evolution 1.4.6, simply check if this tool is in your
path (it was for me) or you will need to adjust the path to the
executable.


Beside this, there are likely a couple of tools out there which can
convert vcf to csv format. If your target tool/application doesn't
handle VCard files natively.

HTH

...guenther


-- 
char *t=[EMAIL PROTECTED];
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128  (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

___
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution


Re: [Evolution] problem with red carpet and a proxy

2004-08-23 Thread guenther

  You can grab any needed packages from the Ximian FTP server directly and
  install it using 'rpm' -- if Ximian provides packages for your distro.
  If not (and it doesn't look like it to me), you are left to RH's
  updates...
 
 Doesn't appear to have anything for RH Enterprise, and unfortunately,
 the only updates that I can find from RH are for security updates.
 
 Guenther, thanks for your response.

You're welcome.

What's the version you want to upgrade to, anyways? You are currently
using 1.4.5, latest stable version is 1.4.6 -- 1.5.x versions are still
development releases, which likely will not be released for RH
Enterprise Workstation. 2.0.0 will be the next stable major release.

You might want to have a look at the 1.4.6 release notes to see, if it
fixes any issues you encounter:

  http://www.gnome.org/projects/evolution/release_notes/1.4.6.shtml

...guenther


-- 
char *t=[EMAIL PROTECTED];
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128  (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

___
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution


Re: [Evolution] Forward Attachments

2004-08-23 Thread Wise, Jeremey
On Mon, 2004-08-23 at 19:02 +0200, guenther wrote:

   And the origin of any
 attachment will be clear without confusion.
  
  Thanks. this actually explains it better.
 
 I tried to explain this more than once... ;)
 
 You even can set Forwarding as Attachment as default forwarding action
 in the Settings.
 
 
  Just for my understanding...
  Was this changed in 1.5 from 1.4.6.
 
 Dunno when exactly the attachment handling changed. But IIRC it where
 only minor changes, most of the logic still is the same as it was for a
 couple of versions.
 
 
  I am just a little use to the way
  Outlook did things and I thought that 1.4.6. use to do it in a format
  where text forward/replies were inline while attachments always moved
  with the mail. This is apparently not (no longer) the case. Why is
  that?
 
 I already expressed my opinion about attachment handling...
 
 It doesn't make any sense at all to resend attachments when replying --
 cause the one you are replying to just sent you the very same
 attachment. So why would I want to send it back?
 
 When forwarding inline/quoted, the origin of attachments simply is not
 clear. Whereas forwarding as attachment leaves the original mail
 entirely unaltered and isn't ambiguous about the origin of any
 attachment.
 
 Forwarding as Attachment is the way to go, IMHO.
 
 ...guenther
 
This clarified what I needed. It makes sense once it is explained. Hold
over thought process from my MS Outlook days.

Thanks,
___
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution


Re: [Evolution] Exporting addressbook

2004-08-23 Thread Andre Klapper
Am Montag, den 23.08.2004, 17:41 +0200 schrieb guenther:
   Is it possible to export my contact list to a csv file?
  
  mark all your contacts (e.g. by ctrl+a) and then select save as vcf
  file from the main menu.
 
 Which will save in VCard (vcf) rather than the desired Comma Separated
 Value (csv) format...

hi guenther,

right like always... :-)
i should have read the message a few more times than i actually did
before answering it.
that means no more answering user questions directly after coming home
from work, andre! ;-)

thanks,
andre

-- 
 mailto:[EMAIL PROTECTED] | failed!
 http://www.iomc.de


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


[Evolution] Replying -- Add an additional line ?

2004-08-23 Thread Troy C
When replying to email, the cursor/prompt is immediately at the O of :::
On Mon, 2004-08-23

Is there a way to insert an additional line break so instead you get:::

cursor
On Mon,..


vice:::
cursorOn Mon, 


Thanks,
TroyC

___
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution


Re: [Evolution] Replying -- Add an additional line ?

2004-08-23 Thread guenther

 When replying to email, the cursor/prompt is immediately at the O of :::
 On Mon, 2004-08-23
 
 Is there a way to insert an additional line break so instead you get:::
 
 cursor
 On Mon,..
 
 vice:::
 cursorOn Mon, 

Nope. Unfortunately, this string is hardcoded in current versions --
hardcoded with the implied meaning of different strings for different
locales, that is.

There is no way to customize this string in any way including line
breaks and cursor positions ATM, short of patching and re-compiling.

This has been discussed some times already, and a custom setting for
this probably will be an option in Evolution -- eventually...


To counter any discussion regarding top posting and friends: Please see
the archived flame wars first, before going that route... ;-)

...guenther


-- 
char *t=[EMAIL PROTECTED];
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;il;i++){ i%8? c=1:
(c=*++x); c128  (s+=h); if (!(h=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

___
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution


Re: [Evolution] POP3 not downloading all messages

2004-08-23 Thread Paul Harouff




On Mon, 2004-08-23 at 10:52 +0800, Not Zed wrote:

There are two alternatives:
1. don't do this, but then you get duplicate downloads. on a really flakey connection you may never (in a practical sense) get all your mail and get lots of duplicates.
2. delete the old ones always. this assumes we can trust the info, otherwise you could remove non-duplicate mails.

I'm leaning toward 2, but it complicates the code a bit.


The only problem is it looks to me that these mails were never downloaded. Of the 22, I read three on the web which I want to save by downloading them and archiving. The others I never read.

Paul
Huntsville, AL




Re: [Evolution] POP3 not downloading all messages

2004-08-23 Thread Paul Harouff




On Mon, 2004-08-23 at 22:43 -0500, Paul Harouff wrote:

On Mon, 2004-08-23 at 10:52 +0800, Not Zed wrote:

There are two alternatives:
1. don't do this, but then you get duplicate downloads. on a really flakey connection you may never (in a practical sense) get all your mail and get lots of duplicates.
2. delete the old ones always. this assumes we can trust the info, otherwise you could remove non-duplicate mails.

I'm leaning toward 2, but it complicates the code a bit.


The only problem is it looks to me that these mails were never downloaded. Of the 22, I read three on the web which I want to save by downloading them and archiving. The others I never read.



I should also mention that I am job hunting and some of these messages were from head-hunters that I did not read for over a week because they didn't download.

You should always default to being conservative. It's always safer to get a duplicate e-mail than to lose a potential job opportunity.

I WOULD STOP USING EVOLUTION IF IT EVER STARTED AUTOMATICALLY DELETING MESSAGES. I even check the Junk directory before deleting spam -- just to be sure. Duplicate e-mails are a pain, but lost e-mails are worse.

Paul
Huntsville, AL




[Evolution] What Do I Do Now (was POP3 not downloading all messages)

2004-08-23 Thread Paul Harouff




On Mon, 2004-08-23 at 22:43 -0500, Paul Harouff wrote:

On Mon, 2004-08-23 at 10:52 +0800, Not Zed wrote:

There are two alternatives:
1. don't do this, but then you get duplicate downloads. on a really flakey connection you may never (in a practical sense) get all your mail and get lots of duplicates.
2. delete the old ones always. this assumes we can trust the info, otherwise you could remove non-duplicate mails.

I'm leaning toward 2, but it complicates the code a bit.


The only problem is it looks to me that these mails were never downloaded. Of the 22, I read three on the web which I want to save by downloading them and archiving. The others I never read.


Sorry, I should get all my thoughts completed before pressing send.

Now that we know the possible cause, what do I do now. The messages are stuck on the server and I want to get them downloaded.

Paul




Re: [Evolution] POP3 not downloading all messages

2004-08-23 Thread Jeffrey Stedfast
sounds like the exact same problem Nat had, turns out that the problem
was that webmail somehow marked the message as no longer available for
POP download and thus was not an Evolution bug (evolution couldn't even
see it).

I suspect your problem is identical.

Jeff

On Mon, 2004-08-23 at 23:56, Paul Harouff wrote:
 On Mon, 2004-08-23 at 22:43 -0500, Paul Harouff wrote:
  On Mon, 2004-08-23 at 10:52 +0800, Not Zed wrote:
   There are two alternatives:
   1. don't do this, but then you get duplicate downloads.  on a
   really flakey connection you may never (in a practical sense) get
   all your mail and get lots of duplicates.
   2. delete the old ones always.  this assumes we can trust the
   info, otherwise you could remove non-duplicate mails.
   
   I'm leaning toward 2, but it complicates the code a bit.
   
  The only problem is it looks to me that these mails were never
  downloaded. Of the 22, I read three on the web which I want to save
  by downloading them and archiving. The others I never read.
  
 
 I should also mention that I am job hunting and some of these messages
 were from head-hunters that I did not read for over a week because
 they didn't download.
 
 You should always default to being conservative. It's always safer to
 get a duplicate e-mail than to lose a potential job opportunity.
 
 I WOULD STOP USING EVOLUTION IF IT EVER STARTED AUTOMATICALLY DELETING
 MESSAGES. I even check the Junk directory before deleting spam -- just
 to be sure. Duplicate e-mails are a pain, but lost e-mails are worse.
 
 Paul
 Huntsville, AL

___
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution