https://www.claws-mail.org/faq/api.php?action=feedcontributions&user=Ticho&feedformat=atom Claws Mail FAQ - User contributions [en] 2024-03-29T12:52:27Z User contributions MediaWiki 1.35.7 https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3088 GTK3 Porting Checklist 2019-03-27T00:54:47Z <p>Ticho: update</p> <hr /> <div>== Does not work ==<br /> <br /> * Color labels do not show actual color boxes in common prefs.<br /> <br /> *Using gtk_container_add() with GtkBox results in widgets not using full height available to them - gtk_box_pack_start() should be used instead. (Eventually, all GtkBoxes should be migrated to GtkGrid) Fixed so far:<br /> ** compose window textview<br /> ** prefsdialog page content area<br /> ** template preferences dialog<br /> <br /> * Folderview uses too bright colors for row backgrounds (alternating light gray and even lighter gray).<br /> <br /> * Quicksearch sometimes doesn't display the search type combobox and information button.<br /> <br /> * Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> * Fancy doesn't work, hangs indefinitely in webkit_web_view_new().<br /> <br /> * Vcalendar week/month views do not work, sometimes even crashes the whole program.<br /> <br /> * Network log window minimal requested size is too large. Same for Mainwindow.<br /> <br /> * About window won't shrink back if you increase its width. Opened https://bugzilla.gnome.org/show_bug.cgi?id=793407 for that.<br /> <br /> == Works, but is ugly ==<br /> <br /> * GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another like in GTK2.<br /> <br /> == Deprecated API ==<br /> <br /> * GtkHBox, GtkVBox, GtkTable -&gt; GtkGrid<br /> <br /> * Alertpanel needs to be rewritten to not use GTK_STOCK_*, but GtkIconTheme and named icons.<br /> <br /> * GtkUIManager is deprecated in GTK3, to be removed in GTK4<br /> &lt;pre&gt;<br /> #claws@Freenode on 2018-09-24:<br /> (@Ticho) well, for now, we could just stick our heads in the sand and pretend that GtkUIManager is still okay<br /> (@Ticho) we can start caring about it again once it's time to go from GTK3 to GTK4<br /> (@Ticho) (although I'm pretty sure our future selves will hate us for that) :)<br /> (@Ticho) but hopefully by then, there will be better available solutions - even if it was just this Amtk library being widely available and packaged in major distros<br /> (@claws) seems like a plan<br /> &lt;/pre&gt;</div> Ticho https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3085 GTK3 Porting Checklist 2018-09-24T09:51:07Z <p>Ticho: /* Does not work */</p> <hr /> <div>== Does not work ==<br /> <br /> * Color labels do not show actual color boxes in common prefs.<br /> <br /> *Using gtk_container_add() with GtkBox results in widgets not using full height available to them - gtk_box_pack_start() should be used instead. (Eventually, all GtkBoxes should be migrated to GtkGrid) Fixed so far:<br /> ** compose window textview<br /> ** prefsdialog page content area<br /> ** template preferences dialog<br /> <br /> * Folderview uses too bright colors for row backgrounds (alternating light gray and even lighter gray).<br /> <br /> * Folderview uses white text for folders without new messages in them, instead of black. Maybe related to bug #3880.<br /> <br /> * GtkCMCList has redrawing issues when mouse scrolling.<br /> <br /> * Quicksearch sometimes doesn't display the search type combobox and information button.<br /> <br /> * Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> * Fancy doesn't work, hangs indefinitely in webkit_web_view_new().<br /> <br /> * Messageview doesn't show Mimeview with body part icons on the right.<br /> <br /> * Vcalendar week/month views do not work, sometimes even crashes the whole program.<br /> <br /> * Network log window minimal requested size is too large. Same for Mainwindow.<br /> <br /> * About window won't shrink back if you increase its width. Opened https://bugzilla.gnome.org/show_bug.cgi?id=793407 for that.<br /> <br /> == Works, but is ugly ==<br /> <br /> * GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another like in GTK2.<br /> <br /> == Deprecated API ==<br /> <br /> * GtkHBox, GtkVBox, GtkTable -&gt; GtkGrid<br /> <br /> * Alertpanel needs to be rewritten to not use GTK_STOCK_*, but GtkIconTheme and named icons.<br /> <br /> * GtkUIManager is deprecated in GTK3, to be removed in GTK4<br /> &lt;pre&gt;<br /> #claws@Freenode on 2018-09-24:<br /> (@Ticho) well, for now, we could just stick our heads in the sand and pretend that GtkUIManager is still okay<br /> (@Ticho) we can start caring about it again once it's time to go from GTK3 to GTK4<br /> (@Ticho) (although I'm pretty sure our future selves will hate us for that) :)<br /> (@Ticho) but hopefully by then, there will be better available solutions - even if it was just this Amtk library being widely available and packaged in major distros<br /> (@claws) seems like a plan<br /> &lt;/pre&gt;</div> Ticho https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3084 GTK3 Porting Checklist 2018-09-24T09:48:29Z <p>Ticho: /* Deprecated API */ GtkUIManager</p> <hr /> <div>== Does not work ==<br /> <br /> * Color labels do not show actual color boxes in common prefs.<br /> <br /> *Using gtk_container_add() with GtkBox results in widgets not using full height available to them - gtk_box_pack_start() should be used instead. (Eventually, all GtkBoxes should be migrated to GtkGrid) Fixed so far:<br /> ** compose window textview<br /> ** prefsdialog page content area<br /> ** template preferences dialog<br /> <br /> * Folderview uses too bright colors for row backgrounds (alternating light gray and even lighter gray).<br /> <br /> * Folderview uses white text for folders without new messages in them, instead of black. Maybe related to bug #3880.<br /> <br /> * GtkCMCList has redrawing issues when mouse scrolling.<br /> <br /> * Quicksearch sometimes doesn't display the search type combobox and information button.<br /> <br /> * Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> * Fancy doesn't work, hangs indefinitely in webkit_web_view_new().<br /> <br /> * Messageview doesn't show Mimeview with body part icons on the right.<br /> <br /> * Vcalendar week/month views do not work, debug messages look like a new Claws Mail instance is trying to start when trying to display them.<br /> <br /> * Network log window minimal requested size is too large. Same for Mainwindow.<br /> <br /> * About window won't shrink back if you increase its width. Opened https://bugzilla.gnome.org/show_bug.cgi?id=793407 for that.<br /> <br /> == Works, but is ugly ==<br /> <br /> * GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another like in GTK2.<br /> <br /> == Deprecated API ==<br /> <br /> * GtkHBox, GtkVBox, GtkTable -&gt; GtkGrid<br /> <br /> * Alertpanel needs to be rewritten to not use GTK_STOCK_*, but GtkIconTheme and named icons.<br /> <br /> * GtkUIManager is deprecated in GTK3, to be removed in GTK4<br /> &lt;pre&gt;<br /> #claws@Freenode on 2018-09-24:<br /> (@Ticho) well, for now, we could just stick our heads in the sand and pretend that GtkUIManager is still okay<br /> (@Ticho) we can start caring about it again once it's time to go from GTK3 to GTK4<br /> (@Ticho) (although I'm pretty sure our future selves will hate us for that) :)<br /> (@Ticho) but hopefully by then, there will be better available solutions - even if it was just this Amtk library being widely available and packaged in major distros<br /> (@claws) seems like a plan<br /> &lt;/pre&gt;</div> Ticho https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration&diff=3079 Installation and Configuration 2018-07-14T05:23:27Z <p>Ticho: /* What do I need to compile Claws Mail? */ updated required GTK+ version to 2.24.x</p> <hr /> <div>=== What do I need to compile Claws Mail? ===<br /> <br /> &lt;u&gt;Required:&lt;/u&gt;<br /> <br /> ; Any POSIX compliant UNIX or similar OS eg. Linux, FreeBSD, Solaris, Mac OS X<br /> ; GTK+ 2.24.x or later <br /> ; A recent ANSI C compiler (gcc 2.7.2.3 should also work) <br /> <br /> Otherwise ./configure will fail.<br /> <br /> &lt;u&gt;Optional requirements:&lt;/u&gt;<br /> <br /> ; compface : for X-Face support<br /> ; GnuPG 1.2.1 or later and GPGME 0.4.5 or later : for GnuPG support (see [[Installation_and_Configuration#How_do_I_enable_GPG_support_in_Claws_Mail.3F|How do I enable GPG support in Claws Mail?]])<br /> ; GnuTLS 2.2 or later : for SSL/TLS support<br /> ; libEtPan! 0.57 or later : for IMAP4 support and NNTP support<br /> ; OpenLDAP 2.0.7 or later : for LDAP support<br /> ; Enchant (and dictionaries) : for spell-checker support<br /> ; J-Pilot : for J-Pilot support<br /> ; D-Bus : for interprocess communication support<br /> ; Network Manager : for support for detection of network connection changes<br /> <br /> === How to build Claws Mail on Mac OS X? ===<br /> <br /> The steps to build Claws Mail on Mac OS X have been originally posted by Damien Krotkine, on his dedicated page and his former post to his blog. None of them are avaliable anymore. The procedure below is based on his work.<br /> There's an additional [http://lists.claws-mail.org/pipermail/users/2012-September/003648.html procedure posted on users list] by Stainless Steel Rat.<br /> <br /> &lt;u&gt;Compiling against X.org&lt;/u&gt;<br /> <br /> Installing Claws Mail will require X.org, GTK+ 2.6, and a working POSIX building environment (including the gcc/make toolchain). Let's consider using Fink to install the software requirements on your Mac OS X system.<br /> <br /> Install Fink (http://www.finkproject.org/).<br /> <br /> Download and unpack the Claws Mail sources.<br /> <br /> Run &lt;code&gt;./configure --prefix=/sw&lt;/code&gt; to quickly see what packages are missing, and install them using Fink (&lt;code&gt;fink&lt;/code&gt; or &lt;code&gt;FinkCommander&lt;/code&gt;). Some of the required packages are available in unstable only, so you might need to enable unstable packages in the Fink prefs, then do &lt;code&gt;fink selfupdate scanpackages&lt;/code&gt;. You'll need a complete gcc/make toolchain as well as few extra requirements:<br /> &lt;pre&gt;<br /> xorg (binary)<br /> pkgconfig (binary)<br /> glib2-dev (compiled from source - we recommend &gt;=2.10 from unstable)<br /> gtk+2-dev (compiled from source - must be &gt;=2.6 from unstable)<br /> &lt;/pre&gt;<br /> <br /> Getting IMAP support in Claws Mail requires libetpan, but there is no Fink package for it. Darwin ports provide one, but let's compile it from source directly. Get the tarball from the etpan homepage (http://sourceforge.net/projects/libetpan). Unpack it, and compile the sources with:<br /> &lt;pre&gt;<br /> % ./configure --prefix=/sw &amp;&amp; make &amp;&amp; sudo make install<br /> &lt;/pre&gt;<br /> <br /> If you need SSL support (for IMAP for instance), install openssl-dev, via Fink, but before that, make sure you enable &quot;Use unstable cryptography packages&quot; in the Fink preferences.<br /> <br /> You could also enable support for compface, libgnomeprint/libgnomeprintui, aspell, jpilot, gnupg and gpgme (&gt;=1.0.0) by installing the appropriate packages from Fink.<br /> <br /> If you want to compile any of the dillo-viewer, spamassassin or bogofilter plugins with Claws Mail 2.9.2, you have to apply this patch: http://www.mollux.org/projects/contrib/claws-mail/patches/pending/claws-mail-osx-build-core-plugins-rev1.diff into the Claws Mail sources directory. SpamAssassin can be installed from &lt;code&gt;cpan&lt;/code&gt; (see http://developer.apple.com/server/fighting_spam.html) or from the sources.<br /> <br /> Now configure the sources:<br /> &lt;pre&gt;<br /> % ./configure --prefix=/sw --disable-trayicon-plugin<br /> &lt;/pre&gt;<br /> <br /> If &lt;code&gt;./configure&lt;/code&gt; runs well, it should output something like this:<br /> &lt;pre&gt;<br /> claws-mail 2.9.2<br /> <br /> JPilot : yes<br /> LDAP : yes<br /> OpenSSL : yes<br /> iconv : yes<br /> compface : yes<br /> IPv6 : yes<br /> GNU/aspell : yes<br /> IMAP4 : yes<br /> Crash dialog : no<br /> Libgnomeprint : yes<br /> LibSM : no<br /> Manual : yes<br /> Plugins : dillo-viewer pgpinline pgpmime pgpcore bogofilter spamassassin<br /> Maemo build : no<br /> Config dir : .claws-mail<br /> The binary will be installed in /sw/bin<br /> &lt;/pre&gt;<br /> <br /> Now let's build Claws Mail:<br /> &lt;pre&gt;<br /> % make<br /> &lt;/pre&gt;<br /> <br /> And install it:<br /> &lt;pre&gt;<br /> % sudo make install<br /> &lt;/pre&gt;<br /> <br /> If everything compiled correctly, you should be able to run Claws Mail. You first need to start X: as we've installed the Fink X.org server, you have to run &lt;code&gt;startx&lt;/code&gt;, and now from within a &lt;code&gt;xterm&lt;/code&gt;, run &lt;code&gt;claws-mail&lt;/code&gt;.<br /> <br /> Most of the extra plugins can be installed: you'd need to download and unpack the extra plugin sources tarball and enter the commands below after entering any of the plugins directories you need.<br /> <br /> Available plugins:<br /> &lt;pre&gt;<br /> att_remover<br /> attachwarning<br /> cachesaver<br /> fetchinfo_plugin<br /> gtkhtml2_viewer (libgtkhtml2 required)<br /> mailmbox<br /> notification_plugin<br /> pdf_viewer (poppler &gt;=0.5.1 required)<br /> perl_plugin<br /> smime<br /> synce_plugin<br /> vcalendar<br /> &lt;/pre&gt;<br /> <br /> The following plugins can't be used yet:<br /> &lt;pre&gt;<br /> acpi_notifier (probably not applicable, plugin doesn't compile anyway)<br /> newmail (plugin won't load)<br /> rssyl (plugin will crash)<br /> &lt;/pre&gt;<br /> <br /> Commands to build and install a plugin:<br /> &lt;pre&gt;<br /> % ./configure --prefix=/sw &amp;&amp; sudo make install<br /> &lt;/pre&gt;<br /> <br /> === How do I set up Claws Mail? ===<br /> <br /> When you run Claws Mail for the first time, the Installation Wizard will appear and prompt you for the minimum required information necessary to start using Claws Mail in less than 5 minutes.<br /> <br /> === Why did the creation of the mailbox fail? ===<br /> <br /> Claws Mail reports such an error if it can't create the default mailboxes (inbox, outbox, etc ...). This can be because &lt;homedir&gt;/Mail already contains files with the same names. This occurs when switching from Kmail to Claws Mail, in this case backup and remove the existing Mail directory or use another name for the Claws Mail mail directory.<br /> <br /> === How do I create a new account? ===<br /> <br /> You can add an account by using the menu item '/Configuration/Create new account'<br /> <br /> === Why does Claws Mail not delete my mails when I press &quot;delete&quot;? I set a filter, and Claws Mail does not filter. I moved a mail to a different mailbox and it did not move. ===<br /> <br /> You have the configuration option 'Execute immediately when moving or deleting messages' on the /Configuration/Preferences/Display/Summaries page disabled.<br /> <br /> === Can I set up special addresses/ports for my mailserver / newsserver? ===<br /> <br /> Yes, you can. In the Account preferences, on the 'Advanced' tab you can specify the port addresses that you want to use.<br /> <br /> === Does Claws Mail have options for threading messages? ===<br /> <br /> Yes. You can switch it on and off in the View Menu, just select &quot;Thread View&quot; or press Ctrl+T. (This only affects the currently selected folder; i.e. it is a folder property.)<br /> <br /> === Can I create multiple levels of subfolders to store mail? ===<br /> <br /> Absolutely. This is no problem.<br /> <br /> 1. right-click on an existing folder<br /> <br /> 2. choose 'Create new folder ...' from the resulting menu<br /> <br /> 3. type in a name for your new folder (you can check 'inherit properties from parent folder' if you want to do that)<br /> <br /> === How do I apply a patch after downloading it? ===<br /> <br /> Copy patch to Claws Mail directory Apply the patch:<br /> &lt;pre&gt;&lt;nowiki&gt;<br /> % patch -p0 &lt; some.patch<br /> &lt;/nowiki&gt;&lt;/pre&gt;<br /> Or, if it's gzipped:<br /> &lt;pre&gt;&lt;nowiki&gt;<br /> % gzip -dc some.patch.gz | patch -p0<br /> &lt;/nowiki&gt;&lt;/pre&gt;<br /> <br /> Run &lt;code&gt;./autogen.sh [OPTIONS]&lt;/code&gt;, then &lt;code&gt;make&lt;/code&gt;.<br /> <br /> === How do I compile in support for compface pictures? ===<br /> <br /> You have to have a package called libcompface installed, so this is available for compiling into Claws Mail. You can find out more and download it at http://freshmeat.net/projects/compface/ . Also, Tim Jackson has a spec file, which you can use to build an RPM of compface, at http://www.timj.co.uk/linux/rpms.php .<br /> <br /> === How do I make my own compface image? ===<br /> <br /> You can use the gif2xface.pl script, which converts a 48x48 gif to the format suitable for compface. This script can be found in the 'tools' directory, along with a README. It is also available from this site: http://www.claws-mail.org/tools.php.<br /> You can also let Claws Mail create it by itself from a .xbm file.<br /> <br /> Or, if that doesn't work.<br /> <br /> 1. Find/create 48x48 image, png works well.&lt;br&gt;<br /> 2. Convert it to pbm without dither (this also makes it black and white: convert -dither image.png image.pbm&lt;br&gt;<br /> 3. Convert the pbm to icon: pbmtoicon image.pbm &gt; image.icon&lt;br&gt;<br /> 4. Edit the icon file in a text editor. Delete any comment at the beginning, and put the values in colums of three with comma separation like so:<br /> <br /> 0xfoo, 0xfoo, 0xfoo,<br /> <br /> 5. The final line shouldn't have a comma ending it <br /> <br /> 0xfoo, 0xfoo, 0xfoo<br /> <br /> 6. Make certain there are exactly 48 lines and save.&lt;br&gt;<br /> 7. Run compface on it: compface &lt;image.icon&gt; image.xface&lt;br&gt;<br /> 8. Then follow the instructions below.<br /> <br /> Or you can take the super easy way out and just use this website:<br /> <br /> http://www.dairiki.org/xface/<br /> <br /> === How can I make Claws Mail send my compface image in the mails? ===<br /> <br /> On the Send page of the Account preferences check 'Add user-defined header' and press the 'Edit' button. In the dialogue that appears, add a header named &quot;X-Face&quot; and fill the value field with your face data. Alternatively, you can select a .xbm file in this dialog. Note that if you paste the data from a terminal into the field some spurious newlines can be added, and these can mangle your face, be careful.<br /> <br /> === How can I make Claws Mail send a colour Face image in the mails? ===<br /> <br /> Face headers contain base64-encoded 48x48 PNG image, and don't have any external dependency at compile-time or at run-time. You'll find more details here:<br /> http://quimby.gnus.org/circus/face/<br /> <br /> Once you have your .png file that complies to the specs of the Face header (max length 725 bytes), go to the Send page of the Account preferences, check 'Add user-defined header' and press the 'Edit' button. In the dialogue that appears, add a header named &quot;Face&quot; and click the 'From file' button to select your .png file.<br /> <br /> Note: there's nothing that prevents you from having both a X-Face (see previous FAQ entry) and a Face header in your mails.<br /> <br /> === How do I make my own Face image? ===<br /> <br /> For a color face image, a simple command-line use is all that's needed:<br /> <br /> home:~$ djpeg my.jpg | ppmnorm | pnmscale -width 48 -height 48 | ppmquant 9 | pnmtopng &gt; my.png<br /> <br /> The number after 'ppmquant' can be changed as needed until you have an image that is as close to 725 bytes as possible. It cannot be larger than 725 bytes.<br /> <br /> === How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program? ===<br /> <br /> In the settings part of the program, use &lt;code&gt;claws-mail --compose &quot;%t?subject=%s&amp;body=%d&quot;&lt;/code&gt;<br /> <br /> ; Specific options for typical browsers :<br /> ; Firefox 3<br /> In Firefox go to /Edit/Preferences/Applications. Search for 'mailto'. Under 'Action', select 'Use other...', and locate and select the 'claws-mail' executable, (typically /usr/bin/claws-mail or /usr/local/bin/claws-mail).<br /> ; Firefox 2<br /> Enter 'about:config' in the address bar.<br /> Add or Edit the following values:<br /> &lt;pre&gt;network.protocol-handler.external.mailto : default : boolean : true<br /> network.protocol-handler.app.mailto : user set : string : claws-mail&lt;/pre&gt;<br /> ; Opera:<br /> &lt;pre&gt;claws-mail --compose &lt;nowiki&gt;mailto:%t?[subject=%s&amp;][body=%m]&lt;/nowiki&gt;&lt;/pre&gt;<br /> ; Galeon:<br /> &lt;pre&gt;claws-mail --compose &lt;nowiki&gt;&quot;mailto:%t?subject=%s&amp;body=%d&quot;&lt;/nowiki&gt;&lt;/pre&gt;<br /> ; Konqueror : See [[Installation_and_Configuration#konqueror|How do I make Claws Mail the default mail application for KDE]]?<br /> <br /> === How do I enable GPG support in Claws Mail? ===<br /> <br /> GunPG support requires GnuPG &gt;= 0.4.x and GPGME &gt;= 1.x.x.<br /> <br /> Caution: according to some user experience, you might need to install GnuPG 1.x and GPGME 1.x.x in a separate location (isolated from the system ones), and to make sure GPGME is configured to use this specific GnuPG binary (`configure --prefix=/path/to/the/isolated/gpg1 --with-gpg=/path/to/the/isolated/gpg1/bin/gpg`). This is at least the case on RHEL6 and variants (SL6/CentOS6, Fedora 11+, probably RHEL5 and variants too), who come with GnuPG2 only, and where GPGME is configured to use `/usr/bin/gpg2` (see `gpgme-config --get-gpg`)- so it's useless on these systems to install GnuPG 1.x in system paths and to make sure the `gpg` found on the PATH points to the real GnuPG 1 version. Once this is done, GnuPG 1 and system's GnuPG 2 can both work fine with user's .gnupg/ config (GnuPG 1/2 are designed to do so). You'll need to update your environment where PATH and LD_LIBRARY_PATH must point to /path/to/the/isolated/gpg1 subdirectories prior to start `claws-mail`.<br /> <br /> You need to load the PGP/Core, PGP/MIME, and PGP/inline plugins. '/Configuration/Plugins/Load plugin'.<br /> <br /> === Mutt does not recognize Claws Mail's MH structure ===<br /> <br /> For this to work you need to use the &lt;code&gt;touch&lt;/code&gt; command in every MH folder. &lt;code&gt;touch&lt;/code&gt; the file &lt;code&gt;.xmhcache&lt;/code&gt; and Mutt should do just fine.<br /> <br /> === How can I make Claws Mail notify me when new mail arrives? ===<br /> <br /> Go to '/Configuration/Preferences/Common', on the 'Receive' tab use the settings for 'Run command when new mail arrives'. You can also use the Acpi-notifier (if you have a supported laptop) or the Notification plugin, which are available on the [http://www.claws-mail.org/plugins.php Plugins page].<br /> <br /> === Can I use a spell checker with Claws Mail? ===<br /> <br /> Install Enchant (with dictionaries) and run &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> === I checked out the sources using git and cant find any configure script. What can I do? ===<br /> <br /> The git versions are meant to be used by developers rather than ''normal'' users, so the source (or binary) distributions are easier to use.<br /> <br /> - Yeah, but the latest features from git really look sexy...<br /> <br /> You need to generate the configure script by running &lt;code&gt;./autogen.sh&lt;/code&gt;. Building from git requires a lot of extra dependencies that the release tarballs don't have.<br /> <br /> === Running &quot;autogen.sh&quot; gives errormessages that AM_PATH_GDK_PIXBUF or AM_PATH_(whatever) is not found. What can I do? ===<br /> <br /> There are some *.m4 files in the &lt;code&gt;ac/missing&lt;/code&gt; directory. Try to copy them into the &lt;code&gt;ac&lt;/code&gt; directory and run &lt;code&gt;autogen.sh&lt;/code&gt; again.<br /> <br /> If there are still some .m4 files not found (e.g. those from Gtk), try to run<br /> % locate m4 | less<br /> or<br /> % locate aclocal | less<br /> to find additional directories containing those macros. If you find e.g. a &quot;gtk.m4&quot; in &quot;/opt/gnome/share/aclocal&quot;, change following line in &quot;autogen.sh&quot; from<br /> aclocal -I ac \<br /> to<br /> aclocal -I ac -I /opt/gnome/share/aclocal \<br /> and run it again.<br /> <br /> === I dont want to compile in support for ... any longer, but after running &lt;code&gt;configure&lt;/code&gt;, those libraries are still used. What can I do? ===<br /> <br /> Remove the &lt;code&gt;config.cache&lt;/code&gt; file and run &lt;code&gt;configure&lt;/code&gt; again. You should also use &lt;code&gt;make clean&lt;/code&gt; to avoid undefined references.<br /> <br /> === How can I select different applications to open with specific MIME types? ===<br /> <br /> The MIME-type-&gt;application associations are kept in &lt;code&gt;~/.mailcap&lt;/code&gt; and &lt;code&gt;/etc/mailcap&lt;/code&gt;.<br /> <br /> === How can I change the suggested mimetype for attachments I am sending? ===<br /> <br /> The extension-&gt;MIME-type associations are kept in either &lt;code&gt;/usr/share/mime/globs&lt;/code&gt; or &lt;code&gt;/etc/mime.types&lt;/code&gt;, depending on your system. &lt;br&gt;Right-click an attachment in the compose window's &quot;Attachments&quot; tab, and select Properties to change the MIME-type.<br /> <br /> === Why is the folder list not updated after I manually moved/copied folders? ===<br /> <br /> You need to update Claws Mail's cache. Right click on the mailbox and choose &quot;Check for new folders&quot;.<br /> <br /> === How can I revert original settings, e.g. for fonts, keybindings, etc.? ===<br /> <br /> Claws Mail keeps its configuration files in &lt;code&gt;$HOME/.claws-mail/clawsrc&lt;/code&gt; and creates default entries, if none are found. So the easiest way is to quit claws-mail, temporarily renaming your &lt;code&gt;$HOME/.claws-mail&lt;/code&gt; e.g. to &lt;code&gt;*.bak&lt;/code&gt; and restarting claws-mail in order to get default entries.<br /> <br /> === What environment variables have effect on Claws Mail? ===<br /> <br /> ; Here are the most common variables : <br /> ; HOME : location of .claws-mail (config directory) and default folder for Mailboxes.<br /> ; LANG<br /> ; LC_ALL<br /> ; LC_CTYPE<br /> ; LC_MESSAGES : locale settings, e.g. language and date format.<br /> <br /> For a more detailed list see manual page (man claws-mail).<br /> <br /> === Why are special characters (e.g. umlauts) not displayed correctly? ===<br /> <br /> In most cases, this is caused by emails with broken encodings. You can try to force it using the View/Character Encoding submenu.<br /> <br /> === How can I convert my old mailbox / addressbook from (some mail client). ===<br /> <br /> If you can export your old mailbox to &lt;code&gt;MH&lt;/code&gt; or &lt;code&gt;mbox&lt;/code&gt; format it can be imported directly into Claws Mail. If the mailbox is in &lt;code&gt;MH&lt;/code&gt; format you can use /File/Add Mailbox/MH... If the mailbox is in &lt;code&gt;mbox&lt;/code&gt; format, it can be imported with /File/Import mbox file/...<br /> <br /> The Claws Mail addressbook supports direct import from Mutt, Pine, and LDIF and vCard formats, which are standard formats exported by most email clients.<br /> <br /> In addition, several scripts are provided on the Claws Mail [http://www.claws-mail.org/tools.php website] to convert various mailbox and addressbook formats.<br /> <br /> If your old addressbook only supports CSV export, and it is not supported by the &lt;code&gt;csv2addressbook.pl&lt;/code&gt; script on the [http://www.claws-mail.org/tools.php website], you can convert it to vCard format using this [http://homepage.mac.com/phrogz/CSV2vCard_v2.html online tool]. Another [http://labs.brotherli.ch/vcfconvert/ online tool] can convert from vCard to LDIF format.<br /> <br /> === What configuration files are there, and what are they used for? ===<br /> <br /> The default location for Claws Mail's configuration files is &lt;code&gt;$HOME/.claws-mail/&lt;/code&gt;. (The command '&lt;code&gt;claws-mail --config-dir&lt;/code&gt;' shows the location.) They are in plain text format and quite easy to understand, so don't fear to take a look into them using a text editor.<br /> <br /> ; clawsrc : main configuration: nearly all options from the settings window, e.g. mailbox location, font entries, etc.<br /> ; accountrc : settings for POP/IMAP/NNTP/local accounts<br /> ; actionsrc : user defined actions<br /> ; customheaderrc : user defined header lines<br /> ; dispheaderrc : headers to display above the mail body<br /> ; folderitemrc : folder specific settings<br /> ; folderlist.xml : additional folder specific settings, e.g. hiding read messages, sort order, etc.<br /> ; matcherrc : filtering, processing and scoring settings<br /> ; menurc : Key bindings<br /> ; addrbook/addrbook-*.xml : contents of your address book (before version 3.1.0 the address book files were kept directly in &lt;code&gt;.claws-mail/&lt;/code&gt;)<br /> <br /> === What's a good method for printing an e-mail? ===<br /> <br /> Most precompiled packages will use the libgnomeprintui library or more for more recent builds with GTK 2.10.xx the built in GTK 2.10 printing support (which will be the default), which will allow you to print your emails simply with the same interface as Gnome (or GTK) apps. It will be compiled in if you have libgnomeprint-dev and libgnomeprintui-dev packages installed, or have GTK 2.10.xx<br /> <br /> If Claws Mail hasn't been compiled with libgnomeprintui or GTK 2.10.xx printing support, you can use enscript. Use &lt;code&gt;enscript %s&lt;/code&gt; to print everything on one page, or &lt;code&gt;enscript -U2 %s&lt;/code&gt; for printing two logical pages on one physical page.<br /> <br /> As a more pretty alternative: Use [http://muttprint.sf.net muttprint]. The print-command would then look something like this: &lt;code&gt;muttprint -f %s&lt;/code&gt;<br /> <br /> Using KDE or gv you also get a &quot;print preview&quot; for free! <br /> <br /> Try &lt;code&gt;muttprint -f %s -p - |kghostview -&lt;/code&gt; or &lt;code&gt;muttprint -f %s -p - |gv -&lt;/code&gt; respectively... BTW: muttprint, like enscript, may optionally print two logical pages on one physical page. Just have a look at the docs!<br /> <br /> === Claws refuses to send mail, and says the queue folder cannot be found ===<br /> <br /> This problem happens for people using only IMAP accounts.<br /> Claws Mail requires a queue folder for outgoing mail. If there is none, it will display an error message (&quot;can't find queue folder&quot;) and refuse to send mail.<br /> This feature prevents loss of messages, in the case Claws Mail would be killed while sending an e-mail, or should there be a network problem. It provides extra security against data loss.<br /> <br /> You are advised to create a local folder (/File/Add Mailbox/MH). Outgoing messages will be queued there, and sending will work.<br /> <br /> You can also decide not to use a local folder for the queue, and use the IMAP server for this. It is not recommended because Claw Mail's queued messages have a special header that might not be handled correctly by the IMAP server. <br /> If you really want to create a queueing folder in an IMAP server, create an ordinary folder in it. Right click on it, select /Properties/, and change /Type/ to be &quot;Queue&quot;.<br /> (Might be unneeded : Go to /Configuration/Edit accounts/, select your account, click /Edit/, click /Advanced/. On this screen you can tick /Put queued messages in/ and select the folder you have created.)<br /> <br /> === What is the purpose of this bizarre &quot;Enable Alternate Dictionary&quot; option? ===<br /> <br /> It is useful only if you routinely compose messages that use two or more languages. If this option is enabled, then when you switch to another language, the last one you used is not swapped out from memory, thus, when you switch again to it, there is no delay. Moreover, whenever you use two dictionaries, if you check a word and if the spell checker considers it misspelled in the current language, you can switch to the alternate language and recheck the word in one operation by selecting the &quot;Check with ALTERNATE_LANGUAGE&quot; item (keyboard short-cut: &lt;x&gt;) in the suggestions menu. This is very handy when the message contains paragraphs in two languages.<br /> <br /> === Why doesn't the spell checker have a more traditional user interface, like KMail, Evolution etc? ===<br /> <br /> Because the developer (Melvin Hadasht) noted that by using the keyboard shortcuts the spell checking can be done faster while typing (more on that below). Moreover, there is the option &lt;Spelling/Check All or Check selection&gt; allows to do a spell checking of the whole text or just a selection. Just keep an eye where the suggestions menu shows up to look at the misspelled word, then hit one of the letters corresponding to the suggestion (&amp;lt;a&amp;gt; through &amp;lt;p&amp;gt;, press also &lt;ALT&gt; to make the selected suggestion listed as the first suggestion the next time you do exactly the same mistake --- this is the &quot;learn by mistake&quot; feature), or hit &lt;r&gt; to type a replacement, or hit &lt;ALT-SPACE&gt; to accept the word in the current message, or hit &lt;ALT-RETURN&gt; to accept the word and to add it definitively to your personal dictionary associated to this language. If you have enabled the &quot;Alternate Dictionary&quot;, you can switch to it by hitting &lt;x&gt;.<br /> <br /> If you prefer checking while you type, just bind the &lt;Spelling/Check backwards misspelled word&gt; and &lt;Spelling/Forward to next misspelled word&gt; to two quick keyboard short cuts. Then, as soon as you mistype a word, call the &lt;Check backwards...&gt; short-cut ---you do not need to move the cursor--- and without using the mouse select the suggestion. As Enchant does a good job at suggesting a replacement, you will often end to type &lt;a&gt;, and as the cursor did not move, just continue typing. In contrast, the other option, &lt;Forward to next...&gt; does move the cursor. This is because if you have text after the cursor, that also means in general that you are only editing a message, and not writing it, so advancing the cursor to the misspelled word is in general the wanted behaviour.<br /> &lt;div id=konqueror&gt;<br /> <br /> === How do I make Claws Mail the default mail application for KDE? ===<br /> <br /> KDE does not support passing the full URL to a mailer (see [http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=658 bug 658] and the corresponding [http://bugs.kde.org/show_bug.cgi?id=81598 KDE bug entry]).<br /> But there is a workaround - do the following as root:<br /> &lt;pre&gt;<br /> wget http://www.claws-mail.org/tools/claws-mail-compose.pl<br /> mv claws-mail-compose.pl /usr/local/bin<br /> chmod +x /usr/local/bin/claws-mail-compose.pl<br /> &lt;/pre&gt;<br /> Then go to the KDE Control Center -&gt; KDE Components -&gt; Component Chooser -&gt; Email Client, choose &quot;Use a different email client&quot; and enter the following into the textbox:<br /> &lt;pre&gt;<br /> /usr/local/bin/claws-mail-compose.pl --to=&quot;%t&quot; --cc=&quot;%c&quot; --bcc=&quot;%b&quot; --subject=&quot;%s&quot; --body=&quot;%B&quot; --attach=&quot;%A&quot;<br /> &lt;/pre&gt;<br /> <br /> If your binary has a name other than &quot;claws-mail&quot;, you must append another parameter:<br /> &lt;pre&gt;<br /> --claws-mail=&quot;/usr/bin/claws-mail&quot;<br /> &lt;/pre&gt;<br /> where /usr/bin/claws-mail is the full path to claws-mail on your system.<br /> <br /> In case you don't want that perlscript or you can't use it - there is this alternative. But be aware that passing multiple lines or non-standard characters to Claws Mail from an application (e.g. konqueror trying to send form-data via email) will '''not''' work!<br /> &lt;pre&gt;<br /> claws-mail --compose &lt;nowiki&gt;&quot;~mailto:%t?cc=%c&amp;bcc=%b&amp;subject=%s&amp;body=%B&quot; --attach &quot;%A&quot;&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> Replace &quot;claws-mail&quot; with the actual name of your binary here as well.<br /> &lt;/div&gt;<br /> <br /> === Why does Claws Mail tell me that a gpg signature has expired? ===<br /> <br /> The sender used a key with a time limit, you have to update your keyring regularly to receive the updated signatures, e.g. like this: <br /> <br /> &lt;code&gt;gpg --refresh-keys&lt;/code&gt;<br /> <br /> Note: Most keyservers have problems syncing OpenPGP type keys (see http://keyserver.kjsl.com/~jharris/keyserver.html). It is recommended to switch to SKS keyservers, e.g. subkeys.pgp.net or sks.keyserver.penguin.de .<br /> <br /> <br /> === Why does Claws Mail tell me that there is one unread message in some folders? ===<br /> <br /> If the message count in a folder indicates that you have one unread message but all are marked as read you have to do the following: Right click on toplevel MH folder and use &quot;Check for new messages&quot;, or use '/View/Update Summary'<br /> <br /> === How can I use my free Hotmail, Yahoo, or AOL email account via Claws Mail? ===<br /> <br /> [http://www.freepops.org/en/ FreePOPs] should allow you to create kind of a &quot;bridge&quot; between these proprietary email services and Claws Mail. Simply install FreePOPs, which is probably packaged in your distribution and configure it. After that, you can add an POP3 account to Claws Mail, which receiving server will be &lt;code&gt;localhost&lt;/code&gt; and set the port to use to &lt;code&gt;2000&lt;/code&gt; in the Advanced tab. The username to use consists of a complete email address, like &lt;code&gt; johndoe@hotmail.com&lt;/code&gt;, so that FreePOP can know which type of account it is. For more information, see [http://www.freepops.org/en/files/html-manual/ FreePOPs' user manual].<br /> <br /> === Does Claws Mail work with Gmail accounts? ===<br /> <br /> Yes, provided that you have enabled POP or IMAP access in your Gmail account.<br /> <br /> See:&lt;br&gt;<br /> all about POP access: http://gmail.google.com/support/bin/topic.py?topic=12805&lt;br&gt;<br /> enabling POP in Gmail: http://gmail.google.com/support/bin/answer.py?answer=13273&lt;br&gt;<br /> configure other email client for POP access: http://mail.google.com/support/bin/answer.py?answer=13287&lt;br&gt;<br /> <br /> all about IMAP access: http://gmail.google.com/support/bin/topic.py?topic=12806&lt;br&gt;<br /> enabling IMAP in Gmail: http://gmail.google.com/support/bin/answer.py?answer=77695&amp;topic=13294&lt;br&gt;<br /> configure other email clients for IMAP access: http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=78799&lt;br&gt;<br /> <br /> Information about using Claws with Gmail effectively: http://www.claws-mail.org/faq/index.php?title=Using_Claws_with_Gmail<br /> <br /> === Claws Mail doesn't retrieve emails from my Gmail (POP3) account. Sending messages doesn't work either. What can I do? ===<br /> <br /> Try prefixing your user name, which is usually your email address, with 'recent:' (without the quotes).<br /> <br /> Also make sure that under the 'Send' tab of your Claws Mail Account settings , the 'Authenticate with POP3 before sending' option is turned off.<br /> <br /> Finally, be aware that if the 'Remove messages on server when received' option is set in the 'Receive' tab of your Claws Mail Account, when you retrieve your messages they will be removed from the Gmail 'All emails' folder and they won't be available anymore from the Gmail web interface.<br /> <br /> === Can I have different mailboxes for my accounts even though they aren't IMAP or News? ===<br /> <br /> Yes, you can.<br /> <br /> Use File -&gt; Add mailbox -&gt; MH<br /> <br /> Then in the account preferences on the 'receive' tab set the inbox, on the 'advanced' tab set up the other folders.<br /> <br /> === How can I permanently delete messages? ===<br /> <br /> When you press the [del] key, the selected messages are moved to the Trash folder. You can, of course, empty the trash at any time by using the Trash folder's contextual menu.<br /> <br /> If, however, you want to permanently delete the message without moving it to trash, you have two options:<br /> ;Delete menu: First possibility is to select the /Message/Delete menu item in the main window, (to which you can assign a keyboard shortcut, like [shift+del]), or the message's context menu entry.<br /> ;Trash subfolder: If you systematically want to permanently delete messages from a folder, (for instance, your Junk folder that contains spam messages), you should create that folder as a subfolder of Trash. It will then inherit the behavior of the trash folder, and permanently delete messages when you press [del].<br /> <br /> <br /> === How can I compose email without internet connection (offline)? ===<br /> If you need to create email in offline (e.g. when you are travelling with your notebook and temporaly have no internet connection), you should do the following steps<br /> 1. Create MH mail box (File/Add mailbox) for local storage of messages.<br /> 2. At your account preferences, advanced-tab you should override &quot;put queued messages in&quot; and &quot;put queued draft in&quot; with folders of your MH mail box, e.g.<br /> #mh/local/queue<br /> #mh/local/draft<br /> <br /> When you compose your messages in offline mode, you should press &quot;send later&quot;, to put them into local queue. Entering online you press &quot;send&quot; button in main application screen to actually transmit them.</div> Ticho https://www.claws-mail.org/faq/index.php?title=Claws_Mail_on_Windows&diff=3078 Claws Mail on Windows 2018-03-31T13:14:21Z <p>Ticho: formatting</p> <hr /> <div>=== How to get &quot;debug&quot; output for Claws Mail on Windows? ===<br /> <br /> Claws Mail has an option to display a lot of low-level information during its run, to help developers figure out what's wrong in case of problems. When you report a bug, or ask for help on [http://claws-mail.org/MLs.php?section=community|our IRC channel], developers might request this from you.<br /> <br /> On Windows, this information is saved into file named &lt;code&gt;claws-win32.log&lt;/code&gt;, located at system default temporary directory (environment variable &lt;code&gt;TEMP&lt;/code&gt;, to be precise). This is usually &lt;code&gt;C:\Users\username\AppData\Local\Temp&lt;/code&gt;, but can vary in different Windows versions.<br /> <br /> To enable this debug output, you need to run claws-mail.exe with &lt;code&gt;--debug&lt;/code&gt; option. You can do this either from the &lt;code&gt;cmd.exe&lt;/code&gt; window, or by changing the ''Target'' in desktop or start menu shortcut for Claws mail to include this option.<br /> <br /> Assuming you installed Claws Mail in default location, '''for 32-bit Claws Mail''', the command or the ''Target'' should be (including the double-quotes): &lt;code&gt;&quot;C:\Program Files\Claws Mail (x86)\Claws Mail\claws-mail.exe&quot; --debug&lt;/code&gt;<br /> <br /> '''For 64-bit Claws Mail''', the command or the ''Target'' should be (including the double-quotes): &lt;code&gt;&quot;C:\Program Files\Claws Mail\Claws Mail\claws-mail.exe&quot; --debug&lt;/code&gt;<br /> <br /> Claws Mail will start normally, and you can try reproducing the issue you're having - just perform actions that lead to the issue. The &lt;code&gt;claws-win32.log&lt;/code&gt; will be continuously updated with debug output, depending on what the program is doing.<br /> <br /> Once done, you should copy the file somewhere else (it gets renamed to claws-win32.log.bak and a new log is started everytime you start Claws Mail, even without the &lt;code&gt;--debug&lt;/code&gt; option), and either send it to the developers, or look in it and try to look for clues for solving the issue. However, if you are not familiar with the source code of Claws Mail, most of the lines in this file will not make much sense to you.<br /> <br /> This file does contain some private info, such as usernames (but never passwords), server hostnames, your Claws Mail folder structure, sometimes parts of individual e-mail messages you are working with. If you are uncomfortable with that, you can edit the copied file, but please make it known that you have modified the file when you send it to the developers, to prevent misunderstandings.</div> Ticho https://www.claws-mail.org/faq/index.php?title=Claws_Mail_on_Windows&diff=3077 Claws Mail on Windows 2018-03-31T13:13:30Z <p>Ticho: created</p> <hr /> <div>=== How to get &quot;debug&quot; output for Claws Mail on Windows? ===<br /> <br /> Claws Mail has an option to display a lot of low-level information during its run, to help developers figure out what's wrong in case of problems. When you report a bug, or ask for help on [http://claws-mail.org/MLs.php?section=community|our IRC channel], developers might request this from you.<br /> <br /> On Windows, this information is saved into file named &lt;code&gt;claws-win32.log&lt;/code&gt;, located at system default temporary directory (environment variable &lt;code&gt;TEMP&lt;/code&gt;, to be precise). This is usually &lt;code&gt;C:\Users\username\AppData\Local\Temp&lt;/code&gt;, but can vary in different Windows versions.<br /> <br /> To enable this debug output, you need to run claws-mail.exe with &lt;code&gt;--debug&lt;/code&gt; option. You can do this either from the &lt;code&gt;cmd.exe&lt;/code&gt; window, or by changing the ''Target'' in desktop or start menu shortcut for Claws mail to include this option.<br /> <br /> Assuming you installed Claws Mail in default location, for 32-bit Claws Mail, the command or the ''Target'' should be (including the double-quotes): &lt;code&gt;&quot;C:\Program Files\Claws Mail (x86)\Claws Mail\claws-mail.exe&quot; --debug&lt;/code&gt;<br /> For 64-bit Claws Mail, the command or the ''Target'' should be (including the double-quotes): &lt;code&gt;&quot;C:\Program Files\Claws Mail\Claws Mail\claws-mail.exe&quot; --debug&lt;/code&gt;<br /> <br /> Claws Mail will start normally, and you can try reproducing the issue you're having - performing actions that lead to the issue. The &lt;code&gt;claws-win32.log&lt;/code&gt; will be continuously updated with debug output, depending on what the program is doing.<br /> <br /> Once done, you should copy the file somewhere else (it gets renamed to claws-win32.log.bak and a new log is started everytime you start Claws Mail, even without the &lt;code&gt;--debug&lt;/code&gt; option), and either send it to the developers, or look in it and try to look for clues for solving the issue. However, if you are not familiar with the source code of Claws Mail, most of the lines in this file will not make much sense to you.<br /> <br /> This file does contain some private info, such as usernames (but never passwords), server hostnames, your Claws Mail folder structure, sometimes parts of individual e-mail messages you are working with. If you are uncomfortable with that, you can edit the copied file, but please make it known that you have modified the file when you send it to the developers, to prevent misunderstandings.</div> Ticho https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3068 GTK3 Porting Checklist 2018-02-12T23:32:44Z <p>Ticho: </p> <hr /> <div>== Does not work ==<br /> <br /> * Color labels do not show actual color boxes in common prefs.<br /> <br /> *Using gtk_container_add() with GtkBox results in widgets not using full height available to them - gtk_box_pack_start() should be used instead. (Eventually, all GtkBoxes should be migrated to GtkGrid) Fixed so far:<br /> ** compose window textview<br /> ** prefsdialog page content area<br /> ** template preferences dialog<br /> <br /> * Folderview uses too bright colors for row backgrounds (alternating light gray and even lighter gray).<br /> <br /> * Folderview uses white text for folders without new messages in them, instead of black. Maybe related to bug #3880.<br /> <br /> * GtkCMCList has redrawing issues when mouse scrolling.<br /> <br /> * Quicksearch sometimes doesn't display the search type combobox and information button.<br /> <br /> * Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> * Fancy doesn't work, hangs indefinitely in webkit_web_view_new().<br /> <br /> * Messageview doesn't show Mimeview with body part icons on the right.<br /> <br /> * Vcalendar week/month views do not work, debug messages look like a new Claws Mail instance is trying to start when trying to display them.<br /> <br /> * Network log window minimal requested size is too large. Same for Mainwindow.<br /> <br /> * About window won't shrink back if you increase its width. Opened https://bugzilla.gnome.org/show_bug.cgi?id=793407 for that.<br /> <br /> == Works, but is ugly ==<br /> <br /> * GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another like in GTK2.<br /> <br /> == Deprecated API ==<br /> <br /> * GtkHBox, GtkVBox, GtkTable -&gt; GtkGrid<br /> <br /> * Alertpanel needs to be rewritten to not use GTK_STOCK_*, but GtkIconTheme and named icons.</div> Ticho https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3067 GTK3 Porting Checklist 2018-02-11T19:40:15Z <p>Ticho: </p> <hr /> <div>== Does not work ==<br /> <br /> * Color labels do not show actual color boxes in common prefs.<br /> <br /> *Using gtk_container_add() with GtkBox results in widgets not using full height available to them - gtk_box_pack_start() should be used instead. (Eventually, all GtkBoxes should be migrated to GtkGrid) Fixed so far:<br /> ** compose window textview<br /> ** prefsdialog page content area<br /> ** template preferences dialog<br /> <br /> * Folderview uses too bright colors for row backgrounds (alternating light gray and even lighter gray).<br /> <br /> * Folderview uses white text for folders without new messages in them, instead of black. Maybe related to bug #3880.<br /> <br /> * GtkCMCList has redrawing issues when mouse scrolling.<br /> <br /> * Quicksearch sometimes doesn't display the search type combobox and information button.<br /> <br /> * Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> * Fancy doesn't work, hangs indefinitely in webkit_web_view_new().<br /> <br /> * Messageview doesn't show Mimeview with body part icons on the right.<br /> <br /> * Vcalendar week/month views do not work, debug messages look like a new Claws Mail instance is trying to start when trying to display them.<br /> <br /> * Network log window minimal requested size is too large. Same for Mainwindow.<br /> <br /> == Works, but is ugly ==<br /> <br /> * GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another like in GTK2.<br /> <br /> == Deprecated API ==<br /> <br /> * GtkHBox, GtkVBox, GtkTable -&gt; GtkGrid<br /> <br /> * Alertpanel needs to be rewritten to not use GTK_STOCK_*, but GtkIconTheme and named icons.</div> Ticho https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3066 GTK3 Porting Checklist 2018-02-11T15:05:15Z <p>Ticho: created</p> <hr /> <div>== Does not work ==<br /> <br /> Color labels do not show actual color boxes in common prefs.<br /> <br /> Using gtk_container_add() with GtkBox results in widgets not using full height available to them - gtk_box_pack_start() should be used instead.<br /> Fixed so far:<br /> - compose window textview<br /> - prefsdialog page content area<br /> - template preferences dialog<br /> (Eventually, all GtkBoxes should be migrated to GtkGrid.)<br /> <br /> Folderview uses too bright colors for row backgrounds (alternating light gray and even lighter gray).<br /> <br /> Folderview uses white text for folders without new messages in them, instead of black. Maybe related to bug #3880.<br /> <br /> GtkCMCList has redrawing issues when mouse scrolling.<br /> <br /> Quicksearch sometimes doesn't display the search type combobox and information button.<br /> <br /> Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> Fancy doesn't work, hangs indefinitely in webkit_web_view_new().<br /> <br /> Messageview doesn't show Mimeview with body part icons on the right.<br /> <br /> Vcalendar week/month views do not work, debug messages look like a new Claws Mail instance is trying to start when trying to display them.<br /> <br /> Network log window minimal requested size is too large. Same for Mainwindow.<br /> <br /> == Works, but is ugly ==<br /> <br /> GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another.<br /> <br /> == Deprecated API ==</div> Ticho https://www.claws-mail.org/faq/index.php?title=S/MIME_howto&diff=1590 S/MIME howto 2006-12-20T08:54:59Z <p>Ticho: /* Requirements */ Adjusted the emerge output to include the command.</p> <hr /> <div>==Claws Mail &amp;&amp; S/MIME plugin howto==<br /> <br /> Recently there were many requests on the mailing list on how to configure the S/MIME plugin to work properly. It is not a trivial task as the GUI doesn't provide any configuration options and everything needs to be done in the console.<br /> <br /> I've had a &quot;half-working&quot; setup but always failed on some point when importing S/MIME certificates. I now managed to have a working config and hopefully this howto will give an insight on how to achieve it.<br /> <br /> This howto is based on Gentoo but should be working fine on every other distribution if adjusting it accordingly :)<br /> <br /> ===Requirements===<br /> # recent Claws Mail version<br /> # recent S/MIME plugin (I'm using 0.5.7cvs2 which fixes some decryption bugs)<br /> # S/MIME certificate (this howto is based on Thawte Freemail certs)<br /> # pinentry, gnupg, gpgme, ca-certificates (and openssl) in recent versions<br /> <br /> Those are the versions I'm using:<br /> <br /> # emerge -p pinentry gnupg gpgme ca-certificates<br /> [ebuild R ] app-crypt/pinentry-0.7.2-r3 USE=&quot;gtk ncurses qt3 -caps&quot; 390 kB<br /> [ebuild R ] app-crypt/gnupg-2.0.1-r1 USE=&quot;X bzip2 ldap nls -caps -doc -openct -pcsc-lite (-selinux) -smartcard&quot; 0 kB<br /> [ebuild R ] app-crypt/gpgme-1.1.2-r1 0 kB<br /> [ebuild R ] app-misc/ca-certificates-20050804 92 kB<br /> <br /> ===Optional===<br /> # running gpg-agent for caching the passphrase<br /> I'm using keychain to start gpg-agent. Choose what you like, here are somes howtos:<br /> &lt;br /&gt;<br /> http://www.claws-mail.org/faq/index.php/Plugins#How_do_I_configure_gpg-agent_and_the_PGP_plugin.3F http://gentoo-wiki.com/HOWTO_KMail_gpg-agent_kde#Setting_up_gpg-agent_with_keychain<br /> <br /> <br /> ===Importing S/MIME certificates into gpgsm===<br /> (from http://www.gnupg.org/aegypten/development.en.html#howto_import_external_certs)<br /> &lt;br /&gt;&lt;br /&gt;<br /> First one has to obtain the Thawte Freemail certificate and install it into Firefox/Thunderbird. Export the certificate from Firefox/Thunderbird e.g. to &quot;certbundle.p12&quot; file and remember the passphrase.<br /> <br /> Convert the file into PEM format:&lt;br /&gt;<br /> $ openssl pkcs12 -in certbundle.p12 -out certbundle.pem -nodes<br /> (use the export passphrase)<br /> <br /> Extract the key: &lt;br /&gt;<br /> $ openssl pkcs12 -in certbundle.pem -export -out certkey.p12 -nocerts -nodes<br /> <br /> Import the key into gpgsm:&lt;br /&gt;<br /> $ gpgsm --call-protect-tool --p12-import --store certkey.p12<br /> <br /> Now one has to add the issuers certificate (Thawte) into gpgsm, you can use the certs included in the Freemail cert, but I did the following:<br /> &lt;br /&gt;<br /> $ gpgsm --import /usr/share/ca-certificates/mozilla/Thawte*<br /> (Thawte_Personal_Basic_CA.crt, Thawte_Personal_Premium_CA.crt, Thawte_Server_CA.crt, Thawte_Personal_Freemail_CA.crt, Thawte_Premium_Server_CA.crt, Thawte_Time_Stamping_CA.crt)<br /> <br /> Check if your key has been added:&lt;br /&gt;<br /> $ gpgsm --list-secret-keys<br /> <br /> <br /> ===Configuring S/MIME===<br /> You need to create the file (if it doesn't exist) &quot;$HOME/.gnupg/trustlist.txt&quot; to add Thawte to the trusted key list. This makes it possible to verify/sign/.../ with your Thawte certificate. Add the following lines which contain the fingerprint (not serial number!) of the key and the letter S at the end:&lt;br /&gt;<br /> <br /> # 1.2.840.113549.1.9.1=#706572736F6E616C2D667265656D61696C407468617774652E636F6D,CN=Thawte <br /> # Personal Freemail CA,OU=Certification Services Division,O=Thawte<br /> # Consulting,L=Cape Town,ST=Western Cape,C=ZA<br /> 209900B63D955728140CD13622D8C687A4EB0085 S<br /> &lt;br /&gt;<br /> <br /> This is my &quot;$HOME/.gnupg/gpgsm.conf&quot;:&lt;br /&gt;<br /> disable-crl-checks<br /> disable-policy-checks<br /> auto-issuer-key-retrieve<br /> debug-level basic<br /> <br /> &lt;br /&gt;<br /> gpg-agent is only necessary for caching the passphrase: &quot;$HOME/.gnupg/gpg-agent.conf&quot;&lt;br /&gt;<br /> <br /> pinentry-program /usr/bin/pinentry-qt<br /> default-cache-ttl 86400 # be aware that the passphrases will be cached for 86400 seconds! set accordingly to your need<br /> max-cache-ttl 86400<br /> disable-scdaemon<br /> allow-mark-trusted<br /> <br /> <br /> ===Working with S/MIME plugin and problems/bugs===<br /> I think because few people managed to get it to work properly there weren't many bug reports yet :) There are some things I encountered which don't work fine, e.g. keep in mind:<br /> <br /> from the README:<br /> WARNING: This plugin doesn't handle sign+encrypt and encryption of multipart messages very well (yet).<br /> <br /> * That means if you encrypt and sign a message you get some header stuff in the body of the message and it will be a lot more garbage if you have attached files. Encrypting alone (without attachments) or signing alone (with or without attachments) works fine.<br /> <br /> * I always have to choose my key twice in the &quot;Select Keys&quot; dialog when encrypting? It seems the &quot;Trust key&quot; dialog doesn't show the name of the key, e.g. &quot;The key of '' is not fully trusted&quot;. &lt;br /&gt;CM first asks for the key of the recipient and then asks for the sender's key because CM can't extract it properly: &quot;No exact match for 'email@address'; please select the key.&quot; (guess that is because I have two certs..).&lt;br /&gt; If I send an email to a friend and include myself (To:), CM will ask me three times for the correct keys.<br /> <br /> * Although I added my own fingerprint to trustlist.txt CM always says that the recipient is not fully trusted when I send encrypted/signed emails. <br /> <br /> * As of now the &quot;Select Keys&quot; dialog when encrypting emails is a bit awkward to use if you have more than one key (e.g. one expired one you still want to keep to be able to decrypt older emails). It only shows the Key ID and no info about the date which makes it more difficult to choose the correct one.</div> Ticho