https://www.claws-mail.org/faq/api.php?action=feedcontributions&user=Colin&feedformat=atom Claws Mail FAQ - User contributions [en] 2024-03-28T23:31:19Z User contributions MediaWiki 1.35.7 https://www.claws-mail.org/faq/index.php?title=General_Information&diff=2063 General Information 2009-01-17T17:16:20Z <p>Colin: /* Why does Claws Mail load big folders slowly? */</p> <hr /> <div>=== What is Claws Mail? ===<br /> <br /> Claws Mail is an e-mail client (&amp; news reader) based on GTK+, running on the X Window System, and aiming for<br /> <br /> * Quick response<br /> * Graceful, and sophisticated interface<br /> * Easy configuration, intuitive operation<br /> * Abundant features<br /> * Extensibility<br /> * Robustness and stability<br /> <br /> === What are the differences between Claws Mail and Sylpheed? ===<br /> <br /> Claws Mail (formerly Sylpheed-Claws) started as the bleeding-edge version of Sylpheed, in order to act as a testbed for new features for Sylpheed. The idea was to regularly resync with Hiroyuki's main branch, and vice-versa. Claws Mail then evolved into the stable extended version of Sylpheed, and is now an entity in its own right, mainly due to different goals and the fact that syncing both codebases doesn't happen anymore.<br /> <br /> Claws Mail has many extra features compared to Sylpheed and is more powerful, yet is just as fast, lightweight and stable.<br /> <br /> === Where can I get Claws Mail? ===<br /> <br /> See the Downloads page http://www.claws-mail.org/downloads.php.<br /> <br /> === Who writes Claws Mail? ===<br /> <br /> Claws Mail is developed by the [http://www.claws-mail.org/theteam.php Claws Mail Team].<br /> <br /> === How does Claws Mail store mails? ===<br /> <br /> Mails are stored in the MH mailfile format as used by MH and EMH. Maildir and mbox format are supported via two plugins available on the [http://www.claws-mail.org/plugins.php Plugins page].<br /> <br /> === Does Claws Mail have mail filtering? ===<br /> <br /> Yes. You can find it in Configuration-&gt;Filtering... tab.<br /> <br /> === Can Claws Mail handle local unix mailboxes? ===<br /> <br /> Yes.<br /> <br /> === Can Claws Mail handle IPv6? ===<br /> <br /> Yes, IPv6 is fully supported in Claws Mail.<br /> <br /> === How many POP3, News or IMAP accounts can I set up in Claws Mail? ===<br /> <br /> The number is unlimited. The limit is reached when your computer stops responding.<br /> <br /> === Can I set up an Account for sending Mail only? ===<br /> <br /> Yes, set up a new account using '''Configuration -&gt; Create new Account''' and set the Protocol to ''None (SMTP only)''. <br /> Or create a local Account for a MH-directory and disable automatic checking for new mail on that account.<br /> <br /> === Does Claws Mail support encryption like GPG? ===<br /> <br /> Yes. GPG is implemented and works fine. For activating it in Claws Mail, see the [[Installation_and_Configuration#How_do_I_enable_GPG_support_in_Claws_Mail.3F|Installation and Configuration]] section.<br /> <br /> === How does Claws Mail check for MIME types? ===<br /> <br /> Claws Mail uses the Mutt type of mime checking.<br /> <br /> === Does Claws Mail allow me to write HTML styled messages? ===<br /> <br /> No. A discussion has gone around over this topic, and the outcome was that HTML mail is not wanted. If you really need to send HTML, you can of course attach a webpage to an e-mail.<br /> <br /> === Does Claws Mail have name completion in the address fields? ===<br /> <br /> Yes. When you search for a name that starts with &quot;don&quot;, type &quot;don&quot; (without the quotes) and press the TAB key. This will show you the correct name (when only one &quot;don&quot; exists in your addressbook. Otherwise a dropdown list appears, which allows you to select the name you want. E.g. Donald Duck, Don Johnson. But also e-mail addresses starting with &quot;don&quot; will appear in the list (like &quot;don.giovanni@maffia.org&quot;).<br /> <br /> === Why is Claws Mail so fast? ===<br /> <br /> That's what it is designed for!<br /> <br /> === How can I send in patches, report bugs, talk about Claws Mail with others? ===<br /> <br /> To talk to others, you should join the Claws Mail users' mailing list at http://www.claws-mail.org/MLs.php.<br /> <br /> === Can I import an mbox into Claws Mail's MH mailfolders? ===<br /> <br /> Yes, just create/select the folder you want your mails in, and select &quot;Import mbox file&quot; in the File menu.<br /> <br /> === Can I use procmail to sort my mails with the MH mail handling? ===<br /> <br /> Yes. Just make sure that you add /. to the end of a rule so procmail knows that you are filtering into an MH mail folder. Example :<br /> &lt;pre&gt;<br /> 0:<br /> <br /> * ^Subject:.*claws<br /> <br /> clawsmail/.<br /> &lt;/pre&gt;<br /> <br /> Check man procmail for details.<br /> <br /> === When I upgrade Claws Mail, are there things I should be aware of? ===<br /> <br /> Yes, some more critical than others.<br /> <br /> You should always read the RELEASE_NOTES document that is included in the release tarballs.<br /> The release notes can also be viewed on the Claws Mail [http://www.claws-mail.org/news.php News] page.<br /> <br /> === How can I quickly update the views in Claws Mail? ===<br /> <br /> Just press Alt-U or select &quot;update&quot; from the summary menu.<br /> <br /> === Why does Claws Mail allow me to open more than one instance at the same time for the same user on a network? ===<br /> <br /> Claws Mail opens a Unix-domain socket using a name constucted from your TMPDIR path plus your UID.<br /> This socket is used to arbitrate multiple instances on a given machine.<br /> In Linux, at least, named Unix-domain sockets are known only locally, to the creating machine.<br /> Pointing your TMPDIR environment variable to /home/yours/tmp doesn't have the desired effect,<br /> as the socket definition would need to be propagated across the LAN and isn't.<br /> <br /> === Does Claws Mail have an anti-spam feature? ===<br /> <br /> Yes. It has a [[Plugins | Bogofilter]] plugin and a [[Plugins | SpamAssassin]] plugin. You can find details of them on the [[Plugins]] FAQ Page.<br /> <br /> You can also use other spam filters via [[Actions]], futher details can be found on the [[Using_Claws_Mail_with_other_programs|Using Claws Mail with other programs]] page.<br /> <br /> === Does Claws Mail support Return Receipts? ===<br /> <br /> Yes.<br /> <br /> To request a Return Receipt use '/Options/Request Return Receipt' in the Compose window.<br /> <br /> When you receive a message that requests a Return Receipt a notification area is shown just above the message view. You can either use the 'Send receipt' button, or ignore the request - no receipts are sent automatically.<br /> <br /> You can choose to never send Return Receipts by using the option on the Mail Handling/Sending page of the Preferences. When you use this option, all Return Receipt requests are ignored and you will not be prompted to send one.<br /> <br /> === Why does Claws Mail load big folders slowly? ===<br /> <br /> Certain options, although handy, can slow down Claws Mail. Consider disabling the following options to achieve more speed:<br /> &lt;br&gt;<br /> /Display/Summaries 'Display sender using address book'<br /> &lt;br&gt;<br /> /Display/Summaries 'Thread using subject in addition to standard headers'<br /> &lt;br&gt;<br /> /Plugins/GPG 'Automatically check signatures'<br /> &lt;br&gt;<br /> In the Message List, Sort by Date or other non-string headers instead of Subject, From or To.<br /> &lt;br&gt;<br /> Avoid using cpu intensive folder Processing rules conditions such as &quot;Whole message&quot;, &quot;Body part&quot;, etc, and Pre/Post processing.<br /> <br /> === How do I make a new Icon Theme for Claws Mail? ===<br /> <br /> Obviously you need to have some artistic abilities (well, not much unless you want to make a really cool theme), but, apart from that, there's some technical points you should consider when making a new theme and you want to share it with the rest of the world:<br /> <br /> * Choose a license for it. Remember that themes without license are not free.<br /> * If you're using some other theme or graphic element you found on the web be careful and check its license also. Some authors use strange licenses which does not allow derivations or redistributions, or impose the original license over derived works.<br /> * If you're making original artwork and do not know (or care) which license to choose, [http://www.gnu.org/copyleft/gpl.html GPL] is a good and recommended option. It's the same license that Claws Mail uses.<br /> * Try to provide a full set of icons. The easiest way to do that is to copy all Claws Mail icons and start editing them.<br /> * Keep the sizes uniform. Claws Mail default icons are certain size, and some variations are allowed, but size disparity can not be a good idea if two icons are going to be displayed side to side.<br /> * Provide a .claws_themeinfo file<br /> * Have a look at the existing themes, they may inspire you! :)</div> Colin https://www.claws-mail.org/faq/index.php?title=General_Information&diff=2062 General Information 2009-01-15T07:34:54Z <p>Colin: /* Why does Claws Mail load big folders slowly? */</p> <hr /> <div>=== What is Claws Mail? ===<br /> <br /> Claws Mail is an e-mail client (&amp; news reader) based on GTK+, running on the X Window System, and aiming for<br /> <br /> * Quick response<br /> * Graceful, and sophisticated interface<br /> * Easy configuration, intuitive operation<br /> * Abundant features<br /> * Extensibility<br /> * Robustness and stability<br /> <br /> === What are the differences between Claws Mail and Sylpheed? ===<br /> <br /> Claws Mail (formerly Sylpheed-Claws) started as the bleeding-edge version of Sylpheed, in order to act as a testbed for new features for Sylpheed. The idea was to regularly resync with Hiroyuki's main branch, and vice-versa. Claws Mail then evolved into the stable extended version of Sylpheed, and is now an entity in its own right, mainly due to different goals and the fact that syncing both codebases doesn't happen anymore.<br /> <br /> Claws Mail has many extra features compared to Sylpheed and is more powerful, yet is just as fast, lightweight and stable.<br /> <br /> === Where can I get Claws Mail? ===<br /> <br /> See the Downloads page http://www.claws-mail.org/downloads.php.<br /> <br /> === Who writes Claws Mail? ===<br /> <br /> Claws Mail is developed by the [http://www.claws-mail.org/theteam.php Claws Mail Team].<br /> <br /> === How does Claws Mail store mails? ===<br /> <br /> Mails are stored in the MH mailfile format as used by MH and EMH. Maildir and mbox format are supported via two plugins available on the [http://www.claws-mail.org/plugins.php Plugins page].<br /> <br /> === Does Claws Mail have mail filtering? ===<br /> <br /> Yes. You can find it in Configuration-&gt;Filtering... tab.<br /> <br /> === Can Claws Mail handle local unix mailboxes? ===<br /> <br /> Yes.<br /> <br /> === Can Claws Mail handle IPv6? ===<br /> <br /> Yes, IPv6 is fully supported in Claws Mail.<br /> <br /> === How many POP3, News or IMAP accounts can I set up in Claws Mail? ===<br /> <br /> The number is unlimited. The limit is reached when your computer stops responding.<br /> <br /> === Can I set up an Account for sending Mail only? ===<br /> <br /> Yes, set up a new account using '''Configuration -&gt; Create new Account''' and set the Protocol to ''None (SMTP only)''. <br /> Or create a local Account for a MH-directory and disable automatic checking for new mail on that account.<br /> <br /> === Does Claws Mail support encryption like GPG? ===<br /> <br /> Yes. GPG is implemented and works fine. For activating it in Claws Mail, see the [[Installation_and_Configuration#How_do_I_enable_GPG_support_in_Claws_Mail.3F|Installation and Configuration]] section.<br /> <br /> === How does Claws Mail check for MIME types? ===<br /> <br /> Claws Mail uses the Mutt type of mime checking.<br /> <br /> === Does Claws Mail allow me to write HTML styled messages? ===<br /> <br /> No. A discussion has gone around over this topic, and the outcome was that HTML mail is not wanted. If you really need to send HTML, you can of course attach a webpage to an e-mail.<br /> <br /> === Does Claws Mail have name completion in the address fields? ===<br /> <br /> Yes. When you search for a name that starts with &quot;don&quot;, type &quot;don&quot; (without the quotes) and press the TAB key. This will show you the correct name (when only one &quot;don&quot; exists in your addressbook. Otherwise a dropdown list appears, which allows you to select the name you want. E.g. Donald Duck, Don Johnson. But also e-mail addresses starting with &quot;don&quot; will appear in the list (like &quot;don.giovanni@maffia.org&quot;).<br /> <br /> === Why is Claws Mail so fast? ===<br /> <br /> That's what it is designed for!<br /> <br /> === How can I send in patches, report bugs, talk about Claws Mail with others? ===<br /> <br /> To talk to others, you should join the Claws Mail users' mailing list at http://www.claws-mail.org/MLs.php.<br /> <br /> === Can I import an mbox into Claws Mail's MH mailfolders? ===<br /> <br /> Yes, just create/select the folder you want your mails in, and select &quot;Import mbox file&quot; in the File menu.<br /> <br /> === Can I use procmail to sort my mails with the MH mail handling? ===<br /> <br /> Yes. Just make sure that you add /. to the end of a rule so procmail knows that you are filtering into an MH mail folder. Example :<br /> &lt;pre&gt;<br /> 0:<br /> <br /> * ^Subject:.*claws<br /> <br /> clawsmail/.<br /> &lt;/pre&gt;<br /> <br /> Check man procmail for details.<br /> <br /> === When I upgrade Claws Mail, are there things I should be aware of? ===<br /> <br /> Yes, some more critical than others.<br /> <br /> You should always read the RELEASE_NOTES document that is included in the release tarballs.<br /> The release notes can also be viewed on the Claws Mail [http://www.claws-mail.org/news.php News] page.<br /> <br /> === How can I quickly update the views in Claws Mail? ===<br /> <br /> Just press Alt-U or select &quot;update&quot; from the summary menu.<br /> <br /> === Why does Claws Mail allow me to open more than one instance at the same time for the same user on a network? ===<br /> <br /> Claws Mail opens a Unix-domain socket using a name constucted from your TMPDIR path plus your UID.<br /> This socket is used to arbitrate multiple instances on a given machine.<br /> In Linux, at least, named Unix-domain sockets are known only locally, to the creating machine.<br /> Pointing your TMPDIR environment variable to /home/yours/tmp doesn't have the desired effect,<br /> as the socket definition would need to be propagated across the LAN and isn't.<br /> <br /> === Does Claws Mail have an anti-spam feature? ===<br /> <br /> Yes. It has a [[Plugins | Bogofilter]] plugin and a [[Plugins | SpamAssassin]] plugin. You can find details of them on the [[Plugins]] FAQ Page.<br /> <br /> You can also use other spam filters via [[Actions]], futher details can be found on the [[Using_Claws_Mail_with_other_programs|Using Claws Mail with other programs]] page.<br /> <br /> === Does Claws Mail support Return Receipts? ===<br /> <br /> Yes.<br /> <br /> To request a Return Receipt use '/Options/Request Return Receipt' in the Compose window.<br /> <br /> When you receive a message that requests a Return Receipt a notification area is shown just above the message view. You can either use the 'Send receipt' button, or ignore the request - no receipts are sent automatically.<br /> <br /> You can choose to never send Return Receipts by using the option on the Mail Handling/Sending page of the Preferences. When you use this option, all Return Receipt requests are ignored and you will not be prompted to send one.<br /> <br /> === Why does Claws Mail load big folders slowly? ===<br /> <br /> Certain options, although handy, can slow down Claws Mail. Consider disabling the following options to achieve more speed:<br /> &lt;br&gt;<br /> /Display/Summaries 'Display sender using address book'<br /> &lt;br&gt;<br /> /Display/Summaries 'Thread using subject in addition to standard headers'<br /> &lt;br&gt;<br /> /Plugins/GPG 'Automatically check signatures'<br /> &lt;br&gt;<br /> In the Message List, Sort by Date or other non-string headers instead of Subject, From or To.<br /> &lt;br&gt;<br /> Avoid using cpu intensive Folder Processing rule Conditions such as &quot;Whole message&quot;, &quot;Body part&quot;, etc.<br /> <br /> === How do I make a new Icon Theme for Claws Mail? ===<br /> <br /> Obviously you need to have some artistic abilities (well, not much unless you want to make a really cool theme), but, apart from that, there's some technical points you should consider when making a new theme and you want to share it with the rest of the world:<br /> <br /> * Choose a license for it. Remember that themes without license are not free.<br /> * If you're using some other theme or graphic element you found on the web be careful and check its license also. Some authors use strange licenses which does not allow derivations or redistributions, or impose the original license over derived works.<br /> * If you're making original artwork and do not know (or care) which license to choose, [http://www.gnu.org/copyleft/gpl.html GPL] is a good and recommended option. It's the same license that Claws Mail uses.<br /> * Try to provide a full set of icons. The easiest way to do that is to copy all Claws Mail icons and start editing them.<br /> * Keep the sizes uniform. Claws Mail default icons are certain size, and some variations are allowed, but size disparity can not be a good idea if two icons are going to be displayed side to side.<br /> * Provide a .claws_themeinfo file<br /> * Have a look at the existing themes, they may inspire you! :)</div> Colin https://www.claws-mail.org/faq/index.php?title=General_Information&diff=2061 General Information 2009-01-15T07:34:40Z <p>Colin: /* Why does Claws Mail load big folders slowly? */</p> <hr /> <div>=== What is Claws Mail? ===<br /> <br /> Claws Mail is an e-mail client (&amp; news reader) based on GTK+, running on the X Window System, and aiming for<br /> <br /> * Quick response<br /> * Graceful, and sophisticated interface<br /> * Easy configuration, intuitive operation<br /> * Abundant features<br /> * Extensibility<br /> * Robustness and stability<br /> <br /> === What are the differences between Claws Mail and Sylpheed? ===<br /> <br /> Claws Mail (formerly Sylpheed-Claws) started as the bleeding-edge version of Sylpheed, in order to act as a testbed for new features for Sylpheed. The idea was to regularly resync with Hiroyuki's main branch, and vice-versa. Claws Mail then evolved into the stable extended version of Sylpheed, and is now an entity in its own right, mainly due to different goals and the fact that syncing both codebases doesn't happen anymore.<br /> <br /> Claws Mail has many extra features compared to Sylpheed and is more powerful, yet is just as fast, lightweight and stable.<br /> <br /> === Where can I get Claws Mail? ===<br /> <br /> See the Downloads page http://www.claws-mail.org/downloads.php.<br /> <br /> === Who writes Claws Mail? ===<br /> <br /> Claws Mail is developed by the [http://www.claws-mail.org/theteam.php Claws Mail Team].<br /> <br /> === How does Claws Mail store mails? ===<br /> <br /> Mails are stored in the MH mailfile format as used by MH and EMH. Maildir and mbox format are supported via two plugins available on the [http://www.claws-mail.org/plugins.php Plugins page].<br /> <br /> === Does Claws Mail have mail filtering? ===<br /> <br /> Yes. You can find it in Configuration-&gt;Filtering... tab.<br /> <br /> === Can Claws Mail handle local unix mailboxes? ===<br /> <br /> Yes.<br /> <br /> === Can Claws Mail handle IPv6? ===<br /> <br /> Yes, IPv6 is fully supported in Claws Mail.<br /> <br /> === How many POP3, News or IMAP accounts can I set up in Claws Mail? ===<br /> <br /> The number is unlimited. The limit is reached when your computer stops responding.<br /> <br /> === Can I set up an Account for sending Mail only? ===<br /> <br /> Yes, set up a new account using '''Configuration -&gt; Create new Account''' and set the Protocol to ''None (SMTP only)''. <br /> Or create a local Account for a MH-directory and disable automatic checking for new mail on that account.<br /> <br /> === Does Claws Mail support encryption like GPG? ===<br /> <br /> Yes. GPG is implemented and works fine. For activating it in Claws Mail, see the [[Installation_and_Configuration#How_do_I_enable_GPG_support_in_Claws_Mail.3F|Installation and Configuration]] section.<br /> <br /> === How does Claws Mail check for MIME types? ===<br /> <br /> Claws Mail uses the Mutt type of mime checking.<br /> <br /> === Does Claws Mail allow me to write HTML styled messages? ===<br /> <br /> No. A discussion has gone around over this topic, and the outcome was that HTML mail is not wanted. If you really need to send HTML, you can of course attach a webpage to an e-mail.<br /> <br /> === Does Claws Mail have name completion in the address fields? ===<br /> <br /> Yes. When you search for a name that starts with &quot;don&quot;, type &quot;don&quot; (without the quotes) and press the TAB key. This will show you the correct name (when only one &quot;don&quot; exists in your addressbook. Otherwise a dropdown list appears, which allows you to select the name you want. E.g. Donald Duck, Don Johnson. But also e-mail addresses starting with &quot;don&quot; will appear in the list (like &quot;don.giovanni@maffia.org&quot;).<br /> <br /> === Why is Claws Mail so fast? ===<br /> <br /> That's what it is designed for!<br /> <br /> === How can I send in patches, report bugs, talk about Claws Mail with others? ===<br /> <br /> To talk to others, you should join the Claws Mail users' mailing list at http://www.claws-mail.org/MLs.php.<br /> <br /> === Can I import an mbox into Claws Mail's MH mailfolders? ===<br /> <br /> Yes, just create/select the folder you want your mails in, and select &quot;Import mbox file&quot; in the File menu.<br /> <br /> === Can I use procmail to sort my mails with the MH mail handling? ===<br /> <br /> Yes. Just make sure that you add /. to the end of a rule so procmail knows that you are filtering into an MH mail folder. Example :<br /> &lt;pre&gt;<br /> 0:<br /> <br /> * ^Subject:.*claws<br /> <br /> clawsmail/.<br /> &lt;/pre&gt;<br /> <br /> Check man procmail for details.<br /> <br /> === When I upgrade Claws Mail, are there things I should be aware of? ===<br /> <br /> Yes, some more critical than others.<br /> <br /> You should always read the RELEASE_NOTES document that is included in the release tarballs.<br /> The release notes can also be viewed on the Claws Mail [http://www.claws-mail.org/news.php News] page.<br /> <br /> === How can I quickly update the views in Claws Mail? ===<br /> <br /> Just press Alt-U or select &quot;update&quot; from the summary menu.<br /> <br /> === Why does Claws Mail allow me to open more than one instance at the same time for the same user on a network? ===<br /> <br /> Claws Mail opens a Unix-domain socket using a name constucted from your TMPDIR path plus your UID.<br /> This socket is used to arbitrate multiple instances on a given machine.<br /> In Linux, at least, named Unix-domain sockets are known only locally, to the creating machine.<br /> Pointing your TMPDIR environment variable to /home/yours/tmp doesn't have the desired effect,<br /> as the socket definition would need to be propagated across the LAN and isn't.<br /> <br /> === Does Claws Mail have an anti-spam feature? ===<br /> <br /> Yes. It has a [[Plugins | Bogofilter]] plugin and a [[Plugins | SpamAssassin]] plugin. You can find details of them on the [[Plugins]] FAQ Page.<br /> <br /> You can also use other spam filters via [[Actions]], futher details can be found on the [[Using_Claws_Mail_with_other_programs|Using Claws Mail with other programs]] page.<br /> <br /> === Does Claws Mail support Return Receipts? ===<br /> <br /> Yes.<br /> <br /> To request a Return Receipt use '/Options/Request Return Receipt' in the Compose window.<br /> <br /> When you receive a message that requests a Return Receipt a notification area is shown just above the message view. You can either use the 'Send receipt' button, or ignore the request - no receipts are sent automatically.<br /> <br /> You can choose to never send Return Receipts by using the option on the Mail Handling/Sending page of the Preferences. When you use this option, all Return Receipt requests are ignored and you will not be prompted to send one.<br /> <br /> === Why does Claws Mail load big folders slowly? ===<br /> <br /> Certain options, although handy, can slow down Claws Mail. Consider disabling the following options to achieve more speed:<br /> &lt;br&gt;<br /> /Display/Summaries 'Display sender using address book'<br /> &lt;br&gt;<br /> /Display/Summaries 'Thread using subject in addition to standard headers'<br /> &lt;br&gt;<br /> /Plugins/GPG 'Automatically check signatures'<br /> &lt;b&gt;<br /> In the Message List, Sort by Date or other non-string headers instead of Subject, From or To.<br /> &lt;br&gt;<br /> Avoid using cpu intensive Folder Processing rule Conditions such as &quot;Whole message&quot;, &quot;Body part&quot;, etc.<br /> <br /> === How do I make a new Icon Theme for Claws Mail? ===<br /> <br /> Obviously you need to have some artistic abilities (well, not much unless you want to make a really cool theme), but, apart from that, there's some technical points you should consider when making a new theme and you want to share it with the rest of the world:<br /> <br /> * Choose a license for it. Remember that themes without license are not free.<br /> * If you're using some other theme or graphic element you found on the web be careful and check its license also. Some authors use strange licenses which does not allow derivations or redistributions, or impose the original license over derived works.<br /> * If you're making original artwork and do not know (or care) which license to choose, [http://www.gnu.org/copyleft/gpl.html GPL] is a good and recommended option. It's the same license that Claws Mail uses.<br /> * Try to provide a full set of icons. The easiest way to do that is to copy all Claws Mail icons and start editing them.<br /> * Keep the sizes uniform. Claws Mail default icons are certain size, and some variations are allowed, but size disparity can not be a good idea if two icons are going to be displayed side to side.<br /> * Provide a .claws_themeinfo file<br /> * Have a look at the existing themes, they may inspire you! :)</div> Colin https://www.claws-mail.org/faq/index.php?title=File:Key_gpg_signed.png&diff=2058 File:Key gpg signed.png 2009-01-06T08:55:17Z <p>Colin: </p> <hr /> <div></div> Colin https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=2049 Main Page 2008-10-02T09:37:26Z <p>Colin: Remove empty section</p> <hr /> <div>== Claws Mail FAQ ==<br /> <br /> === General ===<br /> <br /> * [[General Information]]<br /> * [[Installation and Configuration]]<br /> ** [[S/MIME_howto|S/MIME Plugin Howto]]<br /> ** [[LDAP and Claws Mail]]<br /> ** [[Connecting to MS Exchange]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Filtering and Processing of Messages]]<br /> * [[Actions]]<br /> * [[Templates]]<br /> * [[Plugins]]<br /> * [[Using Claws Mail with other programs]]<br /> <br /> ----<br /> : If you edit the FAQ pages please keep the style. If you change anchor names you might break links from other pages, so don't do that. Invent better names for new anchors. That makes it easier to reference them from other pages. You don't have to add new questions to the end of the list, if you think it's better placed after another question.</div> Colin https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration&diff=1971 Installation and Configuration 2008-02-19T10:37:18Z <p>Colin: remove clamav, the return</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.6.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<br /> ; OpenSSL : for SSL support<br /> ; libEtPan! 0.48 or later : for IMAP4 support<br /> ; OpenLDAP 2.0.7 or later : for LDAP support<br /> ; Aspell 0.50 or later (and dictionaries) : for spell-checker support<br /> ; libgnomeprint-2.2 and libgnomeprintui-2.2 : for extended printer support<br /> ; J-Pilot : for J-Pilot support<br /> ; SpamAssassin : for SpamAssassin plugin support<br /> ; Clam AntiVirus : for Clam AntiVirus plugin support<br /> ; Dillo : for Dillo HTML viewer plugin support<br /> ; Bogofilter : for Bogofilter plugin support<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, see his dedicated page (http://damien.krotkine.com/claws/) and his former post to his blog (http://planet.gentoo.org/developers/dams/2007/05/05/compile_claws_mail_on_mac_os_x). The procedure below is based on his work.<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 /> === 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 =./autogen.sh=, remove the generated =/config.cache= file (unless you want to install in prefix /usr/local). Run =./configure= with the appropriate options and then make. (Text as found on the Claws Mail patch page.)<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 /> In the Configuration menu, Preferences for current account, Send tab, check Add user-defined header and press Edit button. A dialog 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 in the Configuration menu, Preferences for current account, Send tab, check Add user-defined header and press Edit button. A dialog appears, add a header named &quot;Face&quot; and click the &quot;From file&quot; button then 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 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 /> ; Opera:<br /> &lt;pre&gt;claws-mail --compose &lt;nowiki&gt;mailto:%t?subject=%s&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 /> 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 Trayicon (which is shipped with Claws Mail) or Acpi-notifier or Notification plugins, 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 Aspell &gt;= 0.50 and use the &lt;code&gt;./configure&lt;/code&gt; option &lt;code&gt;--enable-aspell&lt;/code&gt;<br /> <br /> === I checked out the sources using cvs and cant find any configure script. What can I do? ===<br /> <br /> The cvs 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 cvs really look sexy...<br /> <br /> You need to generate the configure script by running &lt;code&gt;./autogen.sh&lt;/code&gt;. Building from CVS requires a lot of extra dependencies that the release tarballs don't have, as an easier alternative, consider using the daily CVS snapshot instead, available from http://www.claws-mail.org/cvs.php.<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 /> === 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 mailclient). ===<br /> <br /> In the source distribution, you can find some scripts in the &lt;code&gt;tools&lt;/code&gt; subdirectory, maybe your application is supported. You can also try to export your old mailbox to &lt;code&gt;MH&lt;/code&gt; or &lt;code&gt;mbox&lt;/code&gt; format. If the mailbox is in &lt;code&gt;mbox&lt;/code&gt; format, it can be imported: File -&gt; Import mbox file...<br /> <br /> For the addressbook, direct import is supported for Mutt and Pine, but also LDIF, which is a standard format which most email clients can export to.<br /> <br /> Tip: Take a look at the &quot;harvest addresses&quot; function from the &lt;code&gt;Tools&lt;/code&gt; menu, it could be a useful alternative or addition, when importing your old contacts.<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 /> === Mail is not sent because the queue folder cannot be found? ===<br /> <br /> (From the old bug tracker): Claws Mail requires a queue folder. This<br /> was changed to prevent message losses, if Claws Mail is killed while sending. Create a local folder (/File/Add Mailbox.../MH) for the queue and sending should work. I would not suggest to use the imap<br /> server for this purpose because Claws Mail's queue messages have a special header that can not be handled correctly by the imap server, when the data for the summaryview is queried.<br /> <br /> If you really want to create a queueing folder in an IMAP server, you just have to create an ordinary folder in it, and then edit folderlist.xml file in Claws Mail's configuration directory. In this file, you will find a &quot;folderitem&quot; tag, with its &quot;name&quot; attribute set to the IMAP folder name you just created for queueing. You should edit this tag, and set its &quot;type&quot; attribute set to &quot;queue&quot;. Note that this &quot;folderitem&quot; you're looking that will be a child of an &quot;folder&quot; tag that has its &quot;type&quot; attribute set to &quot;imap&quot;.<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 GNU/Aspell 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 /> http://gmail.google.com/support/bin/topic.py?topic=1555&lt;br&gt;<br /> http://gmail.google.com/support/bin/answer.py?answer=13273&lt;br&gt;<br /> http://mail.google.com/support/bin/topic.py?topic=12760&lt;br&gt;<br /> http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=78799<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].</div> Colin https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration&diff=1970 Installation and Configuration 2008-02-19T10:36:18Z <p>Colin: delete clamav</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.6.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<br /> ; OpenSSL : for SSL support<br /> ; libEtPan! 0.48 or later : for IMAP4 support<br /> ; OpenLDAP 2.0.7 or later : for LDAP support<br /> ; Aspell 0.50 or later (and dictionaries) : for spell-checker support<br /> ; libgnomeprint-2.2 and libgnomeprintui-2.2 : for extended printer support<br /> ; J-Pilot : for J-Pilot support<br /> ; SpamAssassin : for SpamAssassin plugin support<br /> ; Clam AntiVirus : for Clam AntiVirus plugin support<br /> ; Dillo : for Dillo HTML viewer plugin support<br /> ; Bogofilter : for Bogofilter plugin support<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, see his dedicated page (http://damien.krotkine.com/claws/) and his former post to his blog (http://planet.gentoo.org/developers/dams/2007/05/05/compile_claws_mail_on_mac_os_x). The procedure below is based on his work.<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, clamav, 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 /> === 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 =./autogen.sh=, remove the generated =/config.cache= file (unless you want to install in prefix /usr/local). Run =./configure= with the appropriate options and then make. (Text as found on the Claws Mail patch page.)<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 /> In the Configuration menu, Preferences for current account, Send tab, check Add user-defined header and press Edit button. A dialog 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 in the Configuration menu, Preferences for current account, Send tab, check Add user-defined header and press Edit button. A dialog appears, add a header named &quot;Face&quot; and click the &quot;From file&quot; button then 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 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 /> ; Opera:<br /> &lt;pre&gt;claws-mail --compose &lt;nowiki&gt;mailto:%t?subject=%s&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 /> 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 Trayicon (which is shipped with Claws Mail) or Acpi-notifier or Notification plugins, 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 Aspell &gt;= 0.50 and use the &lt;code&gt;./configure&lt;/code&gt; option &lt;code&gt;--enable-aspell&lt;/code&gt;<br /> <br /> === I checked out the sources using cvs and cant find any configure script. What can I do? ===<br /> <br /> The cvs 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 cvs really look sexy...<br /> <br /> You need to generate the configure script by running &lt;code&gt;./autogen.sh&lt;/code&gt;. Building from CVS requires a lot of extra dependencies that the release tarballs don't have, as an easier alternative, consider using the daily CVS snapshot instead, available from http://www.claws-mail.org/cvs.php.<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 /> === 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 mailclient). ===<br /> <br /> In the source distribution, you can find some scripts in the &lt;code&gt;tools&lt;/code&gt; subdirectory, maybe your application is supported. You can also try to export your old mailbox to &lt;code&gt;MH&lt;/code&gt; or &lt;code&gt;mbox&lt;/code&gt; format. If the mailbox is in &lt;code&gt;mbox&lt;/code&gt; format, it can be imported: File -&gt; Import mbox file...<br /> <br /> For the addressbook, direct import is supported for Mutt and Pine, but also LDIF, which is a standard format which most email clients can export to.<br /> <br /> Tip: Take a look at the &quot;harvest addresses&quot; function from the &lt;code&gt;Tools&lt;/code&gt; menu, it could be a useful alternative or addition, when importing your old contacts.<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 /> === Mail is not sent because the queue folder cannot be found? ===<br /> <br /> (From the old bug tracker): Claws Mail requires a queue folder. This<br /> was changed to prevent message losses, if Claws Mail is killed while sending. Create a local folder (/File/Add Mailbox.../MH) for the queue and sending should work. I would not suggest to use the imap<br /> server for this purpose because Claws Mail's queue messages have a special header that can not be handled correctly by the imap server, when the data for the summaryview is queried.<br /> <br /> If you really want to create a queueing folder in an IMAP server, you just have to create an ordinary folder in it, and then edit folderlist.xml file in Claws Mail's configuration directory. In this file, you will find a &quot;folderitem&quot; tag, with its &quot;name&quot; attribute set to the IMAP folder name you just created for queueing. You should edit this tag, and set its &quot;type&quot; attribute set to &quot;queue&quot;. Note that this &quot;folderitem&quot; you're looking that will be a child of an &quot;folder&quot; tag that has its &quot;type&quot; attribute set to &quot;imap&quot;.<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 GNU/Aspell 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 /> http://gmail.google.com/support/bin/topic.py?topic=1555&lt;br&gt;<br /> http://gmail.google.com/support/bin/answer.py?answer=13273&lt;br&gt;<br /> http://mail.google.com/support/bin/topic.py?topic=12760&lt;br&gt;<br /> http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=78799<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].</div> Colin https://www.claws-mail.org/faq/index.php?title=Debugging_Claws&diff=1872 Debugging Claws 2007-06-21T06:52:35Z <p>Colin: </p> <hr /> <div>If you find a bug in Claws Mail, reporting it is the best way to have it fixed. Here are some pointers on how to make the most useful bug report possible.<br /> <br /> == Functionality bug (non crasher) ==<br /> If you face a functional bug, where Claws Mail doesn't crash, but doesn't do the right thing in your opinion, open a bug on the [http://thewildbeast.co.uk/claws-mail/bugzilla/ bug tracker] describing the action you're trying to do.<br /> <br /> == Crasher bug ==<br /> If Claws Mail crashes when you're trying to perform some action, we will need more information than just the steps to reproduce: this sort of bug often depends on many variables, previous actions, your setup, etc. We will need a backtrace, which shows us precisely where in the code Claws crashes and where it came from.<br /> <br /> To generate a good backtrace, Claws Mail needs to have &quot;debug symbols&quot; available. Without debug symbols, the backtrace is useless because it will not show function information, line numbers and other interesting things.<br /> <br /> The way to have debug symbols available depends on the way you installed Claws Mail:<br /> <br /> * Self-compiled Claws Mail: if you compile Claws Mail yourself, rebuild it using the following:<br /> $ '''make clean'''<br /> $ '''export CFLAGS=-g'''<br /> $ '''./configure'''<br /> $ '''make'''<br /> $ '''sudo make install'''<br /> <br /> * Claws Mail packages from your distribution: if you installed Claws Mail from pre-compiled packages, you will often have to install a special &quot;debug&quot; package that have the debug symbols; here are a few examples:<br /> ** For Debian and Ubuntu:<br /> $ '''sudo apt-get install claws-mail-dbg'''<br /> ** For Mandriva:<br /> $ '''sudo urpmi claws-mail-debug'''<br /> ** For Fedora:<br /> $ '''sudo yum install claws-mail-debuginfo'''<br /> ** For Suse:<br /> $ '''sudo smart install claws-mail-debuginfo'''<br /> <br /> Once you have done that, you can proceed to reproduce the crash inside gdb, the Gnu DeBugger. From a command-line, start claws-mail from gdb:<br /> $ '''gdb claws-mail'''<br /> GNU gdb 6.4-debian<br /> [...]<br /> (gdb) '''run --debug'''<br /> Starting program: /usr/local/bin/claws-mail<br /> [...] ''Here, Claws Mail starts. Make it crash, and you will get the following:''<br /> Program received signal SIGSEGV, Segmentation fault.<br /> [Switching to Thread -1227139392 (LWP 10159)]<br /> 0xffffe410 in __kernel_vsyscall ()<br /> ''You can now ask gdb for the backtrace:''<br /> (gdb) '''thread apply all bt'''<br /> <br /> You should now get an output resembling this:<br /> Thread 2 (Thread -1249215568 (LWP 10168)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb7aeec76 in pthread_cond_wait@@GLIBC_2.3.2 ()<br /> from /lib/tls/i686/cmov/libpthread.so.0<br /> #2 0xb71ead5a in mailsem_internal_wait (s=0x82fe798) at mailsem.c:121<br /> #3 0xb71eaf11 in mailsem_down (sem=0xfffffffc) at mailsem.c:321<br /> #4 0x081c96e0 in thread_run (data=0x82e9eb0) at etpan-thread-manager.c:318<br /> #5 0xb7aec341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0<br /> #6 0xb6fef4ee in clone () from /lib/tls/i686/cmov/libc.so.6<br /> <br /> Thread 1 (Thread -1227139392 (LWP 10159)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb6fe58c4 in poll () from /lib/tls/i686/cmov/libc.so.6<br /> #2 0xb72b9b08 in g_main_context_iterate (context=0x833efd0, block=1,<br /> dispatch=1, self=0x8311100) at gmain.c:2977<br /> #3 0xb72b9fd8 in IA__g_main_loop_run (loop=0x82d1180) at gmain.c:2879<br /> #4 0xb7710765 in IA__gtk_main () at gtkmain.c:1026<br /> #5 0x08102191 in main (argc=1, argv=0xbf9131a4) at main.c:1093<br /> (gdb) '''quit'''<br /> <br /> This is what you should copy and paste in a [http://thewildbeast.co.uk/claws-mail/bugzilla/ new bug report].<br /> Don't forget to briefly explain what you were doing, which version you were using, and so on.<br /> <br /> Finally, gdb can also be used to attach to an already running Claws Mail:<br /> $ '''gdb -p `pidof claws-mail`'''<br /> You can use that for example if Claws Mail is unresponsive; once in gdb, you can use '''Ctrl-C''' to interrupt execution and '''thread apply all bt''' to see where Claws Mail was stuck.<br /> <br /> == Strange crasher bug ==<br /> Some crashes are due to memory corruptions that occured before the crash. In this case, gdb doesn't help as much as it could, but valgrind does a great job in tracing the execution and showing clearly where the problem lies.<br /> <br /> You can run valgrind with:<br /> $ '''G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind \'''<br /> '''--tool=memcheck --error-limit=no --leak-check=full \'''<br /> '''--show-reachable=yes claws-mail 2&gt;&amp;1 | tee valgrind.log'''<br /> <br /> Valgrind slows down the execution a lot. Just redo the actions needed to reproduce the crash, then exit. If the crash doesn't happen under valgrind, the log may still contain the crash causes (and valgrind just changes the result).<br /> <br /> Thanks for helping making Claws Mail better!</div> Colin https://www.claws-mail.org/faq/index.php?title=Fortunes&diff=1867 Fortunes 2007-06-12T06:40:24Z <p>Colin: </p> <hr /> <div> 08:14 &lt;@colinl&gt; hehehe, Claws is actually quite usable in valgrind :)<br /> 08:15 &lt;@colinl&gt; it feels a little bit like Evo, actually<br /> <br /> 23:05 &lt;@wwp&gt; there's no magics in claws mail</div> Colin https://www.claws-mail.org/faq/index.php?title=Debugging_Claws&diff=1860 Debugging Claws 2007-06-08T09:39:37Z <p>Colin: /* Crasher bug */</p> <hr /> <div>If you find a bug in Claws Mail, reporting it is the best way to have it fixed. Here are some pointers on how to make the most useful bugreport possible.<br /> <br /> == Functionality bug (non crasher) ==<br /> If you face a functional bug, where Claws Mail doesn't crash, but doesn't do the right thing in your opinion, open a bug on the [http://thewildbeast.co.uk/claws-mail/bugzilla/ bug tracker] describing the action you're trying to do.<br /> <br /> == Crasher bug ==<br /> If Claws Mail crashes when you're trying to perform some action, we will need more information than just the steps to reproduce: this sort of bug often depends on many variables, previous actions, your setup, etc. We will need a backtrace, which shows us precisely where in the code Claws crashes and where it came from.<br /> <br /> To generate a good backtrace, Claws Mail needs to have &quot;debug symbols&quot; available. Without debug symbols, the backtrace is useless because it will not show function information, line numbers and other interesting things.<br /> <br /> The way to have debug symbols available depends on the way you installed Claws Mail:<br /> <br /> * Self-compiled Claws Mail: if you compile Claws Mail yourself, rebuild it using the following:<br /> $ '''make clean'''<br /> $ '''export CFLAGS=-g'''<br /> $ '''./configure'''<br /> $ '''make'''<br /> $ '''sudo make install'''<br /> <br /> * Claws Mail packages from your distribution: if you installed Claws Mail from pre-compiled packages, you will often have to install a special &quot;debug&quot; package that have the debug symbols; here are a few examples:<br /> ** For Debian and Ubuntu:<br /> $ '''sudo apt-get install claws-mail-dbg'''<br /> ** For Mandriva:<br /> $ '''sudo urpmi claws-mail-debug'''<br /> ** For Fedora:<br /> $ '''sudo yum install claws-mail-debuginfo'''<br /> ** For Suse:<br /> $ '''sudo smart install claws-mail-debuginfo'''<br /> <br /> Once you have done that, you can proceed to reproduce the crash inside gdb, the Gnu DeBugger. From a command-line, start claws-mail from gdb:<br /> $ '''gdb claws-mail'''<br /> GNU gdb 6.4-debian<br /> [...]<br /> (gdb) '''run --debug'''<br /> Starting program: /usr/local/bin/claws-mail<br /> [...] ''Here, Claws Mail starts. Make it crash, and you will get the following:''<br /> Program received signal SIGSEGV, Segmentation fault.<br /> [Switching to Thread -1227139392 (LWP 10159)]<br /> 0xffffe410 in __kernel_vsyscall ()<br /> ''You can now ask gdb for the backtrace:''<br /> (gdb) '''thread apply all bt'''<br /> <br /> You should now get an output resembling this:<br /> Thread 2 (Thread -1249215568 (LWP 10168)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb7aeec76 in pthread_cond_wait@@GLIBC_2.3.2 ()<br /> from /lib/tls/i686/cmov/libpthread.so.0<br /> #2 0xb71ead5a in mailsem_internal_wait (s=0x82fe798) at mailsem.c:121<br /> #3 0xb71eaf11 in mailsem_down (sem=0xfffffffc) at mailsem.c:321<br /> #4 0x081c96e0 in thread_run (data=0x82e9eb0) at etpan-thread-manager.c:318<br /> #5 0xb7aec341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0<br /> #6 0xb6fef4ee in clone () from /lib/tls/i686/cmov/libc.so.6<br /> <br /> Thread 1 (Thread -1227139392 (LWP 10159)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb6fe58c4 in poll () from /lib/tls/i686/cmov/libc.so.6<br /> #2 0xb72b9b08 in g_main_context_iterate (context=0x833efd0, block=1,<br /> dispatch=1, self=0x8311100) at gmain.c:2977<br /> #3 0xb72b9fd8 in IA__g_main_loop_run (loop=0x82d1180) at gmain.c:2879<br /> #4 0xb7710765 in IA__gtk_main () at gtkmain.c:1026<br /> #5 0x08102191 in main (argc=1, argv=0xbf9131a4) at main.c:1093<br /> (gdb) '''quit'''<br /> <br /> This is what you should copy and paste in a [http://thewildbeast.co.uk/claws-mail/bugzilla/ new bug report].<br /> Don't forget to briefly explain what you were doing, which version you were using, and so on.<br /> <br /> Finally, gdb can also be used to attach to an already running Claws Mail:<br /> $ '''gdb -p `pidof claws-mail`'''<br /> You can use that for example if Claws Mail is unresponsive; once in gdb, you can use '''Ctrl-C''' to interrupt execution and '''thread apply all bt''' to see where Claws Mail was stuck.<br /> <br /> <br /> Thanks for helping making Claws Mail better!</div> Colin https://www.claws-mail.org/faq/index.php?title=Debugging_Claws&diff=1859 Debugging Claws 2007-06-08T09:27:42Z <p>Colin: /* Crasher bug */</p> <hr /> <div>If you find a bug in Claws Mail, reporting it is the best way to have it fixed. Here are some pointers on how to make the most useful bugreport possible.<br /> <br /> == Functionality bug (non crasher) ==<br /> If you face a functional bug, where Claws Mail doesn't crash, but doesn't do the right thing in your opinion, open a bug on the [http://thewildbeast.co.uk/claws-mail/bugzilla/ bug tracker] describing the action you're trying to do.<br /> <br /> == Crasher bug ==<br /> If Claws Mail crashes when you're trying to perform some action, we will need more information than just the steps to reproduce: this sort of bug often depends on many variables, previous actions, your setup, etc. We will need a backtrace, which shows us precisely where in the code Claws crashes and where it came from.<br /> <br /> To generate a good backtrace, Claws Mail needs to have &quot;debug symbols&quot; available. Without debug symbols, the backtrace is useless because it will not show function information, line numbers and other interesting things.<br /> <br /> The way to have debug symbols available depends on the way you installed Claws Mail:<br /> <br /> * Self-compiled Claws Mail: if you compile Claws Mail yourself, rebuild it using the following:<br /> $ '''make clean'''<br /> $ '''export CFLAGS=-g'''<br /> $ '''./configure'''<br /> $ '''make'''<br /> $ '''sudo make install'''<br /> <br /> * Claws Mail packages from your distribution: if you installed Claws Mail from pre-compiled packages, you will often have to install a special &quot;debug&quot; package that have the debug symbols; here are a few examples:<br /> ** For Debian and Ubuntu:<br /> $ '''sudo apt-get install claws-mail-dbg'''<br /> ** For Mandriva:<br /> $ '''sudo urpmi claws-mail-debug'''<br /> ** For Fedora:<br /> $ '''sudo yum install claws-mail-debuginfo'''<br /> ** For Suse:<br /> $ '''sudo smart install claws-mail-debuginfo'''<br /> <br /> Once you have done that, you can proceed to reproduce the crash inside gdb, the Gnu DeBugger. From a command-line, start claws-mail from gdb:<br /> $ '''gdb claws-mail'''<br /> GNU gdb 6.4-debian<br /> [...]<br /> (gdb) '''run --debug'''<br /> Starting program: /usr/local/bin/claws-mail<br /> [...] ''Here, Claws Mail starts. Make it crash, and you will get the following:''<br /> Program received signal SIGSEGV, Segmentation fault.<br /> [Switching to Thread -1227139392 (LWP 10159)]<br /> 0xffffe410 in __kernel_vsyscall ()<br /> ''You can now ask gdb for the backtrace:''<br /> (gdb) '''thread apply all bt'''<br /> <br /> You should now get an output resembling this:<br /> Thread 2 (Thread -1249215568 (LWP 10168)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb7aeec76 in pthread_cond_wait@@GLIBC_2.3.2 ()<br /> from /lib/tls/i686/cmov/libpthread.so.0<br /> #2 0xb71ead5a in mailsem_internal_wait (s=0x82fe798) at mailsem.c:121<br /> #3 0xb71eaf11 in mailsem_down (sem=0xfffffffc) at mailsem.c:321<br /> #4 0x081c96e0 in thread_run (data=0x82e9eb0) at etpan-thread-manager.c:318<br /> #5 0xb7aec341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0<br /> #6 0xb6fef4ee in clone () from /lib/tls/i686/cmov/libc.so.6<br /> <br /> Thread 1 (Thread -1227139392 (LWP 10159)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb6fe58c4 in poll () from /lib/tls/i686/cmov/libc.so.6<br /> #2 0xb72b9b08 in g_main_context_iterate (context=0x833efd0, block=1,<br /> dispatch=1, self=0x8311100) at gmain.c:2977<br /> #3 0xb72b9fd8 in IA__g_main_loop_run (loop=0x82d1180) at gmain.c:2879<br /> #4 0xb7710765 in IA__gtk_main () at gtkmain.c:1026<br /> #5 0x08102191 in main (argc=1, argv=0xbf9131a4) at main.c:1093<br /> (gdb) '''quit'''<br /> <br /> This is what you should copy and paste in a [http://thewildbeast.co.uk/claws-mail/bugzilla/ new bug report].<br /> Don't forget to briefly explain what you were doing, which version you were using, and so on.<br /> <br /> Thanks for helping making Claws Mail better!</div> Colin https://www.claws-mail.org/faq/index.php?title=Debugging_Claws&diff=1858 Debugging Claws 2007-06-08T08:50:02Z <p>Colin: /* Crasher bug */</p> <hr /> <div>If you find a bug in Claws Mail, reporting it is the best way to have it fixed. Here are some pointers on how to make the most useful bugreport possible.<br /> <br /> == Functionality bug (non crasher) ==<br /> If you face a functional bug, where Claws Mail doesn't crash, but doesn't do the right thing in your opinion, open a bug on the [http://thewildbeast.co.uk/claws-mail/bugzilla/ bug tracker] describing the action you're trying to do.<br /> <br /> == Crasher bug ==<br /> If Claws Mail crashes when you're trying to perform some action, we will need a more information than just the steps to reproduce: this sort of bug often depends on many variables, previous actions, your setup, etc. We will need a backtrace, which shows us precisely where in the code Claws crashes and where it came from.<br /> <br /> To generate a good backtrace, Claws Mail needs to have &quot;debug symbols&quot; available. Without debug symbols, the backtrace is useless because it will not show function information, line numbers and other interesting things.<br /> <br /> The way to have debug symbols available depends on the way you installed Claws Mail:<br /> <br /> * Self-compiled Claws Mail: if you compile Claws Mail yourself, rebuild it using the following:<br /> $ '''make clean'''<br /> $ '''export CFLAGS=-g'''<br /> $ '''./configure'''<br /> $ '''make'''<br /> $ '''sudo make install'''<br /> <br /> * Claws Mail packages from your distribution: if you installed Claws Mail from pre-compiled packages, you will often have to install a special &quot;debug&quot; package that have the debug symbols; here are a few examples:<br /> ** For Debian and Ubuntu:<br /> $ '''sudo apt-get install claws-mail-dbg'''<br /> ** For Mandriva:<br /> $ '''sudo urpmi claws-mail-debug'''<br /> ** For Fedora:<br /> $ '''sudo yum install claws-mail-debuginfo'''<br /> ** For Suse:<br /> $ '''sudo smart install claws-mail-debuginfo'''<br /> <br /> Once you have done that, you can proceed to reproduce the crash inside gdb, the Gnu DeBugger. From a command-line, start claws-mail from gdb:<br /> $ '''gdb claws-mail'''<br /> GNU gdb 6.4-debian<br /> [...]<br /> (gdb) '''run --debug'''<br /> Starting program: /usr/local/bin/claws-mail<br /> [...] ''Here, Claws Mail starts. Make it crash, and you will get the following:''<br /> Program received signal SIGSEGV, Segmentation fault.<br /> [Switching to Thread -1227139392 (LWP 10159)]<br /> 0xffffe410 in __kernel_vsyscall ()<br /> ''You can now ask gdb for the backtrace:''<br /> (gdb) '''thread apply all bt'''<br /> <br /> You should now get an output resembling this:<br /> Thread 2 (Thread -1249215568 (LWP 10168)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb7aeec76 in pthread_cond_wait@@GLIBC_2.3.2 ()<br /> from /lib/tls/i686/cmov/libpthread.so.0<br /> #2 0xb71ead5a in mailsem_internal_wait (s=0x82fe798) at mailsem.c:121<br /> #3 0xb71eaf11 in mailsem_down (sem=0xfffffffc) at mailsem.c:321<br /> #4 0x081c96e0 in thread_run (data=0x82e9eb0) at etpan-thread-manager.c:318<br /> #5 0xb7aec341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0<br /> #6 0xb6fef4ee in clone () from /lib/tls/i686/cmov/libc.so.6<br /> <br /> Thread 1 (Thread -1227139392 (LWP 10159)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb6fe58c4 in poll () from /lib/tls/i686/cmov/libc.so.6<br /> #2 0xb72b9b08 in g_main_context_iterate (context=0x833efd0, block=1,<br /> dispatch=1, self=0x8311100) at gmain.c:2977<br /> #3 0xb72b9fd8 in IA__g_main_loop_run (loop=0x82d1180) at gmain.c:2879<br /> #4 0xb7710765 in IA__gtk_main () at gtkmain.c:1026<br /> #5 0x08102191 in main (argc=1, argv=0xbf9131a4) at main.c:1093<br /> (gdb) '''quit'''<br /> <br /> This is what you should copy and paste in a [http://thewildbeast.co.uk/claws-mail/bugzilla/ new bug report].<br /> Don't forget to briefly explain what you were doing, which version you were using, and so on.<br /> <br /> Thanks for helping making Claws Mail better!</div> Colin https://www.claws-mail.org/faq/index.php?title=Debugging_Claws&diff=1857 Debugging Claws 2007-06-08T08:42:01Z <p>Colin: /* Debugging Claws Mail */</p> <hr /> <div>If you find a bug in Claws Mail, reporting it is the best way to have it fixed. Here are some pointers on how to make the most useful bugreport possible.<br /> <br /> == Functionality bug (non crasher) ==<br /> If you face a functional bug, where Claws Mail doesn't crash, but doesn't do the right thing in your opinion, open a bug on the [http://thewildbeast.co.uk/claws-mail/bugzilla/ bug tracker] describing the action you're trying to do.<br /> <br /> == Crasher bug ==<br /> If Claws Mail crashes when you're trying to perform some action, we will need a more information than just the steps to reproduce: this sort of bug often depends on many variables, previous actions, your setup, etc. We will need a backtrace, which shows us precisely where in the code Claws crashes and where it came from.<br /> <br /> To generate a good backtrace, Claws Mail needs to have &quot;debug symbols&quot; available. Without debug symbols, the backtrace is useless because it will not show function information, line numbers and other interesting things.<br /> <br /> The way to have debug symbols available depends on the way you installed Claws Mail:<br /> <br /> * Self-compiled Claws Mail: if you compile Claws Mail yourself, rebuild it using the following:<br /> $ '''make clean'''<br /> $ '''export CFLAGS=-g'''<br /> $ '''./configure'''<br /> $ '''make'''<br /> $ '''sudo make install'''<br /> <br /> * Claws Mail packages from your distribution: if you installed Claws Mail from pre-compiled packages, you will often have to install a special &quot;debug&quot; package that have the debug symbols; here are a few examples:<br /> ** For Debian and Ubuntu:<br /> $ '''sudo apt-get install claws-mail-dbg'''<br /> ** For Mandriva:<br /> $ '''sudo urpmi claws-mail-debug'''<br /> ** For Fedora:<br /> $ '''sudo yum install claws-mail-debuginfo'''<br /> ** For Suse:<br /> $ '''sudo smart install claws-mail-debuginfo'''<br /> <br /> Once you have done that, you can proceed to reproduce the crash inside gdb, the Gnu DeBugger. From a command-line, start claws-mail from gdb:<br /> $ '''gdb claws-mail'''<br /> GNU gdb 6.4-debian<br /> [...]<br /> (gdb) '''run'''<br /> Starting program: /usr/local/bin/claws-mail<br /> [...] ''Here, Claws Mail starts. Make it crash, and you will get the following:''<br /> Program received signal SIGSEGV, Segmentation fault.<br /> [Switching to Thread -1227139392 (LWP 10159)]<br /> 0xffffe410 in __kernel_vsyscall ()<br /> ''You can now ask gdb for the backtrace:''<br /> (gdb) '''thread apply all bt'''<br /> <br /> You should now get an output resembling this:<br /> Thread 2 (Thread -1249215568 (LWP 10168)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb7aeec76 in pthread_cond_wait@@GLIBC_2.3.2 ()<br /> from /lib/tls/i686/cmov/libpthread.so.0<br /> #2 0xb71ead5a in mailsem_internal_wait (s=0x82fe798) at mailsem.c:121<br /> #3 0xb71eaf11 in mailsem_down (sem=0xfffffffc) at mailsem.c:321<br /> #4 0x081c96e0 in thread_run (data=0x82e9eb0) at etpan-thread-manager.c:318<br /> #5 0xb7aec341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0<br /> #6 0xb6fef4ee in clone () from /lib/tls/i686/cmov/libc.so.6<br /> <br /> Thread 1 (Thread -1227139392 (LWP 10159)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb6fe58c4 in poll () from /lib/tls/i686/cmov/libc.so.6<br /> #2 0xb72b9b08 in g_main_context_iterate (context=0x833efd0, block=1,<br /> dispatch=1, self=0x8311100) at gmain.c:2977<br /> #3 0xb72b9fd8 in IA__g_main_loop_run (loop=0x82d1180) at gmain.c:2879<br /> #4 0xb7710765 in IA__gtk_main () at gtkmain.c:1026<br /> #5 0x08102191 in main (argc=1, argv=0xbf9131a4) at main.c:1093<br /> (gdb) '''quit'''<br /> <br /> This is what you should copy and paste in a [http://thewildbeast.co.uk/claws-mail/bugzilla/ new bugreport].<br /> Don't forget to explain a bit what you were doing and so on, this will help too.<br /> <br /> Thanks for helping making Claws Mail better!</div> Colin https://www.claws-mail.org/faq/index.php?title=Debugging_Claws&diff=1856 Debugging Claws 2007-06-08T08:40:11Z <p>Colin: </p> <hr /> <div>= Debugging Claws Mail =<br /> If you find a bug in Claws Mail, reporting it is the best way to have it fixed. Here are some pointers on how to make the most useful bugreport possible.<br /> <br /> == Functionality bug (non crasher) ==<br /> If you face a functional bug, where Claws Mail doesn't crash, but doesn't do the right thing in your opinion, open a bug on the [http://thewildbeast.co.uk/claws-mail/bugzilla/ bug tracker] describing the action you're trying to do.<br /> <br /> == Crasher bug ==<br /> If Claws Mail crashes when you're trying to perform some action, we will need a more information than just the steps to reproduce: this sort of bug often depends on many variables, previous actions, your setup, etc. We will need a backtrace, which shows us precisely where in the code Claws crashes and where it came from.<br /> <br /> To generate a good backtrace, Claws Mail needs to have &quot;debug symbols&quot; available. Without debug symbols, the backtrace is useless because it will not show function information, line numbers and other interesting things.<br /> <br /> The way to have debug symbols available depends on the way you installed Claws Mail:<br /> <br /> * Self-compiled Claws Mail: if you compile Claws Mail yourself, rebuild it using the following:<br /> $ '''make clean'''<br /> $ '''export CFLAGS=-g'''<br /> $ '''./configure'''<br /> $ '''make'''<br /> $ '''sudo make install'''<br /> <br /> * Claws Mail packages from your distribution: if you installed Claws Mail from pre-compiled packages, you will often have to install a special &quot;debug&quot; package that have the debug symbols; here are a few examples:<br /> ** For Debian and Ubuntu:<br /> $ '''sudo apt-get install claws-mail-dbg'''<br /> ** For Mandriva:<br /> $ '''sudo urpmi claws-mail-debug'''<br /> ** For Fedora:<br /> $ '''sudo yum install claws-mail-debuginfo'''<br /> ** For Suse:<br /> $ '''sudo smart install claws-mail-debuginfo'''<br /> <br /> Once you have done that, you can proceed to reproduce the crash inside gdb, the Gnu DeBugger. From a command-line, start claws-mail from gdb:<br /> $ '''gdb claws-mail'''<br /> GNU gdb 6.4-debian<br /> [...]<br /> (gdb) '''run'''<br /> Starting program: /usr/local/bin/claws-mail<br /> [...] ''Here, Claws Mail starts. Make it crash, and you will get the following:''<br /> Program received signal SIGSEGV, Segmentation fault.<br /> [Switching to Thread -1227139392 (LWP 10159)]<br /> 0xffffe410 in __kernel_vsyscall ()<br /> ''You can now ask gdb for the backtrace:''<br /> (gdb) '''thread apply all bt'''<br /> <br /> You should now get an output resembling this:<br /> Thread 2 (Thread -1249215568 (LWP 10168)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb7aeec76 in pthread_cond_wait@@GLIBC_2.3.2 ()<br /> from /lib/tls/i686/cmov/libpthread.so.0<br /> #2 0xb71ead5a in mailsem_internal_wait (s=0x82fe798) at mailsem.c:121<br /> #3 0xb71eaf11 in mailsem_down (sem=0xfffffffc) at mailsem.c:321<br /> #4 0x081c96e0 in thread_run (data=0x82e9eb0) at etpan-thread-manager.c:318<br /> #5 0xb7aec341 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0<br /> #6 0xb6fef4ee in clone () from /lib/tls/i686/cmov/libc.so.6<br /> <br /> Thread 1 (Thread -1227139392 (LWP 10159)):<br /> #0 0xffffe410 in __kernel_vsyscall ()<br /> #1 0xb6fe58c4 in poll () from /lib/tls/i686/cmov/libc.so.6<br /> #2 0xb72b9b08 in g_main_context_iterate (context=0x833efd0, block=1,<br /> dispatch=1, self=0x8311100) at gmain.c:2977<br /> #3 0xb72b9fd8 in IA__g_main_loop_run (loop=0x82d1180) at gmain.c:2879<br /> #4 0xb7710765 in IA__gtk_main () at gtkmain.c:1026<br /> #5 0x08102191 in main (argc=1, argv=0xbf9131a4) at main.c:1093<br /> (gdb) '''quit'''<br /> <br /> This is what you should copy and paste in a [http://thewildbeast.co.uk/claws-mail/bugzilla/ new bugreport].<br /> Don't forget to explain a bit what you were doing and so on, this will help too.<br /> <br /> Thanks for helping making Claws Mail better!</div> Colin https://www.claws-mail.org/faq/index.php?title=S/MIME_howto&diff=1753 S/MIME howto 2007-04-27T19:51:51Z <p>Colin: /* Working with S/MIME plugin and problems/bugs */</p> <hr /> <div>==Claws Mail &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, recommended: v2.7.1 (multiple RFC fixes), or CVS<br /> # recent S/MIME plugin, recommended: v0.6.0 (multiple RFC fixes), or CVS<br /> # S/MIME certificate (this howto is based on Thawte Freemail certs)<br /> # pinentry, gnupg, gpgme, ca-certificates (and openssl) in recent versions<br /> # gpg-agent to cache the passphrase<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 /> 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 /> ===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 /> If this doesn't show a secret key, you may have to import the three certificates from certbundle.pem: separate them to three files (starting with &quot;--- BEGIN CERTIFICATE ---&quot; and ending with &quot;--- END CERTIFICATE ---&quot;), then run &lt;br /&gt; <br /> $ gpgsm --import cert1.pem cert2.pem cert3.pem<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. I also added my own certificate to the trustlist. 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 /> * As of current CVS (CM =&gt;2.7.0cvs11 and S/MIME &gt;=0.5.8cvs2) the S/MIME plugin is more RFC compliant and signing, encrypting, decrypting and verifying messages is working very well now. I tested compatibility with Outlook 11 and Thunderbird, some Kmail emails in my inbox decrypt fine too!<br /> <br /> * I'm only aware of one problem, where you'll get &quot;Bad signature&quot; warnings, when you forward (via CM) a signed+encrypted email with an attachment and sign+encrypt the email itself again too.<br /> <br /> * Error: Couldn't decrypt: &quot;unsupported algorithm&quot; - this happens when you receive an email which got encrypted with RC2 algorithm (e.g. some Outlook 11 and some Thunderbird MUAs). I'm currently not aware of a solution, as the underlying libgcrypt doesn't handle it for patent reasons. (see https://intevation.de/roundup/aegypten/issue11 and http://forums.mozillazine.org/viewtopic.php?p=2858116 )<br /> <br /> * 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 /> * 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 additional key that is expired and you still want to keep it to be able to decrypt older emails). It only shows the Key ID and no info about the expiry date which makes it more difficult to choose the correct one.</div> Colin https://www.claws-mail.org/faq/index.php?title=S/MIME_howto&diff=1725 S/MIME howto 2007-04-13T13:18:09Z <p>Colin: /* Requirements */</p> <hr /> <div>==Claws Mail &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, recommended: v2.7.1 (multiple RFC fixes), or CVS<br /> # recent S/MIME plugin, recommended: v0.6.0 (multiple RFC fixes), or CVS<br /> # S/MIME certificate (this howto is based on Thawte Freemail certs)<br /> # pinentry, gnupg, gpgme, ca-certificates (and openssl) in recent versions<br /> # gpg-agent to cache the passphrase<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 /> 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 /> ===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 /> If this doesn't show a secret key, you may have to import the three certificates from certbundle.pem: separate them to three files (starting with &quot;--- BEGIN CERTIFICATE ---&quot; and ending with &quot;--- END CERTIFICATE ---&quot;), then run &lt;br /&gt; <br /> $ gpgsm --import cert1.pem cert2.pem cert3.pem<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. I also added my own certificate to the trustlist. 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 /> * As of current CVS (CM =&gt;2.7.0cvs11 and S/MIME &gt;=0.5.8cvs2) the S/MIME plugin is more RFC compliant and signing, encrypting, decrypting and verifying messages is working very well now. I tested compatibility with Outlook 11 and Thunderbird, some Kmail emails in my inbox decrypt fine too!<br /> <br /> * I'm only aware of one problem, where you'll get &quot;Bad signature&quot; warnings, when you forward (via CM) a signed+encrypted email with an attachment and sign+encrypt the email itself again too.<br /> <br /> * Error: Couldn't decrypt: &quot;unsupported algorithm&quot; - this happens when you receive an email which got encrypted with RC2 algorithm (e.g. some Outlook 11 and some Thunderbird MUAs). I'm currently not aware of a solution, as the underlying libgcrypt doesn't handle it well (https://intevation.de/roundup/aegypten/issue11)<br /> <br /> * 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 /> * 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 additional key that is expired and you still want to keep it to be able to decrypt older emails). It only shows the Key ID and no info about the expiry date which makes it more difficult to choose the correct one.</div> Colin https://www.claws-mail.org/faq/index.php?title=S/MIME_howto&diff=1724 S/MIME howto 2007-04-13T13:17:30Z <p>Colin: gpg-agent is not optional</p> <hr /> <div>==Claws Mail &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, recommended: v2.7.1 (multiple RFC fixes), or CVS<br /> # recent S/MIME plugin, recommended: v0.6.0 (multiple RFC fixes), or CVS<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 /> 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 /> ===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 /> If this doesn't show a secret key, you may have to import the three certificates from certbundle.pem: separate them to three files (starting with &quot;--- BEGIN CERTIFICATE ---&quot; and ending with &quot;--- END CERTIFICATE ---&quot;), then run &lt;br /&gt; <br /> $ gpgsm --import cert1.pem cert2.pem cert3.pem<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. I also added my own certificate to the trustlist. 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 /> * As of current CVS (CM =&gt;2.7.0cvs11 and S/MIME &gt;=0.5.8cvs2) the S/MIME plugin is more RFC compliant and signing, encrypting, decrypting and verifying messages is working very well now. I tested compatibility with Outlook 11 and Thunderbird, some Kmail emails in my inbox decrypt fine too!<br /> <br /> * I'm only aware of one problem, where you'll get &quot;Bad signature&quot; warnings, when you forward (via CM) a signed+encrypted email with an attachment and sign+encrypt the email itself again too.<br /> <br /> * Error: Couldn't decrypt: &quot;unsupported algorithm&quot; - this happens when you receive an email which got encrypted with RC2 algorithm (e.g. some Outlook 11 and some Thunderbird MUAs). I'm currently not aware of a solution, as the underlying libgcrypt doesn't handle it well (https://intevation.de/roundup/aegypten/issue11)<br /> <br /> * 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 /> * 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 additional key that is expired and you still want to keep it to be able to decrypt older emails). It only shows the Key ID and no info about the expiry date which makes it more difficult to choose the correct one.</div> Colin https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=1638 MediaWiki:Sidebar 2007-02-27T12:20:52Z <p>Colin: </p> <hr /> <div>* FAQ navigation<br /> ** mainpage|mainpage<br /> ** General Information|General Information<br /> ** Installation and Configuration|Installation and Configuration<br /> ** Interface|Interface<br /> ** Composing Mails Or News|Composing Mails Or News<br /> ** Filtering and Processing of Messages|Filtering and Processing of Messages<br /> ** Actions|Actions<br /> ** Templates|Templates<br /> ** Plugins|Plugins<br /> ** S/MIME_howto|S/MIME Plugin Howto<br /> ** Using Claws Mail with other programs|Using Claws Mail with other programs<br /> &lt;!-- ** portal-url|portal --&gt;<br /> &lt;!-- ** currentevents-url|currentevents --&gt;<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> &lt;!-- ** helppage|help --&gt;<br /> &lt;!-- ** sitesupport-url|sitesupport --&gt;<br /> <br /> * Main Site<br /> ** http://www.claws-mail.org/|What is it?<br /> ** http://www.claws-mail.org/news.php|News<br /> ** http://www.claws-mail.org/features.php|Features<br /> ** http://www.claws-mail.org/screenshots.php|Screenshots<br /> ** http://www.claws-mail.org/documentation.php|User manual<br /> ** http://www.claws-mail.org/downloads.php|Downloads<br /> ** http://www.claws-mail.org/plugins.php|Plugins<br /> ** http://www.claws-mail.org/themes.php|Themes<br /> ** http://www.claws-mail.org/tools.php|Tools<br /> ** http://sourceforge.net/projects/sylpheed-claws/|The Project<br /> ** http://www.claws-mail.org/devel.php|Developers<br /> ** http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi|Bug Tracker<br /> ** http://www.claws-mail.org/i18n.php|i18n Status<br /> ** http://www.claws-mail.org/cvs.php|Get CVS<br /> ** http://www.claws-mail.org/cvstrak-gtk2.php|CVS Tracker<br /> ** http://cvs.sunsite.dk/viewcvs.cgi/sylpheedclaws/sylpheed-claws/?only_with_tag=gtk2|Browse CVS<br /> ** http://www.claws-mail.org/barometz.php|CVS Stats<br /> ** http://www.claws-mail.org/MLs.php|Contact<br /> ** http://www.claws-mail.org/reviews.php|Reviews<br /> ** http://www.claws-mail.org/theteam.php|The Team<br /> ** http://planet.claws-mail.org/|The Planet<br /> ** http://www.cafepress.com/claws_mail/|The Claws Store</div> Colin https://www.claws-mail.org/faq/index.php?title=Fortunes&diff=1637 Fortunes 2007-02-21T08:17:42Z <p>Colin: </p> <hr /> <div> 08:14 &lt;@colinl&gt; hehehe, Claws is actually quite usable in valgrind :)<br /> 08:15 &lt;@colinl&gt; it feels a little bit like Evo, actually</div> Colin https://www.claws-mail.org/faq/index.php?title=Developer%27s_Corner&diff=1636 Developer's Corner 2007-02-21T08:16:51Z <p>Colin: /* The Claws Mail Developer's Corner */</p> <hr /> <div>=== The Claws Mail Developer's Corner ===<br /> <br /> * [[DevelopmentModel|Development Model]]<br /> * [[Ideas]]<br /> * [[ManualTODO|Manual TODO]]<br /> * [[Translator's Information]]<br /> <br /> <br /> <br /> * [[OctoberMeeting|The October 2006 Meeting]]<br /> * [[Fortunes]]</div> Colin https://www.claws-mail.org/faq/index.php?title=Translator%27s_Information&diff=1622 Translator's Information 2007-02-06T13:05:31Z <p>Colin: /* Information for new translators */</p> <hr /> <div>===The Release Process===<br /> <br /> : The Claws Team sets a date for release, at least 2 weeks in advance.<br /> :: &lt;u&gt;Week One:&lt;/u&gt; CVS feature freeze<br /> ::: No new features are added to CVS, the Team try to fix as many outstanding bugs as possible, test new features thoroughly, and improve any translatable strings as is deemed necessary.<br /> ::: A message announcing the forthcoming release is sent to the [http://www.claws-mail.org/MLs.php translators' mailing list].<br /> :: &lt;u&gt;Week Two:&lt;/u&gt; CVS string freeze<br /> ::: No new features are added and no translatable strings are changed or added.<br /> ::: During this second week, translators should update their local CVS trees and work on updating their translations. For those translators who are unable to build from CVS, up to date POT files are made available for download at http://www.claws-mail.org/i18n/.<br /> ::: Whan a translator has updated his/her translations they should be sent to Paul at [mailto:translations@thewildbeast.co.uk translations@thewildbeast.co.uk] at any time before the week is up. They will then be committed to CVS and included in the release.<br /> :: &lt;u&gt;Week Three:&lt;/u&gt; The release<br /> ::: The release will be made on Day One of Week Three.<br /> <br /> : &lt;b&gt;Bug-Fix Releases&lt;/b&gt;<br /> :: The Claws Team occasionally feels the need to make bug-fix releases. These are normally indicated by an increment of the MICRO_VERSION, (e.g. from version 2.7.0 to 2.7.1). The bug-fix releases contain none of the new features that have been added to CVS since the last major release, and they also do not contain any new translatable strings that may have been added to CVS. Therefore no translation updates are required for these releases and, consequently, the usual process, detailed above, is not initiated.<br /> <br /> ===Information for new translators===<br /> <br /> '''Starting fresh'''<br /> <br /> First grab yourself a copy of the Claws Mail sources, preferably from [http://www.claws-mail.org/cvs.php CVS], and create a claws-mail.pot file:<br /> : ./autogen.sh<br /> : cd po<br /> : make claws-mail.pot<br /> If you are not able to build from CVS, then get a copy of the last released sources from the [http://sourceforge.net/project/showfiles.php?group_id=25528&amp;package_id=147457 SourceForge Claws-Mail files page], which has the claws-mail.pot file included.<br /> <br /> Copy claws-mail.pot to [LANGUAGE ABBREV].po, (replace [LANGUAGE ABBREV] with the correct abbreviation for your language, e.g. 'is' if you are tranlating into Icelandic).<br /> : cp claws-mail.pot is.po<br /> <br /> Open your new po file with your favourite text editor, (or you may prefer to use a translation catalog editor, such as [http://poedit.sourceforge.net poedit] or [http://kbabel.kde.org/ kbabel], for example), and first edit the the header section of your file. You will need to replace the text in UPPERCASE with the correct values. The easiest way to workout how to do this is to compare it to another po file that already exists:<br /> <br /> {| border=&quot;1&quot;<br /> |+ po file header section<br /> ! your new po file !! es.po<br /> |-<br /> | &lt;pre&gt;# SOME DESCRIPTIVE TITLE.<br /> # Copyright (C) YEAR The Claws Mail Team<br /> # FIRST AUTHOR &lt;EMAIL@ADDRESS&gt;, YEAR.<br /> #<br /> #, fuzzy<br /> msgid &quot;&quot;<br /> msgstr &quot;&quot;<br /> &quot;Project-Id-Version: PACKAGE VERSION\n&quot;<br /> &quot;Report-Msgid-Bugs-To: paul@claws-mail.org\n&quot;<br /> &quot;POT-Creation-Date: 2007-01-30 09:03+0000\n&quot;<br /> &quot;PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n&quot;<br /> &quot;Last-Translator: FULL NAME &lt;EMAIL@ADDRESS&gt;\n&quot;<br /> &quot;Language-Team: LANGUAGE &lt;LL@li.org&gt;\n&quot;<br /> &quot;MIME-Version: 1.0\n&quot;<br /> &quot;Content-Type: text/plain; charset=CHARSET\n&quot;<br /> &quot;Content-Transfer-Encoding: 8bit\n&quot;<br /> &quot;Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n&quot;&lt;/pre&gt;<br /> | &lt;pre&gt;# Spanish translation of Claws Mail.<br /> # Copyright (C) 2000 Free Software Foundation, Inc.<br /> # Ricardo Mones &lt;ricardo@mones.org&gt;, 2000-2007.<br /> #<br /> msgid &quot;&quot;<br /> msgstr &quot;&quot;<br /> &quot;Project-Id-Version: claws mail\n&quot;<br /> &quot;Report-Msgid-Bugs-To: paul@claws-mail.org\n&quot;<br /> &quot;POT-Creation-Date: 2007-01-25 12:17+0100\n&quot;<br /> &quot;PO-Revision-Date: 2007-01-25 19:28+0200\n&quot;<br /> &quot;Last-Translator: Ricardo Mones &lt;ricardo@mones.org&gt;\n&quot;<br /> &quot;Language-Team: Ricardo Mones &lt;ricardo@mones.org&gt;\n&quot;<br /> &quot;MIME-Version: 1.0\n&quot;<br /> &quot;Content-Type: text/plain; charset=iso-8859-1\n&quot;<br /> &quot;Content-Transfer-Encoding: 8bit\n&quot;<br /> &quot;Plural-Forms: nplurals=2; plural=n != 1;\n&quot;&lt;/pre&gt;<br /> |}<br /> Consult the [http://www.gnu.org/software/gettext/manual/html_node/gettext_150.html gettext manual] for the correct Plural-Forms entry for your language.<br /> <br /> Next you will add your translated strings in the &lt;b&gt;msgstr&lt;/b&gt; sections.<br /> Again, an example from es.po:<br /> <br /> {|<br /> |-<br /> &lt;pre&gt;#: src/account.c:372<br /> msgid &quot;&quot;<br /> &quot;Some composing windows are open.\n&quot;<br /> &quot;Please close all the composing windows before editing the accounts.&quot;<br /> msgstr &quot;&quot;<br /> &quot;Hay ventanas de composici&amp;oacute;n abiertas.\n&quot;<br /> &quot;Cierre todas las ventanas de composici&amp;oacute;n antes de editar las cuentas.&quot;<br /> &lt;/pre&gt;<br /> |}<br /> <br /> There are some variations to the format which you should be aware of:<br /> <br /> :: Default hotkeys are indicated by the '_' character:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/account.c:767<br /> msgid &quot; _Set as default account &quot;<br /> msgstr &quot; _Establecer como primaria &quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: The presence of dynamically-generated text is indicated by the 'c-format' line. The 'c format', (%s, %d, etc.), in your &lt;b&gt;msgstr&lt;/b&gt; must match the one used in the &lt;b&gt;msgid&lt;/b&gt;:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/account.c:867<br /> #, c-format<br /> msgid &quot;Copy of %s&quot;<br /> msgstr &quot;Copia de %s&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Some strings have informational data for translators included in the &lt;b&gt;msgid&lt;/b&gt; part, delimited by the '|' character. Their purpose is to indicate the context of the string and they should not appear in your &lt;b&gt;msgstr&lt;/b&gt;:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/prefs_msg_colors.c:228<br /> msgid &quot;Tooltip|Pick color for 2nd level text&quot;<br /> msgstr &quot;Elejir el color para el texto de segundo nivel&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Other strings have the informational data included in the comment header, indicated by 'TRANSLATORS: &amp;hellip;':<br /> :::{|<br /> |-<br /> &lt;pre&gt;#. TRANSLATORS: 'color %d' refers to the filtering/processing<br /> #. rule name and should not be translated<br /> #: src/prefs_msg_colors.c:432 src/prefs_msg_colors.c:464<br /> #, c-format<br /> msgid &quot;Set label for 'color %d'&quot;<br /> msgstr &quot;Establecer la etiqueta para el &amp;laquo;color %d&amp;raquo;&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Some strings contain markup, which should be left in place:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/wizard.c:892<br /> msgid &quot;&lt;span weight=\&quot;bold\&quot;&gt;Your name:&lt;/span&gt;&quot;<br /> msgstr &quot;&lt;span weight=\&quot;bold\&quot;&gt;Su nombre:&lt;/span&gt;&quot;&lt;/pre&gt;<br /> |}<br /> <br /> <br /> '''Checking your translation for errors''' (and completeness)<br /> : /usr/bin/msgfmt -c --statistics is.po<br /> <br /> <br /> '''Building Claws Mail with your new translation included'''<br /> <br /> For this step you will need to be able to build from CVS, so a full set of development tools is required.<br /> <br /> Open the file configure.ac in your text editor and locate the line that begins with 'ALL_LINGUAS=', then add your language to the list of languages.<br /> <br /> Then run ./autogen.sh [OPTIONS], make, make install as usual.<br /> <br /> <br /> '''Updating your translation'''<br /> <br /> When it is time to update your translation, first update your [http://www.claws-mail.org/cvs.php CVS] working directory.<br /> Then do the following:<br /> <br /> : cd po<br /> : rm claws-mail.pot<br /> : make claws-mail.pot<br /> <br /> Next issue the following command to update your po file:<br /> <br /> : /usr/bin/msgmerge --update is.po claws-mail.pot<br /> <br /> Then open your file and locate the strings that need updating. These will have an empty &lt;b&gt;msgstr&lt;/b&gt; or will be marked 'fuzzy':<br /> ::{|<br /> |-<br /> &lt;pre&gt;#: src/mainwindow.c:838 src/messageview.c:332<br /> #, fuzzy<br /> msgid &quot;/_Tools/List _URLs...&quot;<br /> msgstr &quot;/_Herramientas/Exportar _HTML...&quot;&lt;/pre&gt;<br /> |}<br /> <br /> Correct the &lt;b&gt;msgstr&lt;/b&gt; and remove the line '#, fuzzy'.<br /> <br /> Obsolete entries will have been moved to the end of the file and have the following format:<br /> ::{|<br /> |-<br /> &lt;pre&gt;#~ msgid &quot;Really quit?&quot;<br /> #~ msgstr &quot;Salir realmente?&quot;<br /> &lt;/pre&gt;<br /> |}<br /> The obsolete entries can be removed.</div> Colin https://www.claws-mail.org/faq/index.php?title=Translator%27s_Information&diff=1621 Translator's Information 2007-02-06T13:03:09Z <p>Colin: /* Information for new translators */</p> <hr /> <div>===The Release Process===<br /> <br /> : The Claws Team sets a date for release, at least 2 weeks in advance.<br /> :: &lt;u&gt;Week One:&lt;/u&gt; CVS feature freeze<br /> ::: No new features are added to CVS, the Team try to fix as many outstanding bugs as possible, test new features thoroughly, and improve any translatable strings as is deemed necessary.<br /> ::: A message announcing the forthcoming release is sent to the [http://www.claws-mail.org/MLs.php translators' mailing list].<br /> :: &lt;u&gt;Week Two:&lt;/u&gt; CVS string freeze<br /> ::: No new features are added and no translatable strings are changed or added.<br /> ::: During this second week, translators should update their local CVS trees and work on updating their translations. For those translators who are unable to build from CVS, up to date POT files are made available for download at http://www.claws-mail.org/i18n/.<br /> ::: Whan a translator has updated his/her translations they should be sent to Paul at [mailto:translations@thewildbeast.co.uk translations@thewildbeast.co.uk] at any time before the week is up. They will then be committed to CVS and included in the release.<br /> :: &lt;u&gt;Week Three:&lt;/u&gt; The release<br /> ::: The release will be made on Day One of Week Three.<br /> <br /> : &lt;b&gt;Bug-Fix Releases&lt;/b&gt;<br /> :: The Claws Team occasionally feels the need to make bug-fix releases. These are normally indicated by an increment of the MICRO_VERSION, (e.g. from version 2.7.0 to 2.7.1). The bug-fix releases contain none of the new features that have been added to CVS since the last major release, and they also do not contain any new translatable strings that may have been added to CVS. Therefore no translation updates are required for these releases and, consequently, the usual process, detailed above, is not initiated.<br /> <br /> ===Information for new translators===<br /> <br /> '''Starting fresh'''<br /> <br /> First grab yourself a copy of the Claws Mail sources, preferably from [http://www.claws-mail.org/cvs.php CVS], and create a claws-mail.pot file:<br /> : ./autogen.sh<br /> : cd po<br /> : make claws-mail.pot<br /> If you are not able to build from CVS, then get a copy of the last released sources from the [http://sourceforge.net/project/showfiles.php?group_id=25528&amp;package_id=147457 SourceForge Claws-Mail files page], which has the claws-mail.pot file included.<br /> <br /> Copy claws-mail.pot to [LANGUAGE ABBREV].po, (replace [LANGUAGE ABBREV] with the correct abbreviation for your language, e.g. 'is' if you are tranlating into Icelandic).<br /> : cp claws-mail.pot is.po<br /> <br /> Open your new po file with your favourite text editor, (or you may prefer to use a translation catalog editor, such as [http://poedit.sourceforge.net poedit] or [http://kbabel.kde.org/ kbabel], for example), and first edit the the header section of your file. You will need to replace the text in UPPERCASE with the correct values. The easiest way to workout how to do this is to compare it to another po file that already exists:<br /> <br /> {| border=&quot;1&quot;<br /> |+ po file header section<br /> ! your new po file !! es.po<br /> |-<br /> | &lt;pre&gt;# SOME DESCRIPTIVE TITLE.<br /> # Copyright (C) YEAR The Claws Mail Team<br /> # FIRST AUTHOR &lt;EMAIL@ADDRESS&gt;, YEAR.<br /> #<br /> #, fuzzy<br /> msgid &quot;&quot;<br /> msgstr &quot;&quot;<br /> &quot;Project-Id-Version: PACKAGE VERSION\n&quot;<br /> &quot;Report-Msgid-Bugs-To: paul@claws-mail.org\n&quot;<br /> &quot;POT-Creation-Date: 2007-01-30 09:03+0000\n&quot;<br /> &quot;PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n&quot;<br /> &quot;Last-Translator: FULL NAME &lt;EMAIL@ADDRESS&gt;\n&quot;<br /> &quot;Language-Team: LANGUAGE &lt;LL@li.org&gt;\n&quot;<br /> &quot;MIME-Version: 1.0\n&quot;<br /> &quot;Content-Type: text/plain; charset=CHARSET\n&quot;<br /> &quot;Content-Transfer-Encoding: 8bit\n&quot;<br /> &quot;Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n&quot;&lt;/pre&gt;<br /> | &lt;pre&gt;# Spanish translation of Claws Mail.<br /> # Copyright (C) 2000 Free Software Foundation, Inc.<br /> # Ricardo Mones &lt;ricardo@mones.org&gt;, 2000-2007.<br /> #<br /> msgid &quot;&quot;<br /> msgstr &quot;&quot;<br /> &quot;Project-Id-Version: claws mail\n&quot;<br /> &quot;Report-Msgid-Bugs-To: paul@claws-mail.org\n&quot;<br /> &quot;POT-Creation-Date: 2007-01-25 12:17+0100\n&quot;<br /> &quot;PO-Revision-Date: 2007-01-25 19:28+0200\n&quot;<br /> &quot;Last-Translator: Ricardo Mones &lt;ricardo@mones.org&gt;\n&quot;<br /> &quot;Language-Team: Ricardo Mones &lt;ricardo@mones.org&gt;\n&quot;<br /> &quot;MIME-Version: 1.0\n&quot;<br /> &quot;Content-Type: text/plain; charset=iso-8859-1\n&quot;<br /> &quot;Content-Transfer-Encoding: 8bit\n&quot;<br /> &quot;Plural-Forms: nplurals=2; plural=n != 1;\n&quot;&lt;/pre&gt;<br /> |}<br /> Consult the [http://www.gnu.org/software/gettext/manual/html_node/gettext_150.html gettext manual] for the correct Plural-Forms entry for your language.<br /> <br /> Next you will add your translated strings in the &lt;b&gt;msgstr&lt;/b&gt; sections.<br /> Again, an example from es.po:<br /> <br /> {|<br /> |-<br /> &lt;pre&gt;#: src/account.c:372<br /> msgid &quot;&quot;<br /> &quot;Some composing windows are open.\n&quot;<br /> &quot;Please close all the composing windows before editing the accounts.&quot;<br /> msgstr &quot;&quot;<br /> &quot;Hay ventanas de composici&amp;oacute;n abiertas.\n&quot;<br /> &quot;Cierre todas las ventanas de composici&amp;oacute;n antes de editar las cuentas.&quot;<br /> &lt;/pre&gt;<br /> |}<br /> <br /> There are some variations to the format which you should be aware of:<br /> <br /> :: Default hotkeys are indicated by the '_' character:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/account.c:767<br /> msgid &quot; _Set as default account &quot;<br /> msgstr &quot; _Establecer como primaria &quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: The presence of dynamically-generated text is indicated by the 'c-format' line. The 'c format', (%s, %d, etc.), in your &lt;b&gt;msgstr&lt;/b&gt; must match the one used in the &lt;b&gt;msgid&lt;/b&gt;:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/account.c:867<br /> #, c-format<br /> msgid &quot;Copy of %s&quot;<br /> msgstr &quot;Copia de %s&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Some strings have informational data for translators included in the &lt;b&gt;msgid&lt;/b&gt; part, delimited by the '|' character. Their purpose is to indicate the context of the string and they should not appear in your &lt;b&gt;msgstr&lt;/b&gt;:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/prefs_msg_colors.c:228<br /> msgid &quot;Tooltip|Pick color for 2nd level text&quot;<br /> msgstr &quot;Elejir el color para el texto de segundo nivel&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Other strings have the informational data included in the comment header, indicated by 'TRANSLATORS: &amp;hellip;':<br /> :::{|<br /> |-<br /> &lt;pre&gt;#. TRANSLATORS: 'color %d' refers to the filtering/processing<br /> #. rule name and should not be translated<br /> #: src/prefs_msg_colors.c:432 src/prefs_msg_colors.c:464<br /> #, c-format<br /> msgid &quot;Set label for 'color %d'&quot;<br /> msgstr &quot;Establecer la etiqueta para el &amp;laquo;color %d&amp;raquo;&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Some strings contain markup, which should be left in place:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/wizard.c:892<br /> msgid &quot;&lt;span weight=\&quot;bold\&quot;&gt;Your name:&lt;/span&gt;&quot;<br /> msgstr &quot;&lt;span weight=\&quot;bold\&quot;&gt;Su nombre:&lt;/span&gt;&quot;&lt;/pre&gt;<br /> |}<br /> <br /> <br /> '''Checking your translation for errors''' (and completeness)<br /> : /usr/bin/msgfmt -c --statistics is.po<br /> <br /> <br /> '''Building Claws Mail with your new translation included'''<br /> <br /> For this step you will need to be able to build from CVS, so a full set of development tools is required.<br /> <br /> Open the file configure.ac in your text editor and locate the line that begins with 'ALL_LINGUAS=', then add your language to the list of languages.<br /> <br /> Then run ./autogen.sh [OPTIONS], make, make install as usual.<br /> <br /> <br /> '''Updating your translation'''<br /> <br /> When it is time to update your translation, first update your [http://www.claws-mail.org/cvs.php CVS] working directory.<br /> Then do the following:<br /> <br /> : cd po<br /> : rm claws-mail.pot<br /> : make claws-mail.pot<br /> <br /> Next issue the following command to update your po file:<br /> <br /> : /usr/bin/msgmerge --update is.po claws-mail.pot<br /> <br /> Then open your file and locate the strings that need updating. These will have an empty &lt;b&gt;msgstr&lt;/b&gt; or will be marked 'fuzzy':<br /> ::{|<br /> |-<br /> &lt;pre&gt;#: src/mainwindow.c:838 src/messageview.c:332<br /> #, fuzzy<br /> msgid &quot;/_Tools/List _URLs...&quot;<br /> msgstr &quot;/_Herramientas/Exportar _HTML...&quot;&lt;/pre&gt;<br /> |}<br /> <br /> Correct the &lt;b&gt;msgstr&lt;/b&gt; and remove the line '#, fuzzy'.<br /> <br /> Obsolete entries will have been moved to the end of the file and have the following format:<br /> ::{|<br /> |-<br /> &lt;pre&gt;#~ msgid &quot;Really quit?&quot;<br /> #~ msgstr &quot;Salir realmente?&quot;<br /> &lt;/pre&gt;<br /> |}<br /> The obsolete entries can be removed.<br /> <br /> '''Tools'''<br /> <br /> You can use dedicated tools to update your translations, like [http://sourceforge.net/projects/poedit/ poedit] or [http://kbabel.kde.org/ kbabel], which greatly simplify the task.</div> Colin https://www.claws-mail.org/faq/index.php?title=Translator%27s_Information&diff=1620 Translator's Information 2007-02-06T13:01:18Z <p>Colin: /* Information for new translators */</p> <hr /> <div>===The Release Process===<br /> <br /> : The Claws Team sets a date for release, at least 2 weeks in advance.<br /> :: &lt;u&gt;Week One:&lt;/u&gt; CVS feature freeze<br /> ::: No new features are added to CVS, the Team try to fix as many outstanding bugs as possible, test new features thoroughly, and improve any translatable strings as is deemed necessary.<br /> ::: A message announcing the forthcoming release is sent to the [http://www.claws-mail.org/MLs.php translators' mailing list].<br /> :: &lt;u&gt;Week Two:&lt;/u&gt; CVS string freeze<br /> ::: No new features are added and no translatable strings are changed or added.<br /> ::: During this second week, translators should update their local CVS trees and work on updating their translations. For those translators who are unable to build from CVS, up to date POT files are made available for download at http://www.claws-mail.org/i18n/.<br /> ::: Whan a translator has updated his/her translations they should be sent to Paul at [mailto:translations@thewildbeast.co.uk translations@thewildbeast.co.uk] at any time before the week is up. They will then be committed to CVS and included in the release.<br /> :: &lt;u&gt;Week Three:&lt;/u&gt; The release<br /> ::: The release will be made on Day One of Week Three.<br /> <br /> : &lt;b&gt;Bug-Fix Releases&lt;/b&gt;<br /> :: The Claws Team occasionally feels the need to make bug-fix releases. These are normally indicated by an increment of the MICRO_VERSION, (e.g. from version 2.7.0 to 2.7.1). The bug-fix releases contain none of the new features that have been added to CVS since the last major release, and they also do not contain any new translatable strings that may have been added to CVS. Therefore no translation updates are required for these releases and, consequently, the usual process, detailed above, is not initiated.<br /> <br /> ===Information for new translators===<br /> <br /> '''Starting fresh'''<br /> <br /> First grab yourself a copy of the Claws Mail sources, preferably from [http://www.claws-mail.org/cvs.php CVS], and create a claws-mail.pot file:<br /> : ./autogen.sh<br /> : cd po<br /> : make claws-mail.pot<br /> If you are not able to build from CVS, then get a copy of the last released sources from the [http://sourceforge.net/project/showfiles.php?group_id=25528&amp;package_id=147457 SourceForge Claws-Mail files page], which has the claws-mail.pot file included.<br /> <br /> Copy claws-mail.pot to [LANGUAGE ABBREV].po, (replace [LANGUAGE ABBREV] with the correct abbreviation for your language, e.g. 'is' if you are tranlating into Icelandic).<br /> : cp claws-mail.pot is.po<br /> <br /> Open your new po file with your favourite text editor, (or you may prefer to use a translation catalog editor, such as [http://poedit.sourceforge.net poedit] or [http://kbabel.kde.org/ kbabel], for example), and first edit the the header section of your file. You will need to replace the text in UPPERCASE with the correct values. The easiest way to workout how to do this is to compare it to another po file that already exists:<br /> <br /> {| border=&quot;1&quot;<br /> |+ po file header section<br /> ! your new po file !! es.po<br /> |-<br /> | &lt;pre&gt;# SOME DESCRIPTIVE TITLE.<br /> # Copyright (C) YEAR The Claws Mail Team<br /> # FIRST AUTHOR &lt;EMAIL@ADDRESS&gt;, YEAR.<br /> #<br /> #, fuzzy<br /> msgid &quot;&quot;<br /> msgstr &quot;&quot;<br /> &quot;Project-Id-Version: PACKAGE VERSION\n&quot;<br /> &quot;Report-Msgid-Bugs-To: paul@claws-mail.org\n&quot;<br /> &quot;POT-Creation-Date: 2007-01-30 09:03+0000\n&quot;<br /> &quot;PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n&quot;<br /> &quot;Last-Translator: FULL NAME &lt;EMAIL@ADDRESS&gt;\n&quot;<br /> &quot;Language-Team: LANGUAGE &lt;LL@li.org&gt;\n&quot;<br /> &quot;MIME-Version: 1.0\n&quot;<br /> &quot;Content-Type: text/plain; charset=CHARSET\n&quot;<br /> &quot;Content-Transfer-Encoding: 8bit\n&quot;<br /> &quot;Plural-Forms: nplurals=INTEGER; plural=EXPRESSION;\n&quot;&lt;/pre&gt;<br /> | &lt;pre&gt;# Spanish translation of Claws Mail.<br /> # Copyright (C) 2000 Free Software Foundation, Inc.<br /> # Ricardo Mones &lt;ricardo@mones.org&gt;, 2000-2007.<br /> #<br /> msgid &quot;&quot;<br /> msgstr &quot;&quot;<br /> &quot;Project-Id-Version: claws mail\n&quot;<br /> &quot;Report-Msgid-Bugs-To: paul@claws-mail.org\n&quot;<br /> &quot;POT-Creation-Date: 2007-01-25 12:17+0100\n&quot;<br /> &quot;PO-Revision-Date: 2007-01-25 19:28+0200\n&quot;<br /> &quot;Last-Translator: Ricardo Mones &lt;ricardo@mones.org&gt;\n&quot;<br /> &quot;Language-Team: Ricardo Mones &lt;ricardo@mones.org&gt;\n&quot;<br /> &quot;MIME-Version: 1.0\n&quot;<br /> &quot;Content-Type: text/plain; charset=iso-8859-1\n&quot;<br /> &quot;Content-Transfer-Encoding: 8bit\n&quot;<br /> &quot;Plural-Forms: nplurals=2; plural=n != 1;\n&quot;&lt;/pre&gt;<br /> |}<br /> Consult the [http://www.gnu.org/software/gettext/manual/html_node/gettext_150.html gettext manual] for the correct Plural-Forms entry for your language.<br /> <br /> Next you will add your translated strings in the &lt;b&gt;msgstr&lt;/b&gt; sections.<br /> Again, an example from es.po:<br /> <br /> {|<br /> |-<br /> &lt;pre&gt;#: src/account.c:372<br /> msgid &quot;&quot;<br /> &quot;Some composing windows are open.\n&quot;<br /> &quot;Please close all the composing windows before editing the accounts.&quot;<br /> msgstr &quot;&quot;<br /> &quot;Hay ventanas de composici&amp;oacute;n abiertas.\n&quot;<br /> &quot;Cierre todas las ventanas de composici&amp;oacute;n antes de editar las cuentas.&quot;<br /> &lt;/pre&gt;<br /> |}<br /> <br /> There are some variations to the format which you should be aware of:<br /> <br /> :: Default hotkeys are indicated by the '_' character:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/account.c:767<br /> msgid &quot; _Set as default account &quot;<br /> msgstr &quot; _Establecer como primaria &quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: The presence of dynamically-generated text is indicated by the 'c-format' line. The 'c format', (%s, %d, etc.), in your &lt;b&gt;msgstr&lt;/b&gt; must match the one used in the &lt;b&gt;msgid&lt;/b&gt;:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/account.c:867<br /> #, c-format<br /> msgid &quot;Copy of %s&quot;<br /> msgstr &quot;Copia de %s&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Some strings have informational data for translators included in the &lt;b&gt;msgid&lt;/b&gt; part, delimited by the '|' character. Their purpose is to indicate the context of the string and they should not appear in your &lt;b&gt;msgstr&lt;/b&gt;:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/prefs_msg_colors.c:228<br /> msgid &quot;Tooltip|Pick color for 2nd level text&quot;<br /> msgstr &quot;Elejir el color para el texto de segundo nivel&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Other strings have the informational data included in the comment header, indicated by 'TRANSLATORS: &amp;hellip;':<br /> :::{|<br /> |-<br /> &lt;pre&gt;#. TRANSLATORS: 'color %d' refers to the filtering/processing<br /> #. rule name and should not be translated<br /> #: src/prefs_msg_colors.c:432 src/prefs_msg_colors.c:464<br /> #, c-format<br /> msgid &quot;Set label for 'color %d'&quot;<br /> msgstr &quot;Establecer la etiqueta para el &amp;laquo;color %d&amp;raquo;&quot;&lt;/pre&gt;<br /> |}<br /> <br /> :: Some strings contain markup, which should be left in place:<br /> :::{|<br /> |-<br /> &lt;pre&gt;#: src/wizard.c:892<br /> msgid &quot;&lt;span weight=\&quot;bold\&quot;&gt;Your name:&lt;/span&gt;&quot;<br /> msgstr &quot;&lt;span weight=\&quot;bold\&quot;&gt;Su nombre:&lt;/span&gt;&quot;&lt;/pre&gt;<br /> |}<br /> <br /> <br /> '''Checking your translation for errors''' (and completeness)<br /> : /usr/bin/msgfmt -c --statistics is.po<br /> <br /> <br /> '''Building Claws Mail with your new translation included'''<br /> <br /> For this step you will need to be able to build from CVS, so a full set of development tools is required.<br /> <br /> Open the file configure.ac in your text editor and locate the line that begins with 'ALL_LINGUAS=', then add your language to the list of languages.<br /> <br /> Then run ./autogen.sh [OPTIONS], make, make install as usual.<br /> <br /> <br /> '''Updating your translation'''<br /> <br /> When it is time to update your translation, first update your [http://www.claws-mail.org/cvs.php CVS] working directory.<br /> Then do the following:<br /> <br /> : cd po<br /> : rm claws-mail.pot<br /> : make claws-mail.pot<br /> <br /> Next issue the following command to update your po file:<br /> <br /> : /usr/bin/msgmerge --update is.po claws-mail.pot<br /> <br /> Then open your file and locate the strings that need updating. These will have an empty &lt;b&gt;msgstr&lt;/b&gt; or will be marked 'fuzzy':<br /> ::{|<br /> |-<br /> &lt;pre&gt;#: src/mainwindow.c:838 src/messageview.c:332<br /> #, fuzzy<br /> msgid &quot;/_Tools/List _URLs...&quot;<br /> msgstr &quot;/_Herramientas/Exportar _HTML...&quot;&lt;/pre&gt;<br /> |}<br /> <br /> Correct the &lt;b&gt;msgstr&lt;/b&gt; and remove the line '#, fuzzy'.<br /> <br /> Obsolete entries will have been moved to the end of the file and have the following format:<br /> ::{|<br /> |-<br /> &lt;pre&gt;#~ msgid &quot;Really quit?&quot;<br /> #~ msgstr &quot;Salir realmente?&quot;<br /> &lt;/pre&gt;<br /> |}<br /> The obsolete entries can be removed.</div> Colin https://www.claws-mail.org/faq/index.php?title=S/MIME_howto&diff=1601 S/MIME howto 2007-01-11T11:51:09Z <p>Colin: /* Importing S/MIME certificates into gpgsm */</p> <hr /> <div>==Claws Mail &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 /> If this doesn't show a secret key, you may have to import the three certificates from certbundle.pem: separate them to three files (starting with &quot;--- BEGIN CERTIFICATE ---&quot; and ending with &quot;--- END CERTIFICATE ---&quot;), then run &lt;br /&gt; <br /> $ gpgsm --import cert1.pem cert2.pem cert3.pem<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 additional key that is expired and you still want to keep it 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> Colin https://www.claws-mail.org/faq/index.php?title=OctoberMeeting&diff=1600 OctoberMeeting 2006-12-28T14:48:14Z <p>Colin: </p> <hr /> <div>== October Meeting ==<br /> <br /> A meeting among Sylpheed-Claws developers. This meeting has taken place on October 14th-15th in Bristol, UK.<br /> <br /> People present were:<br /> * Colin (from France/Toulouse) - arrival at Bristol on 14 Oct 16:00, leaving on 15 Oct 17:15, at Ramada Plaza Bristol<br /> * Hoa (from France/Paris) - arrival at Bristol on 14 Oct, 11:45, leaving on 15 Oct 17:15, at Ramada Plaza Bristol<br /> * Paul (already in UK) - Ramada Plaza Bristol<br /> * Mones (from Spain/Gijón) - arrival at Bristol on 13 Oct, 19:10 (EJ6032), leaving on 16 Oct 14:10 (EJ6031), at Ramada Plaza Bristol<br /> * wwp (from France/Montpellier) - arrival at Bristol on 14 Oct 16:00, leaving on 15 Oct 17:15 (flight BE1546/BE1547), at Ramada Plaza Bristol<br /> <br /> Photos can be seen [[http://colino.net/photos/index.php?galerie=Bristol%20meeting here]]!</div> Colin https://www.claws-mail.org/faq/index.php?title=DevelopmentModel&diff=1599 DevelopmentModel 2006-12-28T14:45:14Z <p>Colin: </p> <hr /> <div>== Claws Mail Development Model ==<br /> <br /> Stage 0: Release of a new .0 version<br /> <br /> Stage 1: Propose ideas/goals<br /> <br /> Stage 2: Implementation, single developer testing and committing to CVS.<br /> Fix bugs.<br /> <br /> Stage 3: Synchronization and multiple developer (and CVS users) testing, <br /> unless the code is mature enough, go to stage 2 (or 1).<br /> Fix bugs.<br /> From time to time, migrate bugfixes to stable branch.<br /> <br /> Stage 4: Depending on the goals reached, code maturity, moon phase and <br /> other variables, release a ''stable bugfix'', a ''beta'', or a ''rc''.<br /> Fix bugs.<br /> <br /> Stage 5: Fix bugs.<br /> Magic happens here.<br /> <br /> Stage 6: Feature freeze 2 weeks before stage 8).<br /> Fix bugs.<br /> <br /> Stage 7: String freeze 1 week before stage 8).<br /> Fix bugs.<br /> <br /> Stage 8: Release a new shiny .0 version.<br /> Collect donations, get rich.<br /> <br /> Stage 9: Go to stage 0.<br /> <br /> Motto: All of this can change at developers will. Code must flow.</div> Colin https://www.claws-mail.org/faq/index.php?title=DevelopmentModel&diff=1598 DevelopmentModel 2006-12-28T14:44:11Z <p>Colin: /* Claws Mail Development Model */</p> <hr /> <div>== Claws Mail Development Model ==<br /> <br /> Stage 0: Release of a new .0 version<br /> <br /> Stage 1: Propose ideas/goals<br /> <br /> Stage 2: Implementation, single developer testing and committing to CVS.<br /> Fix bugs.<br /> <br /> Stage 3: Synchronization and multiple developer (and CVS users) testing, <br /> unless the code is mature enough, go to stage 2 (or 1).<br /> Fix bugs.<br /> From time to time, migrate bugfixes to stable branch.<br /> <br /> Stage 4: Depending on the goals reached, code maturity, moon phase and <br /> other variables, release a ''stable bugfix'', a ''beta'', or a ''rc''.<br /> Fix bugs.<br /> <br /> Stage 5: Fix bugs.<br /> Magic happens here.<br /> <br /> Stage 6: Feature freeze 2 weeks before stage 8).<br /> Fix bugs.<br /> <br /> Stage 7: String freeze 1 week before stage 8).<br /> Fix bugs.<br /> <br /> Stage 8: Release a new shiny .0 version.<br /> Collect donations, get rich.<br /> <br /> Motto: All of this can change at developers will. Code must flow.</div> Colin https://www.claws-mail.org/faq/index.php?title=DevelopmentModel&diff=1597 DevelopmentModel 2006-12-28T14:43:37Z <p>Colin: </p> <hr /> <div>== Claws Mail Development Model ==<br /> <br /> Stage 0: Release of a new .0 version<br /> <br /> Stage 1: Propose ideas/goals<br /> <br /> Stage 2: Implementation, single developer testing and committing to CVS.<br /> Fix bugs.<br /> <br /> Stage 3: Synchronization and multiple developer (and CVS users) testing, <br /> unless the code is mature enough, go to stage 2 (or 1).<br /> Fix bugs.<br /> From time to time, migrate bugfixes to stable branch.<br /> <br /> Stage 4: Depending on the goals reached, code maturity, moon phase and <br /> other variables, release a ''stable bugfix'', a ''beta'', or a ''rc''.<br /> Fix bugs.<br /> <br /> Stage 5: Fix bugs.<br /> Magic happens here.<br /> <br /> Stage 6: Feature freeze 2 weeks before stage 8).<br /> Fix bugs.<br /> <br /> Stage 7: String freeze 1 week before stage 8).<br /> Fix bugs.<br /> <br /> Stage 8: Release a new shiny .0 version.<br /> <br /> Motto: All of this can change at developers will. Code must flow.</div> Colin https://www.claws-mail.org/faq/index.php?title=DevelopmentModel&diff=1596 DevelopmentModel 2006-12-28T14:39:50Z <p>Colin: </p> <hr /> <div>== Claws Mail Development Model ==<br /> <br /> Stage 0: Release of a new .0 version<br /> <br /> Stage 1: Propose ideas/goals<br /> <br /> Stage 2: Implementation, single developer testing and committing to CVS.<br /> Fix reported and discovered bugs.<br /> <br /> Stage 3: Synchronization and multiple developer (and CVS users) testing, <br /> unless the code is mature enough, go to stage 2 (or 1).<br /> From time to time, migrate bugfixes to stable branch.<br /> <br /> Stage 4: Depending on the goals reached, code maturity, moon phase and <br /> other variables, release a ''stable bugfix'', a ''beta'', or a ''rc''.<br /> <br /> Stage 5: Magic happens here.<br /> <br /> Stage 6: Feature freeze (usually 2 weeks before 8).<br /> <br /> Stage 6b:Fix bugs.<br /> <br /> Stage 7: String freeze (usually 1 week before 8).<br /> <br /> Stage 8: Release a new shiny version.<br /> <br /> Motto: All of this can change at developers will. Code must flow.</div> Colin https://www.claws-mail.org/faq/index.php?title=Plugins&diff=1588 Plugins 2006-12-20T07:20:45Z <p>Colin: /* What plugins are currently available? */</p> <hr /> <div>=== What are plugins? ===<br /> <br /> Plugins are modules loaded (or unloaded) by Claws Mail at runtime. They provide a<br /> way to extend Claws Mail with new capabilities you really need without having all of them wasting memory.<br /> <br /> === Where are plugins located? ===<br /> <br /> Plugins are located in your &lt;tt&gt;$PREFIX/lib/claws-mail/plugins&lt;/tt&gt;. Typical locations are<br /> &lt;tt&gt;/usr/lib/claws-mail/plugins&lt;/tt&gt; if you installed a packaged plugin and &lt;tt&gt;/usr/local/lib/claws-mail/plugins&lt;/tt&gt; if you're installing from source. (plugins have<br /> a suffix of '.so')<br /> <br /> === I have loaded plugin X but how can I configure it? ===<br /> <br /> Plugin configuration options can be found under '/Configuration/Preferences/Plugins/' and/or '/Configuration/[Account Preferences]/Plugins'.<br /> <br /> Some plugins have a separate interface plugin which provides the<br /> configuration pane for the X plugin. If you have loaded plugin &lt;tt&gt;X.so&lt;/tt&gt; typical name<br /> for the configuration plugin will be &lt;tt&gt;X_gtk.so&lt;/tt&gt;, but this is not mandatory, read<br /> plugin's documentation in case of doubt.<br /> <br /> === What plugins are currently available? ===<br /> <br /> The following plugins are included in the Claws Mail release tarballs<br /> <br /> ; Clam AntiVirus<br /> : Enables the scanning of message attachments in mail received from a POP, IMAP or LOCAL account using Clam AntiVirus. It can optionally delete the mail or save it to a designated folder. Preferences can be found in '/Configuration/Preferences/Plugins/Clam AntiVirus'. <br /> : Clam AntiVirus is available from http://clamav.sourceforge.net/<br /> <br /> ; Dillo HTML Viewer<br /> : Enables the viewing of html messages using the Dillo web browser, version 0.7.0 or newer. It uses Dillo's --local option by default for safe browsing. Preferences can be found in '/Configuration/Preferences/Plugins/Dillo Browser'.<br /> : Dillo is available from http://www.dillo.org/<br /> <br /> ; PGP/Core<br /> : Handles core PGP functions and is required by the PGP/Inline and PGP/MIME plugins.<br /> : Uses GnuPG/GPGME, ftp://ftp.gnupg.org/gcrypt/gpgme/<br /> <br /> ; PGP/inline<br /> : Handles inline PGP signed and/or encrypted mails. You can decrypt mails, verify signatures or sign and encrypt your own mails.<br /> : Uses GnuPG/GPGME, ftp://ftp.gnupg.org/gcrypt/gpgme/<br /> <br /> ; PGP/MIME<br /> : Handles PGP/MIME signed and/or encrypted mails. You can decrypt mails, verify signatures or sign and encrypt your own mails.<br /> : Uses GnuPG/GPGME, ftp://ftp.gnupg.org/gcrypt/gpgme/<br /> <br /> ; SpamAssassin<br /> : Enables the scanning of incoming mail received from a POP, IMAP or LOCAL account using SpamAssassin. It can optionally delete mail identified as spam or save it to a designated folder. Preferences can be found in '/Configuration/ Preferences/Plugins/SpamAssassin'. More complete checks than Bogofilter.<br /> : SpamAssassin is available from http://spamassassin.apache.org/<br /> <br /> ; Bogofilter<br /> : Enables the scanning of incoming mail received from a POP, IMAP or LOCAL account using SpamAssassin. It can optionally delete mail identified as spam or save it to a designated folder. Faster than Spamassassin.<br /> : Bogofilter is available from http://www.bogofilter.org/<br /> <br /> ; Trayicon<br /> : Places an icon in the notification area that indicates whether you have any new mail. A tooltip also shows the current new, unread and total number of messages<br /> <br /> The following plugins are included in the Extra Plugins release tarballs<br /> <br /> ; AcpiNotifier<br /> : Enables mail notification via LEDs on some laptops.<br /> <br /> ; GtkHtml2 Viewer<br /> : Enables the viewing of html messages using libgtkhtml2. Fetches attached images, distant images (depending on the preferences), can cache the images. <br /> <br /> ; CacheSaver<br /> : Saves the caches every 60 seconds (or user-defined period).<br /> <br /> ; etPan-Privacy<br /> : Handles signature verification and decryption of encrypted messages in S/MIME, OpenPGP, and ascii-armored PGP formats.<br /> <br /> ; fetchinfo<br /> : Inserts headers containing some download information: UIDL, Claws Mail account name, POP server, user ID and retrieval time.<br /> <br /> ; maildir<br /> : Provides direct support for Maildir++ mailboxes. With this plugin you can share your Maildir++ mailbox with other mailers or IMAP servers.<br /> <br /> ; mailmbox<br /> : Handles mailboxes in mbox format.<br /> <br /> ; perl<br /> : Intended to extend the filtering possibilities of Claws Mail. It provides a Perl interface to Claws Mail's filtering mechanism, allowing the use of full Perl power in email filters.<br /> <br /> ; RSSyl<br /> : Allows you to read your favorite newsfeeds in Claws Mail. RSS 1.0, 2.0 and Atom feeds are currently supported.<br /> <br /> ; SynCE<br /> : Assists in keeping the addressbook of a Windows CE device (Pocket PC/iPAQ, Smartphone etc) in sync with Claws Mail's addressbook, with respect to email addresses.<br /> <br /> ; S/MIME<br /> : Handles S/MIME crypto (signing, encrypting, verifying signatures and decrypting). See [[S/MIME howto]] to get it working.<br /> <br /> ; vCalendar<br /> : Enables vCalendar message handling like that produced by Evolution or Outlook. It provides a personal calendar and public calendar import and export as well as Free/busy import and export to help planning meetings.<br /> <br /> === How do I configure SpamAssassin and the SpamAssassin plugin? ===<br /> <br /> There are many configurations possible, this answer applies when the spamassassin daemon spamd is running on your local computer.<br /> <br /> If you have the dependencies installed, the SpamAssassin plugin will be built automatically when building Claws Mail. When you start Claws Mail the plugin is NOT loaded or enabled. Load the plugins: Configuration|Plugins|Load Plugins, browse to your plugin directory location as described above. Load &lt;tt&gt;spamassassin.so&lt;/tt&gt;. You then need to configure it in: Configuration|Preferences|Plugins|Spamassassin. There are six items to set correctly.<br /> # Transport: For our configuration set this to Localhost. If ever you want to turn spam checking off, set this to Disabled.<br /> # Spamd: This should be set to the IP port number that spamd is listening on, it's normally 783.<br /> # Save Spam: If cleared, this tickbox tells Claws Mail to delete mails that spamassassin thinks are spam.<br /> # Save Folder: If Save Spam is set, this is the folder that Claws Mail will send spam to.<br /> # Maximum Size: Spam is usually small, so it's a waste of resources to spam check very large emails, this sets the size threshold in KBytes.<br /> # Timeout: This is the time that sylpheed will wait while spamd checks each message. The default of 30 seconds is OK for most machines, but slow ones may need this increased.<br /> <br /> Now you need to test the installation. Send yourself some spam. When you receive it, it should be placed into the spam folder that you configured. To check that spamd is being called, put a tail on your sys.log (mine is in &lt;tt&gt;/var/log/sys.log&lt;/tt&gt;, so &lt;tt&gt;tail -f /var/log/sys.log&lt;/tt&gt; works) and see if spamd runs and what it says. If it is not running for every mail message received then check carefully both the SpamAssassin and Claws Mail settings. If it is running, but not detecting spam, then you may need to train the bayesian filter - see SpamAssassin's documentation for that.<br /> <br /> === Does the SpamAssassin plugin change the email headers? ===<br /> <br /> No, it only uses the return value from SpamAssassin, (SPAM/NOT SPAM). To use header changing ability of SpamAssassin you can either configure an [[Actions|Action]] (Report as SPAM: spamassassin -r &lt; %f), or a [[Filtering and Processing of Messages|Filtering]] rule (test &quot;!(spamc -c &lt; %f)&quot;), or setup fetchmail and procmail to filter emails into your Claws Mail mailbox instead of using the plugin.<br /> <br /> === How do I configure gpg-agent and the PGP plugin? ===<br /> <br /> Attempts to use your gpg key to sign/encrypt messages will fail with a 'Signature failed' message without even asking you for your password if:<br /> # Your OS automatically starts the gpg-agent daemon AND<br /> # you only have the CURSES based pinentry program installed AND<br /> # you started sylpheed from a menu or icon<br /> (Note: my Fedora Core 4 workstation install was configured this way).<br /> The solution is to make sure that you have the pinentry-gtk or pinentry-qt programs installed. Claws Mail will then present the pinentry dialog box to get your GPG passphrase.<br /> <br /> You can tell if this is working by the dialog box presented to you for your passphrase. The pinentry dialog is a little uglier than the Claws Mail version, and the window title is 'pinentry'.<br /> <br /> One advantage of using the gpg-agent over Claws Mail password dialog is that the password caching then works with other applications using the gpg-agent (eg the command line when you specify --use-agent).<br /> <br /> Note 2: If it still refuses to work you might want to try the following steps:<br /> * Make sure your ''~/.gnupg/gpg.conf'' contains the line<br /> &lt;code&gt;use-agent&lt;/code&gt;<br /> * Create a file ''~/.gnupg/gpg-agent.conf'' with the following contents:<br /> &lt;code&gt;<br /> &lt;pre&gt;<br /> pinentry-program /usr/bin/pinentry-qt<br /> no-grab<br /> default-cache-ttl 1800<br /> &lt;/pre&gt;<br /> &lt;/code&gt;<br /> * Add the following line to some startup script. (In case of KDE you could use ''~/.kde/env/gpgagent.sh'' - The filename does not matter, the contents of ''~/.kde/env/'' is sourced by startkde)<br /> &lt;pre&gt;eval &quot;$(gpg-agent --daemon)&quot;&lt;/pre&gt;<br /> <br /> <br /> === I love maildir format. Is there a useful replacement in Claws Mail, better than the maildir plugin ? ===<br /> <br /> The maildir plugin works well in Claws Mail. Nevertheless, if you plan to use tons of emails (i.e. X GB of mails), then the maildir plugin is not enough efficient to be usable (tested with 2GB of mails, folders with 30000 mails are long to display).<br /> <br /> The good solution is to use the native format of Claws Mail: the MH format. You have two ways of doing this:<br /> <br /> * Use a local account in MH format: you use the filters of Claws Mail to drop the mails directly on your disk in MH format. Then searching, indexing is very very fast.<br /> <br /> * Use an IMAP account: if doing this way, your emails remains on the IMAP server BUT, when displayed, your mails are downloaded and stored in MH format on your disk too. They are dropped in ~/.claws-mail/imapcache/ and are synchronized with the server (see Synchronize folder in File menu).<br /> <br /> In the two cases, Claws Mail uses the MH format and you can browse your emails with an alternative mail client able to read MH.</div> Colin https://www.claws-mail.org/faq/index.php?title=Ideas&diff=1558 Ideas 2006-10-17T15:20:26Z <p>Colin: /* Address Book */</p> <hr /> <div>== Address Book ==<br /> * improve layout<br /> http://dinh.dyndns.org/~dinh/sylpheed-claws/abook-layout.png<br /> <br /> wwp: I'd propose to (optionally) embed/dock the edit dialog contents into the AB window, as it wouldn't require to enlarge the size of the dialog too much (the layout you're proposing, Hoa, requires much more space on screen, and here it can't fit). See: editing user info [http://wwp.free.fr/tmp/ab-layout-embed-edit1.png], editing group members [http://wwp.free.fr/tmp/ab-layout-embed-edit2.png].<br /> <br /> * use vcard ?<br /> * make it a separate application ? ( I'd rather not (think startup time and fast communication between the two apps), but a --addressbook flag would be nice - Colin)<br /> <br /> == Preferences ==<br /> * in account configuration, hide advanced option so that basic options are all under the same tab<br /> <br /> == Message List ==<br /> * collapsed thread selection<br /> ** when clicking on a collapsed thread (for example, when clicking on the subject) =&gt; expand all the thread<br /> ** when the thread is collapsed and selected, consider all the thread is selected</div> Colin https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=1546 MediaWiki:Sidebar 2006-09-22T11:06:30Z <p>Colin: </p> <hr /> <div>* FAQ navigation<br /> ** mainpage|mainpage<br /> ** General Information|General Information<br /> ** Installation and Configuration|Installation and Configuration<br /> ** Interface|Interface<br /> ** Composing Mails Or News|Composing Mails Or News<br /> ** Filtering and Processing of Messages|Filtering and Processing of Messages<br /> ** Actions|Actions<br /> ** Templates|Templates<br /> ** Plugins|Plugins<br /> ** Using Sylpheed-Claws with other programs|Using Sylpheed-Claws with other programs<br /> &lt;!-- ** portal-url|portal --&gt;<br /> &lt;!-- ** currentevents-url|currentevents --&gt;<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> &lt;!-- ** helppage|help --&gt;<br /> &lt;!-- ** sitesupport-url|sitesupport --&gt;<br /> <br /> * Main Site<br /> ** http://www.sylpheed-claws.net/|What is it?<br /> ** http://www.sylpheed-claws.net/news.php|News<br /> ** http://www.sylpheed-claws.net/features.php|Features<br /> ** http://www.sylpheed-claws.net/screenshots.php|Screenshots<br /> ** http://www.sylpheed-claws.net/documentation.php|User manual<br /> ** http://www.sylpheed-claws.net/downloads.php|Downloads<br /> ** http://www.sylpheed-claws.net/plugins.php|Plugins<br /> ** http://www.sylpheed-claws.net/themes.php|Themes<br /> ** http://www.sylpheed-claws.net/tools.php|Tools<br /> ** http://sourceforge.net/projects/sylpheed-claws/|The Project<br /> ** http://www.sylpheed-claws.net/devel.php|Developers<br /> ** http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi|Bug Tracker<br /> ** http://sourceforge.net/tracker/?group_id=25528&amp;atid=384601|Feature Requests<br /> ** http://www.sylpheed-claws.net/i18n.php|i18n Status<br /> ** http://www.sylpheed-claws.net/cvs.php|Get CVS<br /> ** http://www.sylpheed-claws.net/cvstrak-gtk2.php|CVS Tracker<br /> ** http://cvs.sunsite.dk/viewcvs.cgi/sylpheedclaws/sylpheed-claws/?only_with_tag=gtk2|Browse CVS<br /> ** http://www.sylpheed-claws.net/barometz.php|CVS Stats<br /> ** http://www.sylpheed-claws.net/MLs.php|Contact<br /> ** http://www.sylpheed-claws.net/reviews.php|Reviews<br /> ** http://www.sylpheed-claws.net/theteam.php|The Team<br /> ** http://planet.sylpheed-claws.net/|The Planet<br /> ** http://www.cafepress.com/sylpheed_claws/|The Claws Store</div> Colin https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=1538 MediaWiki:Sidebar 2006-09-20T10:50:48Z <p>Colin: </p> <hr /> <div>* FAQ navigation<br /> ** mainpage|mainpage<br /> ** General Information|General Information<br /> ** Installation and Configuration|Installation and Configuration<br /> ** Interface|Interface<br /> ** Composing Mails Or News|Composing Mails Or News<br /> ** Filtering and Processing of Messages|Filtering and Processing of Messages<br /> ** Actions|Actions<br /> ** Templates|Templates<br /> ** Plugins|Plugins<br /> ** Using Sylpheed-Claws with other programs|Using Sylpheed-Claws with other programs<br /> &lt;!-- ** portal-url|portal --&gt;<br /> &lt;!-- ** currentevents-url|currentevents --&gt;<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> &lt;!-- ** helppage|help --&gt;<br /> &lt;!-- ** sitesupport-url|sitesupport --&gt;<br /> <br /> * Main Site<br /> ** http://www.sylpheed-claws.net/|What is it?<br /> ** http://www.sylpheed-claws.net/news.php|News<br /> ** http://www.sylpheed-claws.net/features.php|Features<br /> ** http://www.sylpheed-claws.net/screenshots.php|Screenshots<br /> ** http://www.sylpheed-claws.net/documentation.php|User manual<br /> ** http://www.sylpheed-claws.net/downloads.php|Downloads<br /> ** http://www.sylpheed-claws.net/plugins.php|Plugins<br /> ** http://www.sylpheed-claws.net/themes.php|Themes<br /> ** http://www.sylpheed-claws.net/tools.php|Tools<br /> ** http://sourceforge.net/projects/sylpheed-claws/|The Project<br /> ** http://www.sylpheed-claws.net/devel.php|Developers<br /> ** http://www.sylpheed-claws.net/MLs.php|Mailing Lists<br /> ** http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi|Bug Tracker<br /> ** http://sourceforge.net/tracker/?group_id=25528&amp;atid=384601|Feature Requests<br /> ** http://www.sylpheed-claws.net/i18n.php|i18n Status<br /> ** http://www.sylpheed-claws.net/cvs.php|Get CVS<br /> ** http://www.sylpheed-claws.net/cvstrak-gtk2.php|CVS Tracker<br /> ** http://cvs.sunsite.dk/viewcvs.cgi/sylpheedclaws/sylpheed-claws/?only_with_tag=gtk2|Browse CVS<br /> ** http://www.sylpheed-claws.net/barometz.php|CVS Stats<br /> ** http://www.sylpheed-claws.net/theteam.php|The Team<br /> ** http://planet.sylpheed-claws.net/|The Planet<br /> ** http://www.cafepress.com/sylpheed_claws/|The Claws Store</div> Colin https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=1537 MediaWiki:Sidebar 2006-09-20T10:48:44Z <p>Colin: </p> <hr /> <div>* FAQ navigation<br /> ** mainpage|mainpage<br /> ** General Information|General Information<br /> ** Installation and Configuration|Installation and Configuration<br /> ** Interface|Interface<br /> ** Composing Mails Or News|Composing Mails Or News<br /> ** Filtering and Processing of Messages|Filtering and Processing of Messages<br /> ** Actions|Actions<br /> ** Templates|Templates<br /> ** Plugins|Plugins<br /> ** Using Sylpheed-Claws with other programs|Using Sylpheed-Claws with other programs<br /> &lt;!-- ** portal-url|portal --&gt;<br /> &lt;!-- ** currentevents-url|currentevents --&gt;<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> &lt;!-- ** helppage|help --&gt;<br /> &lt;!-- ** sitesupport-url|sitesupport --&gt;<br /> <br /> * Main Site<br /> ** http://www.sylpheed-claws.net/|What is it?<br /> ** http://www.sylpheed-claws.net/news.php|News<br /> ** http://www.sylpheed-claws.net/features.php|Features<br /> ** http://www.sylpheed-claws.net/screenshots.php|Screenshots<br /> ** http://www.sylpheed-claws.net/documentation.php|User manual<br /> ** http://www.sylpheed-claws.net/downloads.php|Downloads<br /> ** http://www.sylpheed-claws.net/plugins.php|Plugins<br /> ** http://www.sylpheed-claws.net/themes.php|Themes<br /> ** http://www.sylpheed-claws.net/tools.php|Tools<br /> ** http://sourceforge.net/projects/sylpheed-claws/|The Project<br /> ** http://www.sylpheed-claws.net/devel.php|Developers<br /> ** http://www.sylpheed-claws.net/MLs.php|Mailing Lists<br /> ** http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/index.cgi|Bug Tracker<br /> ** http://sourceforge.net/tracker/?group_id=25528&amp;atid=384601|Feature Requests<br /> ** http://www.sylpheed-claws.net/i18n.php|i18n Status<br /> ** http://www.sylpheed-claws.net/cvs.php|CVS<br /> ** http://www.sylpheed-claws.net/cvstrak-gtk2.php|CVS Tracker<br /> ** http://cvs.sunsite.dk/viewcvs.cgi/sylpheedclaws/sylpheed-claws/?only_with_tag=gtk2|Browse CVS<br /> ** http://www.sylpheed-claws.net/barometz.php|CVS Stats<br /> ** http://www.sylpheed-claws.net/theteam.php|The Team<br /> ** http://planet.sylpheed-claws.net/|The Planet<br /> ** http://www.cafepress.com/sylpheed_claws/|The Claws Store</div> Colin https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=1532 Main Page 2006-09-10T13:07:26Z <p>Colin: /* Sylpheed-Claws FAQ */</p> <hr /> <div>== Sylpheed-Claws FAQ ==<br /> <br /> === General ===<br /> <br /> * [[General Information]]<br /> * [[Installation and Configuration]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Filtering and Processing of Messages]]<br /> * [[Actions]]<br /> * [[Templates]]<br /> * [[Plugins]]<br /> * [[Using Sylpheed-Claws with other programs]]<br /> === Microsoft Windows ===<br /> <br /> * [[Windows: Downloads | Downloads]]<br /> ----<br /> : If you edit the FAQ pages please keep the style. If you change anchor names you might break links from other pages, so don't do that. Invent better names for new anchors. That makes it easier to reference them from other pages. You don't have to add new questions to the end of the list, if you think it's better placed after another question.</div> Colin https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=1531 Main Page 2006-09-10T13:05:25Z <p>Colin: /* Sylpheed-Claws FAQ */</p> <hr /> <div>== Sylpheed-Claws FAQ ==<br /> <br /> === General ===<br /> <br /> * [[General Information]]<br /> * [[Installation and Configuration]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Filtering and Processing of Messages]]<br /> * [[Actions]]<br /> * [[Templates]]<br /> * [[Plugins]]<br /> * [[Using Sylpheed-Claws with other programs]]<br /> === Microsoft Windows ===<br /> <br /> * [[Windows: Downloads | Downloads]]<br /> ----<br /> : If you edit the FAQ pages please keep the style. If you change anchor names you might break links from other pages, so don't do that. Invent better names for new anchors. That makes it easier to reference them from other pages. You don't have to add new questions to the end of the list, if you think it's better placed after another question.</div> Colin https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=1530 Main Page 2006-09-10T13:04:47Z <p>Colin: /* Sylpheed-Claws FAQ */</p> <hr /> <div>== Sylpheed-Claws FAQ ==<br /> <br /> === General ===<br /> <br /> * [[General Information]]<br /> * [[Installation and Configuration]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Filtering and Processing of Messages]]<br /> * [[Actions]]<br /> * [[Templates]]<br /> * [[Plugins]]<br /> * [[Using Sylpheed-Claws with other programs]]<br /> === Microsoft Windows ===<br /> <br /> * [[Windows: Downloads | Downloads]]<br /> ----<br /> : If you edit the FAQ pages please keep the style. If you change anchor names you might break links from other pages, so don't do that. Invent better names for new anchors. That makes it easier to reference them from other pages. You don't have to add new questions to the end of the list, if you think it's better placed after another question.</div> Colin https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=1529 Main Page 2006-09-10T13:03:19Z <p>Colin: /* Sylpheed-Claws FAQ */</p> <hr /> <div>== Sylpheed-Claws FAQ ==<br /> <br /> === General ===<br /> <br /> * [[General Information]]<br /> * [[Installation and Configuration]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Filtering and Processing of Messages]]<br /> * [[Actions]]<br /> * [[Templates]]<br /> * [[Plugins]]<br /> * [[Using Sylpheed-Claws with other programs]]<br /> === Microsoft Windows ===<br /> <br /> * [[Windows: Downloads | Downloads]]<br /> ----<br /> : If you edit the FAQ pages please keep the style. If you change anchor names you might break links from other pages, so don't do that. Invent better names for new anchors. That makes it easier to reference them from other pages. You don't have to add new questions to the end of the list, if you think it's better placed after another question.</div> Colin https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=1528 Main Page 2006-09-10T13:02:20Z <p>Colin: /* Sylpheed-Claws FAQ */</p> <hr /> <div>== Sylpheed-Claws FAQ ==<br /> <br /> === General ===<br /> <br /> * [[General Information]]<br /> * [[Installation and Configuration]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Filtering and Processing of Messages]]<br /> * [[Actions]]<br /> * [[Templates]]<br /> * [[Plugins]]<br /> * [[Using Sylpheed-Claws with other programs]]<br /> === Microsoft Windows ===<br /> <br /> * [[Windows: Downloads | Downloads]]<br /> ----<br /> : If you edit the FAQ pages please keep the style. If you change anchor names you might break links from other pages, so don't do that. Invent better names for new anchors. That makes it easier to reference them from other pages. You don't have to add new questions to the end of the list, if you think it's better placed after another question.</div> Colin https://www.claws-mail.org/faq/index.php?title=Plugins&diff=1525 Plugins 2006-09-09T18:59:37Z <p>Colin: /* What plugins are currently available? */</p> <hr /> <div>=== What are plugins? ===<br /> <br /> Plugins are modules loaded (or unloaded) by Sylpheed-Claws at runtime. They provide a<br /> way to extend Sylpheed-Claws with new capabilities you really need without having all of them wasting memory.<br /> <br /> === Where are plugins located? ===<br /> <br /> Plugins are located in your &lt;tt&gt;$PREFIX/lib/sylpheed-claws/plugins&lt;/tt&gt;. Typical locations are<br /> &lt;tt&gt;/usr/lib/sylpheed-claws/plugins&lt;/tt&gt; if you installed a packaged plugin and &lt;tt&gt;/usr/local/lib/sylpheed-claws/plugins&lt;/tt&gt; if you're installing from source. (plugins have<br /> a suffix of '.so')<br /> <br /> Note that in older versions of Sylpheed-Claws (=&lt; 0.9.11) the directory name was sylpheed and not sylpheed-claws (i.e. &lt;tt&gt;$PREFIX/lib/sylpheed/plugins&lt;/tt&gt;).<br /> <br /> === I have loaded plugin X but how can I configure it? ===<br /> <br /> Plugin configuration options can be found under '/Configuration/Preferences/Plugins/' and/or '/Configuration/[Account Preferences]/Plugins'.<br /> <br /> Some plugins have a separate interface plugin which provides the<br /> configuration pane for the X plugin. If you have loaded plugin &lt;tt&gt;X.so&lt;/tt&gt; typical name<br /> for the configuration plugin will be &lt;tt&gt;X_gtk.so&lt;/tt&gt;, but this is not mandatory, read<br /> plugin's documentation in case of doubt.<br /> <br /> === What plugins are currently available? ===<br /> <br /> The following plugins are included in the Sylpheed-Claws release tarballs<br /> <br /> ; Clam AntiVirus<br /> : Enables the scanning of message attachments in mail received from a POP, IMAP or LOCAL account using Clam AntiVirus. It can optionally delete the mail or save it to a designated folder. Preferences can be found in '/Configuration/Preferences/Plugins/Clam AntiVirus'. <br /> : Clam AntiVirus is available from http://clamav.sourceforge.net/<br /> <br /> ; Dillo HTML Viewer<br /> : Enables the viewing of html messages using the Dillo web browser, version 0.7.0 or newer. It uses Dillo's --local option by default for safe browsing. Preferences can be found in '/Configuration/Preferences/Plugins/Dillo Browser'.<br /> : Dillo is available from http://www.dillo.org/<br /> <br /> ; PGP/Core<br /> : Handles core PGP functions and is required by the PGP/Inline and PGP/MIME plugins.<br /> : Uses GnuPG/GPGME, ftp://ftp.gnupg.org/gcrypt/gpgme/<br /> <br /> ; PGP/inline<br /> : Handles inline PGP signed and/or encrypted mails. You can decrypt mails, verify signatures or sign and encrypt your own mails.<br /> : Uses GnuPG/GPGME, ftp://ftp.gnupg.org/gcrypt/gpgme/<br /> <br /> ; PGP/MIME<br /> : Handles PGP/MIME signed and/or encrypted mails. You can decrypt mails, verify signatures or sign and encrypt your own mails.<br /> : Uses GnuPG/GPGME, ftp://ftp.gnupg.org/gcrypt/gpgme/<br /> <br /> ; SpamAssassin<br /> : Enables the scanning of incoming mail received from a POP, IMAP or LOCAL account using SpamAssassin. It can optionally delete mail identified as spam or save it to a designated folder. Preferences can be found in '/Configuration/ Preferences/Plugins/SpamAssassin'. More complete checks than Bogofilter.<br /> : SpamAssassin is available from http://spamassassin.apache.org/<br /> <br /> ; Bogofilter<br /> : Enables the scanning of incoming mail received from a POP, IMAP or LOCAL account using SpamAssassin. It can optionally delete mail identified as spam or save it to a designated folder. Faster than Spamassassin.<br /> : Bogofilter is available from bogofilter.sourceforge.net/<br /> <br /> ; Trayicon<br /> : Places an icon in the notification area that indicates whether you have any new mail. A tooltip also shows the current new, unread and total number of messages<br /> <br /> The following plugins are included in the External Plugins release tarballs<br /> <br /> ; AcpiNotifier<br /> : Enables mail notification via LEDs on some laptops.<br /> <br /> ; GtkHtml2 Viewer<br /> : Enables the viewing of html messages using libgtkhtml2. Fetches attached images, distant images (depending on the preferences), can cache the images. <br /> <br /> ; CacheSaver<br /> : Saves the caches every 60 seconds (or user-defined period).<br /> <br /> ; etPan-Privacy<br /> : Handles signature verification and decryption of encrypted messages in S/MIME, OpenPGP, and ascii-armored PGP formats.<br /> <br /> ; fetchinfo<br /> : Inserts headers containing some download information: UIDL, Sylpheed-Claws' account name, POP server, user ID and retrieval time.<br /> <br /> ; maildir<br /> : Provides direct support for Maildir++ mailboxes. With this plugin you can share your Maildir++ mailbox with other mailers or IMAP servers.<br /> <br /> ; mailmbox<br /> : Handles mailboxes in mbox format.<br /> <br /> ; perl<br /> : Intended to extend the filtering possibilities of Sylpheed-Claws. It provides a Perl interface to Sylpheed-Claws' filtering mechanism, allowing the use of full Perl power in email filters.<br /> <br /> ; RSSyl<br /> : Allows you to read your favorite newsfeeds in Sylpheed-Claws. RSS 1.0, 2.0 and Atom feeds are currently supported.<br /> <br /> ; SynCE<br /> : Assists in keeping the addressbook of a Windows CE device (Pocket PC/iPAQ, Smartphone etc) in sync with Sylpheed-Claws' addressbook, with respect to email addresses.<br /> <br /> ; vCalendar<br /> : Enables vCalendar message handling like that produced by Evolution or Outlook. It provides a personal calendar and public calendar import and export as well as Free/busy import and export to help planning meetings.<br /> <br /> === How do I configure SpamAssassin and the SpamAssassin plugin? ===<br /> <br /> There are many configurations possible, this answer applies when the spamassassin daemon spamd is running on your local computer.<br /> <br /> If you have the dependencies installed, the SpamAssassin plugin will be built automatically when building Sylpheed-Claws. When you start Sylpheed-Claws the plugin is NOT loaded or enabled. Load the plugins: Configuration|Plugins|Load Plugins, browse to your plugin directory location as described above. Load &lt;tt&gt;spamassassin.so&lt;/tt&gt;. You then need to configure it in: Configuration|Preferences|Plugins|Spamassassin. There are six items to set correctly.<br /> # Transport: For our configuration set this to Localhost. If ever you want to turn spam checking off, set this to Disabled.<br /> # Spamd: This should be set to the IP port number that spamd is listening on, it's normally 783.<br /> # Save Spam: If cleared, this tickbox tells Sylpheed-Claws to delete mails that spamassassin thinks are spam.<br /> # Save Folder: If Save Spam is set, this is the folder that Sylpheed-Claws will send spam to.<br /> # Maximum Size: Spam is usually small, so it's a waste of resources to spam check very large emails, this sets the size threshold in KBytes.<br /> # Timeout: This is the time that sylpheed will wait while spamd checks each message. The default of 30 seconds is OK for most machines, but slow ones may need this increased.<br /> <br /> Now you need to test the installation. Send yourself some spam. When you receive it, it should be placed into the spam folder that you configured. To check that spamd is being called, put a tail on your sys.log (mine is in &lt;tt&gt;/var/log/sys.log&lt;/tt&gt;, so &lt;tt&gt;tail -f /var/log/sys.log&lt;/tt&gt; works) and see if spamd runs and what it says. If it is not running for every mail message received then check carefully both the SpamAssassin and Sylpheed-Claws settings. If it is running, but not detecting spam, then you may need to train the bayesian filter - see SpamAssassin's documentation for that.<br /> <br /> === Does the SpamAssassin plugin change the email headers? ===<br /> <br /> No, it only uses the return value from SpamAssassin, (SPAM/NOT SPAM). To use header changing ability of SpamAssassin you can either configure an [[Actions|Action]] (Report as SPAM: spamassassin -r &lt; %f), or a [[Filtering and Processing of Messages|Filtering]] rule (test &quot;!(spamc -c &lt; %f)&quot;), or setup fetchmail and procmail to filter emails into your Sylpheed-Claws mailbox instead of using the plugin.<br /> <br /> === How do I configure gpg-agent and the PGP plugin? ===<br /> <br /> Attempts to use your gpg key to sign/encrypt messages will fail with a 'Signature failed' message without even asking you for your password if:<br /> # Your OS automatically starts the gpg-agent daemon AND<br /> # you only have the CURSES based pinentry program installed AND<br /> # you started sylpheed from a menu or icon<br /> (Note: my Fedora Core 4 workstation install was configured this way).<br /> The solution is to make sure that you have the pinentry-gtk or pinentry-qt programs installed. Sylpheed-Claws will then present the pinentry dialog box to get your GPG passphrase.<br /> <br /> You can tell if this is working by the dialog box presented to you for your passphrase. The pinentry dialog is a little uglier than the Sylpheed-Claws version, and the window title is 'pinentry'.<br /> <br /> One advantage of using the gpg-agent over Sylpheed-Claws password dialog is that the password caching then works with other applications using the gpg-agent (eg the command line when you specify --use-agent).<br /> <br /> Note 2: If it still refuses to work you might want to try the following steps:<br /> * Make sure your ''~/.gnupg/gpg.conf'' contains the line<br /> &lt;code&gt;use-agent&lt;/code&gt;<br /> * Create a file ''~/.gnupg/gpg-agent.conf'' with the following contents:<br /> &lt;code&gt;<br /> &lt;pre&gt;<br /> pinentry-program /usr/bin/pinentry-qt<br /> no-grab<br /> default-cache-ttl 1800<br /> &lt;/pre&gt;<br /> &lt;/code&gt;<br /> * Add the following line to some startup script. (In case of KDE you could use ''~/.kde/env/gpgagent.sh'' - The filename does not matter, the contents of ''~/.kde/env/'' is sourced by startkde)<br /> &lt;pre&gt;eval &quot;$(gpg-agent --daemon)&quot;&lt;/pre&gt;<br /> <br /> <br /> === I love maildir format. Is there a useful replacement in Sylpheed-Claws, better than the maildir plugin ? ===<br /> <br /> The maildir plugin works well in Sylpheed-Claws. Nevertheless, if you plan to use tons of emails (i.e. X GB of mails), then the maildir plugin is not enough efficient to be usable (tested with 2GB of mails, folders with 30000 mails are long to display).<br /> <br /> The good solution is to use the native format of Sylpheed-Claws: the MH format. You have two ways of doing this:<br /> <br /> * Use a local account in MH format: you use the filters of Sylpheed-Claws to drop the mails directly on your disk in MH format. Then searching, indexing is very very fast.<br /> <br /> * Use an IMAP account: if doing this way, your emails remains on the IMAP server BUT, when displayed, your mails are downloaded and stored in MH format on your disk too. They are dropped in ~/.sylpheed-claws/imapcache/ and are synchronized with the server (see Synchronize folder in File menu).<br /> <br /> In the two cases, Sylpheed-Claws uses the MH format and you can browse your emails with an alternative mail client able to read MH.</div> Colin https://www.claws-mail.org/faq/index.php?title=OctoberMeeting&diff=1513 OctoberMeeting 2006-08-22T11:24:25Z <p>Colin: /* October Meeting */</p> <hr /> <div>== October Meeting ==<br /> <br /> A meeting is planned among Sylpheed-Claws developers. This meeting will take place on October 14th-15th in Bristol, UK.<br /> <br /> People planning to come are:<br /> * Colin (from France/Toulouse) - arrival at Bristol on 14 Oct 16:00, leaving on 15 Oct 17:15<br /> * Hoa (from France/Paris)<br /> * Paul (already in UK)<br /> * Mones (from Spain/Gijón)<br /> <br /> For the hotel, I've found good prices via http://www.city-visitor.com in Ramada Plaza Bristol (in the centre).</div> Colin https://www.claws-mail.org/faq/index.php?title=OctoberMeeting&diff=1512 OctoberMeeting 2006-08-22T11:18:19Z <p>Colin: /* October Meeting */</p> <hr /> <div>== October Meeting ==<br /> <br /> A meeting is planned among Sylpheed-Claws developers. This meeting will take place on October 14th-15th in Bristol, UK.<br /> <br /> People planning to come are:<br /> * Colin (from France/Toulouse) - arrival at Bristol on 14 Oct 16:00, leaving on 15 Oct 17:15<br /> * Hoa (from France/Paris)<br /> * Paul (already in UK)<br /> * Mones (from Spain/Gijón)</div> Colin https://www.claws-mail.org/faq/index.php?title=OctoberMeeting&diff=1506 OctoberMeeting 2006-08-17T09:45:00Z <p>Colin: /* October Meeting */</p> <hr /> <div>== October Meeting ==<br /> <br /> A meeting is planned among Sylpheed-Claws developers. This meeting will take place on October 14th-15th in Bristol, UK.<br /> <br /> People planning to come are:<br /> * Colin (from France/Toulouse)<br /> * Hoa (From France/Paris)<br /> * Paul (already in UK)<br /> * Mones (from Spain/Gijón)</div> Colin https://www.claws-mail.org/faq/index.php?title=OctoberMeeting&diff=1500 OctoberMeeting 2006-08-14T13:01:34Z <p>Colin: </p> <hr /> <div>== October Meeting ==<br /> <br /> A meeting is planned among Sylpheed-Claws developers. This meeting will take place on October 14th-15th in Bristol, UK.<br /> <br /> People planning to come are:<br /> * Colin and Clo</div> Colin