courier-cone Mailing List for Courier Mail Server (Page 35)
Brought to you by:
mrsam
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(22) |
Jun
(75) |
Jul
(34) |
Aug
(14) |
Sep
(43) |
Oct
(17) |
Nov
(31) |
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(15) |
Feb
(7) |
Mar
(7) |
Apr
(57) |
May
(28) |
Jun
(23) |
Jul
(8) |
Aug
(2) |
Sep
(5) |
Oct
(11) |
Nov
(1) |
Dec
|
2005 |
Jan
|
Feb
(4) |
Mar
(13) |
Apr
(2) |
May
(4) |
Jun
(35) |
Jul
(8) |
Aug
(1) |
Sep
(3) |
Oct
(7) |
Nov
(36) |
Dec
(15) |
2006 |
Jan
(3) |
Feb
(14) |
Mar
(13) |
Apr
(27) |
May
(18) |
Jun
|
Jul
|
Aug
(1) |
Sep
(3) |
Oct
|
Nov
(1) |
Dec
|
2007 |
Jan
(8) |
Feb
(11) |
Mar
(8) |
Apr
(7) |
May
(1) |
Jun
(3) |
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(7) |
Nov
(2) |
Dec
(5) |
2008 |
Jan
(4) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(6) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
(6) |
May
(5) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2010 |
Jan
|
Feb
|
Mar
(6) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(27) |
Sep
(5) |
Oct
|
Nov
(4) |
Dec
(4) |
2011 |
Jan
(4) |
Feb
|
Mar
(3) |
Apr
(5) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(2) |
Dec
|
2012 |
Jan
(7) |
Feb
|
Mar
(6) |
Apr
(4) |
May
(6) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(8) |
Dec
|
2013 |
Jan
(4) |
Feb
(5) |
Mar
(7) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
(2) |
May
|
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2015 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(13) |
Jun
|
Jul
|
Aug
(16) |
Sep
|
Oct
|
Nov
|
Dec
(4) |
2017 |
Jan
(1) |
Feb
(5) |
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2018 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
(5) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(2) |
Dec
|
2021 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2023 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Matthew P. C. <mc...@la...> - 2003-06-27 19:21:35
|
> * Several bug fixes: > reply-to not working correctly, sometimes; Thanks Sam. This release fixed the reply-to problem I mentioned at the beginning of June. Matt |
From: Sam V. <mr...@co...> - 2003-06-27 16:37:11
|
Download: http://www.courier-mta.org/download.php#cone Changes: * On the folder index screen, cursor left/right moves to the previous/next tagged message. Very useful after searches. * Several bug fixes: separate viewing of message/rfc822 attachments; date-related locale issues; reply-to not working correctly, sometimes; IMAP APPEND. |
From: Sam V. <mr...@co...> - 2003-06-27 15:39:08
|
Sam Varshavchik writes: > PatrickAle writes: > >> Write(4): 000017APPEND APPEND "Outbox" (\SEEN) "Fri, 27 Jun 2003 >> 16:36:57 +0200" {339}\r\n >> Read(4): 000017APPEND BAD Protocol Error: "Specified date is not >> valid".\r\n >> Socket.CLOSE(5): >> >> When I start the /debugio on the IMAP server I don't see the error >> message in my stderr.txt >> >> Now.. I have NO clue what this means but if someone could give me some > > This error is coming from your IMAP server. It's claiming that "Fri, 27 Jun > 2003 16:36:57 +0200" is not a valid date. > > As best as I can determine, it is a perfectly valid date. Looks like a bug > in your IMAP server. Actually, I take that back. I do see a problem that I need to fix. |
From: Sam V. <mr...@co...> - 2003-06-27 15:10:52
|
PatrickAle writes: > Write(4): 000017APPEND APPEND "Outbox" (\SEEN) "Fri, 27 Jun 2003 > 16:36:57 +0200" {339}\r\n > Read(4): 000017APPEND BAD Protocol Error: "Specified date is not > valid".\r\n > Socket.CLOSE(5): > > When I start the /debugio on the IMAP server I don't see the error > message in my stderr.txt > > Now.. I have NO clue what this means but if someone could give me some This error is coming from your IMAP server. It's claiming that "Fri, 27 Jun 2003 16:36:57 +0200" is not a valid date. As best as I can determine, it is a perfectly valid date. Looks like a bug in your IMAP server. |
From: PatrickAle <pat...@hq...> - 2003-06-27 14:45:56
|
Heyaz, Thanks for your quick reply, I tried what you described and this is what is happening: When I start /usr/bin/cone 2>/tmp/cone-stderr.txt with the /debugio on the SMTP server I see: Read(5): 220 smtp04.freeler.nl ESMTP\r\n Write(5): EHLO lilith\r\n Read(5): 250-smtp04.freeler.nl\r\n250-PIPELINING\r\n250-SIZE 10485760\r\n250 8BITMIME\r\n Write(4): 000017APPEND APPEND "Outbox" (\SEEN) "Fri, 27 Jun 2003 16:36:57 +0200" {339}\r\n Read(4): 000017APPEND BAD Protocol Error: "Specified date is not valid".\r\n Socket.CLOSE(5): When I start the /debugio on the IMAP server I don't see the error message in my stderr.txt Now.. I have NO clue what this means but if someone could give me some hints about what is going on and how it might be fixable I'd be very thankfull. Regards and have a nice weekend Patrick On Fri, 2003-06-27 at 16:23, Sam Varshavchik wrote: > PatrickAle writes: > > > Good morning/afternoon > > > > I installed both version 0.51 and 0.51.20030624 and the following error > > occurs: > > > > Whenever I try to send an email trough my SMTP server defined in the > > 'Setup page'. I get the following error: > > > > Protocol Error: ¨Specified date is not valid¨ > > > > > > To read my email I use an IMAP server (Exchange 2000) and to send my > > email I use a qmail SMTP server (smtp.freeler.nl). > > The error is reported by your mail server. The stock Qmail server does not > do anything of that sorts, so either this is a hacked Qmail that does god > only what, or this error is really coming from the Exchange box. > > Run cone and redirect standard error to a file. Append /debugio to the IMAP > server's hostname in account setup, and try again. Afterwards, search the > error log file for this error message. If not found, repeat with /debugio > added to the SMTP server's hostname. > > > > > What am I doing wrong and how do I fix it? :-) > > > > Thanks, > > > > Patrick > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: INetU > > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > > _______________________________________________ > > Courier-cone mailing list > > Cou...@li... > > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-cone |
From: Sam V. <mr...@co...> - 2003-06-27 14:24:47
|
PatrickAle writes: > Good morning/afternoon > > I installed both version 0.51 and 0.51.20030624 and the following error > occurs: > > Whenever I try to send an email trough my SMTP server defined in the > 'Setup page'. I get the following error: > > Protocol Error: =C2=A8Specified date is not valid=C2=A8 > > > To read my email I use an IMAP server (Exchange 2000) and to send my > email I use a qmail SMTP server (smtp.freeler.nl). The error is reported by your mail server. The stock Qmail server does not do anything of that sorts, so either this is a hacked Qmail that does god only what, or this error is really coming from the Exchange box. Run cone and redirect standard error to a file. Append /debugio to the IMAP= server's hostname in account setup, and try again. Afterwards, search the error log file for this error message. If not found, repeat with /debugio added to the SMTP server's hostname. > > What am I doing wrong and how do I fix it? :-) > > Thanks, > > Patrick > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > _______________________________________________ > Courier-cone mailing list > Cou...@li... > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-cone |
From: PatrickAle <pat...@hq...> - 2003-06-27 13:51:28
|
Good morning/afternoon I installed both version 0.51 and 0.51.20030624 and the following error occurs: Whenever I try to send an email trough my SMTP server defined in the 'Setup page'. I get the following error: Protocol Error: ¨Specified date is not valid¨ To read my email I use an IMAP server (Exchange 2000) and to send my email I use a qmail SMTP server (smtp.freeler.nl). What am I doing wrong and how do I fix it? :-) Thanks, Patrick |
From: Matthias A. <ma...@dt...> - 2003-06-26 22:50:59
|
Sam Varshavchik <mr...@co...> writes: > I'd like to see the complete set of headers. This should only happen if > the From: address is set up as one of your own addresses. Will be sent to Sam's private mail account. -- Matthias Andree |
From: Sam V. <mr...@co...> - 2003-06-26 14:36:46
|
Matthias Andree writes: > Hi, > > my cone 0.51.20030624 apparently confuses To: and From: headers when I > press "Reply" (for example on qsecretary notices as sent by > *@list.cr.yp.to), it takes the "To:" header of the original mail to > derive the reply address. I'd like it to use the Reply-To: or From: > address instead. :-) > > This happens on a local Maildir. I can provide sample headers in a > separate mail to a developer if desired. I'd like to see the complete set of headers. This should only happen if the From: address is set up as one of your own addresses. |
From: Sam V. <mr...@co...> - 2003-06-26 14:32:47
|
Matthias Andree writes: > Sam Varshavchik <mr...@co...> writes: > >>> *** Error code 1 (continuing) >>> Are these functions indispensable? >> >> Yes. > > I think FreeBSD 4 is out of the game then... Such is life. > Maybe a suitable workaround is choosing %I:%M %p versus %H:%M depending > on what strftime formats for "14h" with %X. If it includes the string > "2", assume 12hr, else 24hr time display? Yes. I've independently deduced this trick yesterday. It seems to work. |
From: Matthias A. <ma...@dt...> - 2003-06-26 08:57:07
|
Hi, my cone 0.51.20030624 apparently confuses To: and From: headers when I press "Reply" (for example on qsecretary notices as sent by *@list.cr.yp.to), it takes the "To:" header of the original mail to derive the reply address. I'd like it to use the Reply-To: or From: address instead. :-) This happens on a local Maildir. I can provide sample headers in a separate mail to a developer if desired. -- Matthias Andree |
From: Matthias A. <ma...@dt...> - 2003-06-26 08:40:15
|
Hi, I have a preliminary version of a FreeBSD 5 port of cone that works for me on 5-CURRENT but is hardly tested otherwise. It needs more testing, YOUR HELP, before being submitted to the FreeBSD project. The port is part of this mail, instructions below. Please test, particularly the GnuPG functions, SMAP access, certificate verification for SSL/TLS connections and report back if everything works for you. Please include the exact FreeBSD version, in doubt, use "uname -a" to find out. It does NOT work on FreeBSD 4 (and the port should refuse to build). After unpacking the shar below, cd to the cone directory and type "make install", then if it worked out, "make clean". One inconvenience at runtime is that cone doesn't know how to figure the official name for the character set (say, iso-8859-1) from the X11-based FreeBSD name (ISO8859-1). Work around that by typing env CHARSET=iso-8859-1 cone The c_rehash script has been taken verbatim from FreeBSD's "courier" port. # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # cone # cone/Makefile # cone/distinfo # cone/files # cone/scripts # cone/scripts/c_rehash # cone/pkg-deinstall # cone/pkg-descr # cone/pkg-install # cone/pkg-plist # echo c - cone mkdir -p cone > /dev/null 2>&1 echo x - cone/Makefile sed 's/^X//' >cone/Makefile << 'END-of-cone/Makefile' X# ports collection Makefile for: cone X# Whom: Matthias Andree <mat...@gm...> X# Date created: 2003-06-19 X# X# $FreeBSD$ X# X XPORTNAME= cone XPORTVERSION= 0.51.20030624 XCATEGORIES= mail XMASTER_SITES= http://www.courier-mta.org/beta/${PORTNAME}/ X XMAINTAINER= mat...@gm... XCOMMENT= "Console based mail client with POP3/IMAP/SMAP support" X XLIB_DEPENDS= xml2.5:${PORTSDIR}/textproc/libxml2 \ X aspell.15:${PORTSDIR}/textproc/aspell XBUILD_DEPENDS= gpg:${PORTSDIR}/security/gnupg \ X ${LOCALBASE}/lib/libncurses.so.5.3:${PORTSDIR}/devel/ncurses XRUN_DEPENDS= gpg:${PORTSDIR}/security/gnupg \ X ${LOCALBASE}/lib/libncurses.so.5.3:${PORTSDIR}/devel/ncurses XRUN_DEPENDS+= ${LOCALBASE}/share/sysconftool/sysconftool:${PORTSDIR}/devel/sysconftool X XUSE_BZIP2= yes XUSE_PERL5= yes XGNU_CONFIGURE= yes XCONFIGURE_ARGS= -C --without-db --prefix=${PREFIX} --exec-prefix=${PREFIX} X XCONFIGURE_ENV= REHASH=${SCRIPTDIR}/c_rehash LDFLAGS=-L${LOCALBASE}/lib \ X CPPFLAGS=-I${LOCALBASE}/include XCONFIGURE_TARGET= --build=${MACHINE_ARCH}-portbld-freebsd${OSREL} XMAN1= cone.1 leaf.1 mailtool.1 X Xdo-install: X cd ${WRKSRC} && make install-strip X Xpost-install: X PKG_PREFIX=${PREFIX} ${SH} pkg-install ${PORTNAME} POST-INSTALL X X.include <bsd.port.pre.mk> X X.if ${OSVERSION} < 500000 XIGNORE= "does not build on FreeBSD versions before FreeBSD 5" X.endif X X.include <bsd.port.post.mk> END-of-cone/Makefile echo x - cone/distinfo sed 's/^X//' >cone/distinfo << 'END-of-cone/distinfo' XMD5 (cone-0.51.20030624.tar.bz2) = bf088ff65d0e0be74628cad63ed5b6c7 END-of-cone/distinfo echo c - cone/files mkdir -p cone/files > /dev/null 2>&1 echo c - cone/scripts mkdir -p cone/scripts > /dev/null 2>&1 echo x - cone/scripts/c_rehash sed 's/^X//' >cone/scripts/c_rehash << 'END-of-cone/scripts/c_rehash' X#!/usr/bin/perl X X X# Perl c_rehash script, scan all files in a directory X# and add symbolic links to their hash values. X Xmy $openssl; X Xmy $dir = "/etc/ssl"; X Xif(defined $ENV{OPENSSL}) { X $openssl = $ENV{OPENSSL}; X} else { X $openssl = "openssl"; X $ENV{OPENSSL} = $openssl; X} X Xif(! -f $openssl) { X my $found = 0; X foreach (split /:/, $ENV{PATH}) { X if(-f "$_/$openssl") { X $found = 1; X last; X } X } X if($found == 0) { X print STDERR "c_rehash: rehashing skipped ('openssl' program not available)\n"; X exit 0; X } X} X Xif(@ARGV) { X @dirlist = @ARGV; X} elsif($ENV{SSL_CERT_DIR}) { X @dirlist = split /:/, $ENV{SSL_CERT_DIR}; X} else { X $dirlist[0] = "$dir/certs"; X} X X Xforeach (@dirlist) { X if(-d $_ and -w $_) { X hash_dir($_); X } X} X Xsub hash_dir { X my %hashlist; X print "Doing $_[0]\n"; X chdir $_[0]; X opendir(DIR, "."); X my @flist = readdir(DIR); X # Delete any existing symbolic links X foreach (grep {/^[\da-f]+\.r{0,1}\d+$/} @flist) { X if(-l $_) { X unlink $_; X } X } X closedir DIR; X FILE: foreach $fname (grep {/\.pem$/} @flist) { X # Check to see if certificates and/or CRLs present. X my ($cert, $crl) = check_file($fname); X if(!$cert && !$crl) { X print STDERR "WARNING: $fname does not contain a certificate or CRL: skipping\n"; X next; X } X link_hash_cert($fname) if($cert); X link_hash_crl($fname) if($crl); X } X} X Xsub check_file { X my ($is_cert, $is_crl) = (0,0); X my $fname = $_[0]; X open IN, $fname; X while(<IN>) { X if(/^-----BEGIN (.*)-----/) { X my $hdr = $1; X if($hdr =~ /^(X509 |TRUSTED |)CERTIFICATE$/) { X $is_cert = 1; X last if($is_crl); X } elsif($hdr eq "X509 CRL") { X $is_crl = 1; X last if($is_cert); X } X } X } X close IN; X return ($is_cert, $is_crl); X} X X X# Link a certificate to its subject name hash value, each hash is of X# the form <hash>.<n> where n is an integer. If the hash value already exists X# then we need to up the value of n, unless its a duplicate in which X# case we skip the link. We check for duplicates by comparing the X# certificate fingerprints X Xsub link_hash_cert { X my $fname = $_[0]; X my ($hash, $fprint) = `$openssl x509 -hash -fingerprint -noout -in $fname`; X chomp $hash; X chomp $fprint; X $fprint =~ s/^.*=//; X $fprint =~ tr/://d; X my $suffix = 0; X # Search for an unused hash filename X while(exists $hashlist{"$hash.$suffix"}) { X # Hash matches: if fingerprint matches its a duplicate cert X if($hashlist{"$hash.$suffix"} eq $fprint) { X print STDERR "WARNING: Skipping duplicate certificate $fname\n"; X return; X } X $suffix++; X } X $hash .= ".$suffix"; X print "$fname => $hash\n"; X $symlink_exists=eval {symlink("",""); 1}; X if ($symlink_exists) { X symlink $fname, $hash; X } else { X system ("cp", $fname, $hash); X } X $hashlist{$hash} = $fprint; X} X X# Same as above except for a CRL. CRL links are of the form <hash>.r<n> X Xsub link_hash_crl { X my $fname = $_[0]; X my ($hash, $fprint) = `$openssl crl -hash -fingerprint -noout -in $fname`; X chomp $hash; X chomp $fprint; X $fprint =~ s/^.*=//; X $fprint =~ tr/://d; X my $suffix = 0; X # Search for an unused hash filename X while(exists $hashlist{"$hash.r$suffix"}) { X # Hash matches: if fingerprint matches its a duplicate cert X if($hashlist{"$hash.r$suffix"} eq $fprint) { X print STDERR "WARNING: Skipping duplicate CRL $fname\n"; X return; X } X $suffix++; X } X $hash .= ".r$suffix"; X print "$fname => $hash\n"; X $symlink_exists=eval {symlink("",""); 1}; X if ($symlink_exists) { X symlink $fname, $hash; X } else { X system ("cp", $fname, $hash); X } X $hashlist{$hash} = $fprint; X} X END-of-cone/scripts/c_rehash echo x - cone/pkg-deinstall sed 's/^X//' >cone/pkg-deinstall << 'END-of-cone/pkg-deinstall' X#! /bin/sh Xcase "$2" in DEINSTALL) X if cmp -s "$PKG_PREFIX/etc/cone" "$PKG_PREFIX/etc/cone.dist" ; then X rm -f "$PKG_PREFIX/etc/cone" X else X echo "Modified $PKG_PREFIX/etc/cone left in place." X fi Xesac END-of-cone/pkg-deinstall echo x - cone/pkg-descr sed 's/^X//' >cone/pkg-descr << 'END-of-cone/pkg-descr' XCone is a text-based mail client. Cone seamlessly handles multiple POP3, XIMAP accounts, and local mail folders. Cone is also a simple newsreader. XCone is designed to be foolproof enough to be used by inexperienced users, Xbut also offers advanced features for power users. END-of-cone/pkg-descr echo x - cone/pkg-install sed 's/^X//' >cone/pkg-install << 'END-of-cone/pkg-install' X#! /bin/sh Xcase "$2" in POST-INSTALL) X "$PKG_PREFIX/share/sysconftool/sysconftool" "$PKG_PREFIX/etc/cone.dist" ;; Xesac END-of-cone/pkg-install echo x - cone/pkg-plist sed 's/^X//' >cone/pkg-plist << 'END-of-cone/pkg-plist' Xbin/cone Xbin/leaf Xetc/cone.dist Xlibexec/cone Xshare/cone/APPLICATION.PDF.filter Xshare/cone/IMAGE.GIF.filter Xshare/cone/IMAGE.JPEG.filter Xshare/cone/IMAGE.PNG.filter Xshare/cone/account-checknewmail.html Xshare/cone/account-copymessagesto.html Xshare/cone/account-createfolder.html Xshare/cone/account-deletefolder.html Xshare/cone/account-getfolderfrompath.html Xshare/cone/account-getfolderfromstring.html Xshare/cone/account-getfolderindexinfo.html Xshare/cone/account-getfolderindexsize.html Xshare/cone/account-getmessagecontent.html Xshare/cone/account-getmessagecontentdecoded.html Xshare/cone/account-getmessageenvelope.html Xshare/cone/account-getmessagestructure.html Xshare/cone/account-getparentfolder.html Xshare/cone/account-getsubfolders.html Xshare/cone/account-gettoplevelfolders.html Xshare/cone/account-libmail-addmessage.html Xshare/cone/account-login.html Xshare/cone/account-logout.html Xshare/cone/account-openfolder.html Xshare/cone/account-readfolderinfo.html Xshare/cone/account-removemessages.html Xshare/cone/account-renamefolder.html Xshare/cone/account-savefolderindexinfo.html Xshare/cone/account-searchmessages.html Xshare/cone/account-send.html Xshare/cone/account-translatepath.html Xshare/cone/account-updatefolderindexflags.html Xshare/cone/account-updatefolderindexinfo.html Xshare/cone/add.html Xshare/cone/address.html Xshare/cone/attributes.html Xshare/cone/book.html Xshare/cone/c1838.html Xshare/cone/c1876.html Xshare/cone/cone.hlp Xshare/cone/cone.html Xshare/cone/cone00index.html Xshare/cone/cone01folderlist.html Xshare/cone/cone02folderindex.html Xshare/cone/cone03messageview.html Xshare/cone/cone04writemessage.html Xshare/cone/cone05setup.html Xshare/cone/cone06newaccount.html Xshare/cone/cone07remoteconfig.html Xshare/cone/cone08gpg.html Xshare/cone/cone09masterpassword.html Xshare/cone/cone10encryption.html Xshare/cone/envelope.html Xshare/cone/faq.html Xshare/cone/folder-addmessage.html Xshare/cone/folder-clone.html Xshare/cone/folder-create.html Xshare/cone/folder-createsubfolder.html Xshare/cone/folder-destroy.html Xshare/cone/folder-getname.html Xshare/cone/folder-getparentfolder.html Xshare/cone/folder-getpath.html Xshare/cone/folder-hasmessages.html Xshare/cone/folder-hassubfolders.html Xshare/cone/folder-isparentof.html Xshare/cone/folder-open.html Xshare/cone/folder-readfolderinfo.html Xshare/cone/folder-readsubfolders.html Xshare/cone/folder-renamefolder.html Xshare/cone/folder-tostring.html Xshare/cone/index.html Xshare/cone/install.html Xshare/cone/leaf.html Xshare/cone/libmail.html Xshare/cone/mail-checknewmail.html Xshare/cone/mail-copymessagesto.html Xshare/cone/mail-findfolder.html Xshare/cone/mail-folderfromstring.html Xshare/cone/mail-getfolderindexinfo.html Xshare/cone/mail-getfolderindexsize.html Xshare/cone/mail-getsendfolder.html Xshare/cone/mail-hascapability.html Xshare/cone/mail-homedir.html Xshare/cone/mail-hostname.html Xshare/cone/mail-isremoteurl.html Xshare/cone/mail-loginurldecode.html Xshare/cone/mail-loginurlencode.html Xshare/cone/mail-logout.html Xshare/cone/mail-open.html Xshare/cone/mail-process.html Xshare/cone/mail-readmsgattr.html Xshare/cone/mail-readmsgcontent.html Xshare/cone/mail-readmsgcontentdecoded.html Xshare/cone/mail-readtoplevel.html Xshare/cone/mail-removemessages.html Xshare/cone/mail-resume.html Xshare/cone/mail-savefolderindexinfo.html Xshare/cone/mail-searchmessages.html Xshare/cone/mail-setappcharset.html Xshare/cone/mail-translatepath.html Xshare/cone/mail-updatefolderindexflags.html Xshare/cone/mail-updatefolderindexinfo.html Xshare/cone/mail-updatenotify.html Xshare/cone/mail-upper.html Xshare/cone/mailtool.html Xshare/cone/manpage.css Xshare/cone/mimestruct.html Xshare/cone/native.html Xshare/cone/r6319.html Xshare/cone/r6539.html Xshare/cone/r7945.html Xshare/cone/readme.html Xshare/cone/rootcerts/aba-ecom-root-ca.pem Xshare/cone/rootcerts/addtrust-class-1-ca-root.pem Xshare/cone/rootcerts/addtrust-external-ca-root.pem Xshare/cone/rootcerts/addtrust-public-ca-root.pem Xshare/cone/rootcerts/addtrust-qualified-ca-root.pem Xshare/cone/rootcerts/american-express-certificate-authority.pem Xshare/cone/rootcerts/american-express-global-certificate.pem Xshare/cone/rootcerts/baltimore-cybertrust-code-signing.pem Xshare/cone/rootcerts/baltimore-cybertrust-mobile-root.pem Xshare/cone/rootcerts/baltimore-cybertrust-root.pem Xshare/cone/rootcerts/bankengine.pem Xshare/cone/rootcerts/belsign-object-publishing-ca.pem Xshare/cone/rootcerts/belsign-secure-server-ca.pem Xshare/cone/rootcerts/betrusted-root-ca.pem Xshare/cone/rootcerts/certengine.pem Xshare/cone/rootcerts/class-1-public-primary-ocsp-responder.pem Xshare/cone/rootcerts/class-2-public-primary-ocsp-responder.pem Xshare/cone/rootcerts/class-3-public-primary-ocsp-responder.pem Xshare/cone/rootcerts/cybertrust-japan-root-ca.pem Xshare/cone/rootcerts/cybertrust-japan-secure-server.pem Xshare/cone/rootcerts/deutsche-telekom-root-ca.pem Xshare/cone/rootcerts/digital-signature-trust-co-dstca-00.pem Xshare/cone/rootcerts/digital-signature-trust-co-dstca-01.pem Xshare/cone/rootcerts/dst-rootca-x1.pem Xshare/cone/rootcerts/dst-rootca-x2.pem Xshare/cone/rootcerts/e-certify-ca.pem Xshare/cone/rootcerts/e-certify-ra.pem Xshare/cone/rootcerts/entrust-net-certification-authority.pem Xshare/cone/rootcerts/entrust-net-client-certification-00.pem Xshare/cone/rootcerts/entrust-net-client-certification-01.pem Xshare/cone/rootcerts/entrust-net-secure-server-certification-00.pem Xshare/cone/rootcerts/entrust-net-secure-server-certification-01.pem Xshare/cone/rootcerts/equifax-equifax-premium-certificate.pem Xshare/cone/rootcerts/equifax-equifax-secure-certificate.pem Xshare/cone/rootcerts/equifax-secure-ebusiness-ca-1.pem Xshare/cone/rootcerts/equifax-secure-equifax-secure-ebusiness.pem Xshare/cone/rootcerts/equifax-secure-global-ebusiness.pem Xshare/cone/rootcerts/fortengine.pem Xshare/cone/rootcerts/globalsign-partners-ca.pem Xshare/cone/rootcerts/globalsign-primary-class-1-ca.pem Xshare/cone/rootcerts/globalsign-primary-class-2-ca.pem Xshare/cone/rootcerts/globalsign-primary-class-3-ca.pem Xshare/cone/rootcerts/globalsign-root-ca.pem Xshare/cone/rootcerts/gp-root-2.pem Xshare/cone/rootcerts/gp-root-3.pem Xshare/cone/rootcerts/gp-root-4.pem Xshare/cone/rootcerts/gp-root-5.pem Xshare/cone/rootcerts/gte-cybertrust-global-root.pem Xshare/cone/rootcerts/gte-cybertrust-root-5.pem Xshare/cone/rootcerts/gte-cybertrust-root.pem Xshare/cone/rootcerts/http-www-valicert-com-00.pem Xshare/cone/rootcerts/http-www-valicert-com-01.pem Xshare/cone/rootcerts/http-www-valicert-com-02.pem Xshare/cone/rootcerts/http-www-valicert-net.pem Xshare/cone/rootcerts/mailengine.pem Xshare/cone/rootcerts/rsa-data-security-inc-secure-server.pem Xshare/cone/rootcerts/secure-server-ocsp-responder.pem Xshare/cone/rootcerts/tc-trustcenter-for-security-in-00.pem Xshare/cone/rootcerts/tc-trustcenter-for-security-in-01.pem Xshare/cone/rootcerts/tc-trustcenter-for-security-in-02.pem Xshare/cone/rootcerts/tc-trustcenter-for-security-in-03.pem Xshare/cone/rootcerts/tc-trustcenter-for-security-in-04.pem Xshare/cone/rootcerts/thawte-personal-basic-ca.pem Xshare/cone/rootcerts/thawte-personal-freemail-ca.pem Xshare/cone/rootcerts/thawte-personal-premium-ca.pem Xshare/cone/rootcerts/thawte-premium-server-ca.pem Xshare/cone/rootcerts/thawte-server-ca.pem Xshare/cone/rootcerts/thawte-timestamping-ca.pem Xshare/cone/rootcerts/thawte-universal-ca-root.pem Xshare/cone/rootcerts/traderengine.pem Xshare/cone/rootcerts/usps-production-ca-1.pem Xshare/cone/rootcerts/usps-root-ca.pem Xshare/cone/rootcerts/verisign-class-1-public-primary.pem Xshare/cone/rootcerts/verisign-class-2-public-primary.pem Xshare/cone/rootcerts/verisign-class-3-public-primary.pem Xshare/cone/rootcerts/verisign-class-4-public-primary.pem Xshare/cone/rootcerts/verisign-inc-class-1-public-primary.pem Xshare/cone/rootcerts/verisign-inc-class-2-public-primary.pem Xshare/cone/rootcerts/verisign-inc-class-3-public-primary.pem Xshare/cone/rootcerts/verisign-inc-verisign-trust-network-00.pem Xshare/cone/rootcerts/verisign-inc-verisign-trust-network-01.pem Xshare/cone/rootcerts/verisign-inc-verisign-trust-network-02.pem Xshare/cone/rootcerts/verisign-inc-verisign-trust-network-03.pem Xshare/cone/rootcerts/verisign-time-stamping-authority.pem Xshare/cone/rootcerts/visa-visa-international-service.pem Xshare/cone/rootcerts/xcert-ez-by-dst.pem Xshare/cone/rootcerts/xcert-international-inc-xcert-root-00.pem Xshare/cone/rootcerts/xcert-international-inc-xcert-root-01.pem Xshare/cone/rootcerts/xcert-international-inc-xcert-root-02.pem Xshare/cone/rootcerts/xcert-international-inc-xcert-root-03.pem Xshare/cone/rootcerts/052e396b.0 Xshare/cone/rootcerts/0bb21872.0 Xshare/cone/rootcerts/0c364b2d.0 Xshare/cone/rootcerts/0e82f83a.0 Xshare/cone/rootcerts/11f154d6.0 Xshare/cone/rootcerts/128b9c8d.0 Xshare/cone/rootcerts/19899da5.0 Xshare/cone/rootcerts/1a147d5b.0 Xshare/cone/rootcerts/1bb6c7e0.0 Xshare/cone/rootcerts/256fd83b.0 Xshare/cone/rootcerts/2d047263.0 Xshare/cone/rootcerts/2edf7016.0 Xshare/cone/rootcerts/31044350.0 Xshare/cone/rootcerts/3ad48a91.0 Xshare/cone/rootcerts/3c58f906.0 Xshare/cone/rootcerts/3e7271e8.0 Xshare/cone/rootcerts/412bea73.0 Xshare/cone/rootcerts/418882ac.0 Xshare/cone/rootcerts/43d4bde2.0 Xshare/cone/rootcerts/4643210f.0 Xshare/cone/rootcerts/4d654d1d.0 Xshare/cone/rootcerts/5480ace1.0 Xshare/cone/rootcerts/54edfa5d.0 Xshare/cone/rootcerts/56e607f4.0 Xshare/cone/rootcerts/594f1775.0 Xshare/cone/rootcerts/5ee07a24.0 Xshare/cone/rootcerts/5f5e5caa.0 Xshare/cone/rootcerts/6166cb50.0 Xshare/cone/rootcerts/61f6c934.0 Xshare/cone/rootcerts/66eb5c17.0 Xshare/cone/rootcerts/66ec64da.0 Xshare/cone/rootcerts/6981fb07.0 Xshare/cone/rootcerts/6a15001a.0 Xshare/cone/rootcerts/6c55cf77.0 Xshare/cone/rootcerts/6d6ec79c.0 Xshare/cone/rootcerts/700b8679.0 Xshare/cone/rootcerts/709afd2b.0 Xshare/cone/rootcerts/72fa7371.0 Xshare/cone/rootcerts/73451336.0 Xshare/cone/rootcerts/739b7930.0 Xshare/cone/rootcerts/74c26bd0.0 Xshare/cone/rootcerts/7651b327.0 Xshare/cone/rootcerts/76d6205a.0 Xshare/cone/rootcerts/788c9bfc.0 Xshare/cone/rootcerts/7a9820c1.0 Xshare/cone/rootcerts/7d3cd826.0 Xshare/cone/rootcerts/7d453d8f.0 Xshare/cone/rootcerts/7e74191f.0 Xshare/cone/rootcerts/81447c6e.0 Xshare/cone/rootcerts/843b6c51.0 Xshare/cone/rootcerts/878cf4c6.0 Xshare/cone/rootcerts/8e6e2991.0 Xshare/cone/rootcerts/8efac7d4.0 Xshare/cone/rootcerts/8f7b96c4.0 Xshare/cone/rootcerts/95750816.0 Xshare/cone/rootcerts/97b4211c.0 Xshare/cone/rootcerts/a15b3b6b.0 Xshare/cone/rootcerts/a2be0f54.0 Xshare/cone/rootcerts/a2df7ad7.0 Xshare/cone/rootcerts/a38484ce.0 Xshare/cone/rootcerts/a3c60019.0 Xshare/cone/rootcerts/aaa45464.0 Xshare/cone/rootcerts/b0f3e76e.0 Xshare/cone/rootcerts/b5f329fa.0 Xshare/cone/rootcerts/ba386118.0 Xshare/cone/rootcerts/bb0a889c.0 Xshare/cone/rootcerts/bcdd5959.0 Xshare/cone/rootcerts/bffe8b5d.0 Xshare/cone/rootcerts/c19d42c7.0 Xshare/cone/rootcerts/c215bc69.0 Xshare/cone/rootcerts/c33a80d4.0 Xshare/cone/rootcerts/c527e4ab.0 Xshare/cone/rootcerts/c9bc75ba.0 Xshare/cone/rootcerts/ccf7ff0e.0 Xshare/cone/rootcerts/d2adc77d.0 Xshare/cone/rootcerts/d593166d.0 Xshare/cone/rootcerts/d78a75c7.0 Xshare/cone/rootcerts/db65db21.0 Xshare/cone/rootcerts/ddc328ff.0 Xshare/cone/rootcerts/dfd0b044.0 Xshare/cone/rootcerts/e268a4c5.0 Xshare/cone/rootcerts/e28f6bbc.0 Xshare/cone/rootcerts/e7b8d656.0 Xshare/cone/rootcerts/e9aaa9de.0 Xshare/cone/rootcerts/ed049835.0 Xshare/cone/rootcerts/ed524cf5.0 Xshare/cone/rootcerts/ed62f4e3.0 Xshare/cone/rootcerts/f10dd942.0 Xshare/cone/rootcerts/f4996e82.0 Xshare/cone/rootcerts/f73e89fd.0 Xshare/cone/search.html Xshare/cone/smap1.html Xshare/cone/store.html Xshare/cone/synchronous.html Xshare/cone/x8350.html Xshare/cone/x8435.html Xshare/cone/x8547.html Xshare/cone/x8683.html Xshare/cone/x8938.html Xshare/cone/x9158.html Xshare/cone/x9261.html Xshare/cone/x9484.html Xshare/cone/x9808.html Xshare/cone/x9819.html X@dirrm share/cone/rootcerts X@dirrm share/cone END-of-cone/pkg-plist exit -- Matthias Andree |
From: Matthias A. <ma...@dt...> - 2003-06-26 08:27:44
|
Sam Varshavchik <mr...@co...> writes: >> *** Error code 1 (continuing) >> Are these functions indispensable? > > Yes. I think FreeBSD 4 is out of the game then... >> mail.C:258: macro `LIBMAIL_THROW' used without args > > mail.c(258): > > LIBMAIL_THROW(); > > I definitely see an argument there: an empty one. And gcc 2.95 pickiness is no longer relevant, FreeBSD 5 uses gcc 3.2.x. >> In file included from /usr/include/sys/select.h:40, >> from mail.H:15, >> from mail.C:7: >> /usr/include/sys/event.h:53: syntax error before `;' >> ... > > This one indicates that there's some missing prerequisite .h file that > must be included. This is also FreeBSD 4 specific and does not affect FreeBSD 5. >> Date: Wed, 25 Jun 2003 13:20:59 +0200 >> LANG=de_DE@euro >> LC_*="de_DE@euro" >> EXCEPT: LC_COLLATE=POSIX >> LC_ALL= > > The problem is that there is no well defined mechanism to obtain the > preferred 12/24 hour setting automatically, from the locale, so the > index always formats the time using the 12 hour setting: > > strftime(buffer, sizeof(buffer), "%a %I:%M %p", > localtime(&messageDate)); > > Now, one could use %X instead of %I:%M %p; however that's going to > include the seconds, and there's simply no real estate for them. ... > Perhaps the solution is to have a manual 12/24 hour setting on the setup > screen. I don't see any way to cleanly use the locale setting. I see the problem, and strrchr(buffer, ':') won't be of help if the locale uses something other than ":" to separate the time. The interesting part is that %p is empty on my machine... Maybe a suitable workaround is choosing %I:%M %p versus %H:%M depending on what strftime formats for "14h" with %X. If it includes the string "2", assume 12hr, else 24hr time display? -- Matthias Andree |
From: Sam V. <mr...@co...> - 2003-06-25 21:55:18
|
Matthias Andree writes: > Sam Varshavchik <mr...@co...> writes: > >> Unfortunately, it is not possible to compute, in advance, whether all >> messages from one character set are capable of being shown on a display >> that uses a different character set. This is not feasible. > > It's certainly feasible, I'd try to convert to display character set (if > need be, I'd convert to some efficient Unicode representation first), > and if a missing character is found, issue the warning. The problem is enumerating the characters in the original codeset. With multibyte codesets, you potentially have thousands of multibyte characters. Cone's internal unicode library consists only of functions that translate character streams from and to Unicode. There is no enumeration functionality. It has to be written, for every character set; and use that to create a table of mappable character sets. And then you'd discover that only a few character sets can be fully mapped to another character set. All that work will go to waste. > BTW; I have difficulties porting the stuff to FreeBSD 4, which doesn't > implement mbrtowc and wcrtomb: > > Compiling curses.C > curses.C: In function `static void Curses::mbtow(const char *, vector<__wchar_t,allocator<__wchar_t> > &)': > curses.C:434: implicit declaration of function `int mbrtowc(...)' > curses.C: In function `static class string Curses::wtomb(const __wchar_t *)': > curses.C:517: implicit declaration of function `int wcrtomb(...)' > cursesscreen.C: In method `class Curses::Key CursesScreen::doGetKey()': > cursesscreen.C:556: implicit declaration of function `int mbrtowc(...)' > *** Error code 1 (continuing) > > Are these functions indispensable? Yes. > Would ftp://ftp.whizkidtech.net/unix/ > be a way out? (There's libutf-8.1.0, "Unicode conversion routines > between UCS-4 and UTF-8") No. mbrtowc converts between the local character set, and unicode. wcrtomb does the opposite. These functions obtain the display character set from the locale setting, and set up mapping between whatever the current display character set is, and Unicode. > Then, gcc 2.95 doesn't compile cone (neither on Linux nor FreeBSD), gcc > 3.3 appears fine. > > Compiling mail.C > mail.C:258: macro `LIBMAIL_THROW' used without args mail.c(258): LIBMAIL_THROW(); I definitely see an argument there: an empty one. You can work around that one by #define LIBMAIL_NONE, then using LIBMAIL_NONE as the argument. > In file included from /usr/include/sys/select.h:40, > from mail.H:15, > from mail.C:7: > /usr/include/sys/event.h:53: syntax error before `;' > ... This one indicates that there's some missing prerequisite .h file that must be included. > It then appears as though index and header display of the date didn't > match in their 12/24 hr choice (I prefer 24hr, which is set in the de_DE > locales): > > 187 Mit 01:20 MatthiasAndree (4 Kb) Re: [leafnode-list] Small chang > vs. > Date: Wed, 25 Jun 2003 13:20:59 +0200 > > LANG=de_DE@euro > LC_*="de_DE@euro" > > EXCEPT: LC_COLLATE=POSIX > LC_ALL= The problem is that there is no well defined mechanism to obtain the preferred 12/24 hour setting automatically, from the locale, so the index always formats the time using the 12 hour setting: strftime(buffer, sizeof(buffer), "%a %I:%M %p", localtime(&messageDate)); Now, one could use %X instead of %I:%M %p; however that's going to include the seconds, and there's simply no real estate for them. Perhaps the solution is to have a manual 12/24 hour setting on the setup screen. I don't see any way to cleanly use the locale setting. The Date: header always uses the format defined by RFC 822. |
From: Matthias A. <ma...@dt...> - 2003-06-25 21:33:42
|
Sam Varshavchik <mr...@co...> writes: > Unfortunately, it is not possible to compute, in advance, whether all > messages from one character set are capable of being shown on a display > that uses a different character set. This is not feasible. It's certainly feasible, I'd try to convert to display character set (if need be, I'd convert to some efficient Unicode representation first), and if a missing character is found, issue the warning. I'd understand if that was too inefficient to enable by default though. BTW; I have difficulties porting the stuff to FreeBSD 4, which doesn't implement mbrtowc and wcrtomb: Compiling curses.C curses.C: In function `static void Curses::mbtow(const char *, vector<__wchar_t,allocator<__wchar_t> > &)': curses.C:434: implicit declaration of function `int mbrtowc(...)' curses.C: In function `static class string Curses::wtomb(const __wchar_t *)': curses.C:517: implicit declaration of function `int wcrtomb(...)' cursesscreen.C: In method `class Curses::Key CursesScreen::doGetKey()': cursesscreen.C:556: implicit declaration of function `int mbrtowc(...)' *** Error code 1 (continuing) Are these functions indispensable? Would ftp://ftp.whizkidtech.net/unix/ be a way out? (There's libutf-8.1.0, "Unicode conversion routines between UCS-4 and UTF-8") Then, gcc 2.95 doesn't compile cone (neither on Linux nor FreeBSD), gcc 3.3 appears fine. Compiling mail.C mail.C:258: macro `LIBMAIL_THROW' used without args mail.C:608: macro `LIBMAIL_THROW' used without args mail.C:625: macro `LIBMAIL_THROW' used without args mail.C:719: macro `LIBMAIL_THROW' used without args mail.C:739: macro `LIBMAIL_THROW' used without args In file included from /usr/include/sys/select.h:40, from mail.H:15, from mail.C:7: /usr/include/sys/event.h:53: syntax error before `;' ... It then appears as though index and header display of the date didn't match in their 12/24 hr choice (I prefer 24hr, which is set in the de_DE locales): 187 Mit 01:20 MatthiasAndree (4 Kb) Re: [leafnode-list] Small chang vs. Date: Wed, 25 Jun 2003 13:20:59 +0200 LANG=de_DE@euro LC_*="de_DE@euro" EXCEPT: LC_COLLATE=POSIX LC_ALL= (I haven't yet received feedback as to the removed blanks of this IMAP server, but I didn't expect to hear from web.de - these ... send automatic responses referring to premium rate 1,86 Euro/min phone support -- for bug reports? As though a phone support that talks Winbloze users through setting up POP3 in Lookout Exanthema could help me with that...) -- Matthias Andree |
From: Sam V. <mr...@co...> - 2003-06-25 20:38:42
|
Matthias Andree writes: > 0.50.20030531 just showed me this nice bogus warning: > > [ The following text is written in the us-ascii character set. Your display ] > [ is set to the ISO-8859-15 character set, so some characters may not be ] > [ shown correctly. ] > > I'd think this warning should not display because ISO-8859-{1,2,15} > (don't know the others) is a superset of US-ASCII. In fact, the message > should only be shown when there are characters in the message that > cannot be displayed in the terminal character set. (In fact, most > ISO-8859-1 messages can be displayed on ISO-8859-15 terminals and vice > versa, and most German-language messages can also be displayed on > ISO-8859-2 terminals.) Unfortunately, it is not possible to compute, in advance, whether all messages from one character set are capable of being shown on a display that uses a different character set. This is not feasible. But that's not even the issue, here. us-ascii in Cone is just an alias for iso-8859-1. Essentially, the message is read using iso-8859-1, and then transcoded to iso-8859-15. And, of course, there are a few characters in iso-8859-1 that have no iso-8859-15 equivalents. This warning is suppressed when the display is set to UTF-8. That's because any known character set can be transcoded to UTF-8. The only time this warning is shown on an UTF-8 terminal would be if the original character set is not known to Cone. |
From: Matthias A. <ma...@dt...> - 2003-06-25 20:22:31
|
0.50.20030531 just showed me this nice bogus warning: [ The following text is written in the us-ascii character set. Your display ] [ is set to the ISO-8859-15 character set, so some characters may not be ] [ shown correctly. ] I'd think this warning should not display because ISO-8859-{1,2,15} (don't know the others) is a superset of US-ASCII. In fact, the message should only be shown when there are characters in the message that cannot be displayed in the terminal character set. (In fact, most ISO-8859-1 messages can be displayed on ISO-8859-15 terminals and vice versa, and most German-language messages can also be displayed on ISO-8859-2 terminals.) -- Matthias Andree |
From: Sam V. <mr...@co...> - 2003-06-25 01:55:39
|
Download: http://www.courier-mta.org/download.php#cone Another set of changes; hoping they'll clear the remaining issues. * Several portability fixes. * Compile again new aspell 0.50+ API * New command on the folder listing screen: ^R removes any memorized custom headers for the highlighted folder (reverting to account defaults). * Fix some g++ 3.2.2 silliness; /debugio was logging debug data to stderr one character at a time. * Uploading messages to beta Courier-IMAP with SMAP turned did not show upload progress indication. |
From: Sam V. <mr...@co...> - 2003-06-20 13:47:37
|
Matthias Andree writes: > Note also that FreeBSD 5 doesn't install c_rehash -- I will grab the one > from FreeBSD's courier port and stuff it into scripts/*. Is c_rehash > needed at install time only or later at run time as well? Only at compile time. > What testing needs to be done to bless gnupg 1.2.2 by the cone > ./configure script? The basics: sign message, encrypt message, check signature, decrypt, create keypair, sign keypair, export keys, import keys. |
From: Matthias A. <ma...@dt...> - 2003-06-20 09:38:51
|
Hi, I need the attached four trivial patches to the code to make the 20030618 snapshot of cone compile on FreeBSD 5.1, please integrate. The last one takes a little explanation: FreeBSD doesn't have "EPROTO" in its errno, I don't know where this comes from; so I chose to hardcode the string for now, but I guess it will have to be internationalized some day. So take care when merging the fourth patch. Note also that FreeBSD 5 doesn't install c_rehash -- I will grab the one from FreeBSD's courier port and stuff it into scripts/*. Is c_rehash needed at install time only or later at run time as well? What testing needs to be done to bless gnupg 1.2.2 by the cone ./configure script? TIA, -- Matthias Andree |
From: Sam V. <mr...@co...> - 2003-06-19 04:04:01
|
Download: http://www.courier-mta.org/download.php#cone Build 20030618 is a minor update to build 20030616, that addresses a few open issues. * Version number removed from the help file's name, so in the future after upgrading the online help link still continuse to work. * Cc: headers were not displayed in abbreviated header display with non-IMAP accounts. * Failed SSL negotiation with POP3 accounts may result in a crash. * If Cone was suspended while a server command was pending, after resuming a bogus timeout may result, closing the server connection. * A keyboard shortcut was missing in the encryption menu. |
From: Doug C. <dcl...@li...> - 2003-06-18 15:56:00
|
On Tue, Jun 17, 2003 at 12:22:50AM -0400, Sam Varshavchik wrote: > Perhaps your wchar.h defines these functions only if some preprocessor > symbol is set. My wchar.h defines these functions of __USE_GNU is set, and > features.h defines __USE_GNU if _GNU_SOURCE is set, which should be the > default. Guess I should have looked at that before. Here's some excerpts from wchar.h: #----------------- #if 0 /* XXX: not implemented */ size_t mbrlen __P((const char * __restrict, size_t, mbstate_t * __restrict)); size_t mbrtowc __P((wchar_t * __restrict, const char * __restrict, size_t, mbstate_t * __restrict)); int mbsinit __P((const mbstate_t *)); size_t mbsrtowcs __P((wchar_t * __restrict, const char ** __restrict, size_t, mbstate_t * __restrict)); size_t wcrtomb __P((char * __restrict, wchar_t, mbstate_t * __restrict)); #endif #----------------- #if 0 /* XXX: not implemented */ size_t wcsrtombs __P((char * __restrict, const wchar_t ** __restrict, size_t, mbstate_t * __restrict)); #endif #----------------- #if 0 /* XXX: not implemented */ int wcswidth __P((const wchar_t *, size_t)); int wcwidth __P((wchar_t)); #endif #----------------- Guess that settles it. Revision 1.12 in cvsweb for freebsd has this note: Implement the ISO C90 Amd.1 restartable wide and multibyte character manipulation functions mbrlen(), mbrtowc(), mbsinit(), mbsrtowcs(), wcrtomb(), wcsrtombs(). The release version of wchar.h in FreeBSD RELEASE-4.8 is 1.3, though. Looks like the required functions exist in the 5.0 train, but I don't have any 5.0 boxes around to test with. --Doug |
From: Lars N. <Ce...@gm...> - 2003-06-17 21:43:58
|
> Lars Noschinski writes: >> My local mail server has the FQDN "carrot.home.noschinski.de". If I create >> an account with this server, I get an "ERROR: Invalid argument" in the status >> bar. But if I use a shorter domain name (3 instead of 4 parts) via /etc/hosts >> or the IP address, cone can connect successfully. > > I have no problems creating an account on a server with a 4 part, 27 > character name. Hm, the problem seems to be more complex than I thought: If I add carrot.home.noschinski.de in /etc/hosts, I can connect. Ok, I will do three straces*: 4 parts via DNS, 4 parts via hosts and 3 parts via DNS. (Start cone, open account, [cancel login], quit). The main difference between the two DNS versions is that the final connect call, which returns the EINVAL (Invalid argument) in 4-parts-dns, is IPv6 in the 4 part versions, and IPv4 in the 3 parts version. And some additional tests show, that my system has some greater IPv6 problems (ping6 fails also with "Invalid argument"). So this is obviously no Cone problem and I'm really sorry for wasting your time. And yes, I will make a "Careful investigate 'bugs' (and do a strace)" wallpaper for my desktop ... -- Lars Noschinski -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! |
From: Sam V. <mr...@co...> - 2003-06-17 15:21:53
|
Lars Noschinski writes: > Hello! > > I've experienced another problem with Cone (0.51.20030616): > > My local mail server has the FQDN "carrot.home.noschinski.de". If I create > an account with this server, I get an "ERROR: Invalid argument" in the status > bar. But if I use a shorter domain name (3 instead of 4 parts) via /etc/hosts > or the IP address, cone can connect successfully. > > If I enter an invalid domain name, e.g. "invalid.home.noschinski.de" I get > "ERROR: Name or service not known", so the syntax check seem to be after the > domain name lookup. I have no problems creating an account on a server with a 4 part, 27 character name. |
From: Lars N. <Ce...@gm...> - 2003-06-17 14:09:34
|
Hello! I've experienced another problem with Cone (0.51.20030616): My local mail server has the FQDN "carrot.home.noschinski.de". If I create an account with this server, I get an "ERROR: Invalid argument" in the status bar. But if I use a shorter domain name (3 instead of 4 parts) via /etc/hosts or the IP address, cone can connect successfully. If I enter an invalid domain name, e.g. "invalid.home.noschinski.de" I get "ERROR: Name or service not known", so the syntax check seem to be after the domain name lookup. -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage! |