https://www.claws-mail.org/faq/api.php?action=feedcontributions&user=Claws&feedformat=atom Claws Mail FAQ - User contributions [en] 2024-03-19T07:36:55Z User contributions MediaWiki 1.35.7 https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3230 Oauth2 2023-07-17T16:56:33Z <p>Claws: /* Re-authorisation */</p> <hr /> <div>__FORCETOC__<br /> <br /> == Claws Mail Account Settings for OAuth 2.0 ==<br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt; 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> == Setting up OAuth 2.0 for Gmail == <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: If you use more than one Google/Gmail account, make sure you are signed in to Google Cloud Platform with the desired account before creating a project or changing any settings. (It is possible to be signed into multiple accounts; just make sure the browser tab/window you are working in is controlled by the correct account.)<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'In Production'<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, the initial default is 'Testing'. To change this to 'In Production' click on the 'Publish App' button in the 'Publishing status' section of the 'OAuth Consent Screen', and then click on 'Confirm'. This results in the status changing to ‘In Production’ and a new section ‘Verification Status’ showing with a ‘Needs verification’ status, which can be safely ignored. If this doesn't work for some reason, you can switch back to 'Testing' status on the same 'OAuth Consent Screen' page you used before. For this status to work you need to make sure you've added the desired email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). Note that with this status each authorization code will only last for seven days, after which you will be unable to connect and will see authorization errors in the network log. To get a new authorization code, go to the 'OAuth2' page of the Claws Mail settings and repeat the steps for getting an authorization code and completing authorization. (Note that there is no need to get a new client ID or client secret.) (as of 17 Apr 2022)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the Client ID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the Client ID to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> <br /> Select &quot;Edit OAuth Credentials&quot;, then copy the Client Secret to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable (like trusting the app and its developer, as of 8 Jun 2022).<br /> <br /> <br /> <br /> == Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ==<br /> <br /> ===== Step 1: Log in to Azure (Microsoft's cloud service) =====<br /> <br /> * go to https://portal.azure.com and log in<br /> * click on &lt;code&gt;Azure Active Directory&lt;/code&gt;<br /> * click on &lt;code&gt;App registrations&lt;/code&gt; (in the side menu)<br /> <br /> You can use the [https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps direct link] as well.<br /> <br /> ===== Step 2: Register Claws Mail as a new app =====<br /> <br /> * click &lt;code&gt;New registration&lt;/code&gt; (in the top bar)<br /> * enter &lt;code&gt;Name&lt;/code&gt; (e.g. &lt;q&gt;Claws Mail&lt;/q&gt;)<br /> * set &lt;code&gt;Supported account types&lt;/code&gt; to the most premissive option: ''&lt;q&gt;Accounts in any organizational directory and personal Microsoft accounts&lt;/q&gt;''<br /> * set &lt;code&gt;Redirect URI&lt;/code&gt; to ''&lt;q&gt;Public client/native&lt;/q&gt;'' and ''&lt;q&gt;&lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;&lt;/q&gt;''<br /> * click &lt;code&gt;Register&lt;/code&gt; button (at the bottom)<br /> <br /> ===== Step 3: Configure the app =====<br /> <br /> * click on &lt;code&gt;Authentication&lt;/code&gt; (in the side menu)<br /> * make sure the ''&lt;q&gt;&lt;nowiki&gt;https://login.microsoftonline.com/common/oauth2/nativeclient&lt;/nowiki&gt;&lt;/q&gt;'' is checked, and that the redirect URI is there<br /> * click on &lt;code&gt;API permissions&lt;/code&gt; (in the side menu)<br /> * click on &lt;code&gt;Add a permission -&gt; Microsoft Graph -&gt; Delegated permissions&lt;/code&gt; and add the following permissions&lt;br /&gt;(use the search box to filter the list, then tick the box next to a permission name to select it):<br /> - offline_access<br /> - SMTP.Send<br /> - IMAP.AccessAsUser.All<br /> - POP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - User.Read<br /> <br /> * once all permissions are selected, click &lt;code&gt;Add permissions&lt;/code&gt; button (at the bottom)<br /> <br /> ===== Step 4: Configure OAuth2 in Claws Mail =====<br /> <br /> * choose &lt;code&gt;Service Provider&lt;/code&gt; (e.g. &lt;q&gt;MS Exchange&lt;/q&gt;) - ''TODO: explain the difference''<br /> * enter &lt;code&gt;Client ID&lt;/code&gt; (called &lt;code&gt;Application ID&lt;/code&gt; in Azure - shown at app &lt;code&gt;Overview&lt;/code&gt; page)<br /> * leave &lt;code&gt;Secret&lt;/code&gt; field empty<br /> * click &lt;code&gt;Copy link&lt;/code&gt; button and open the request in your browser (you will be asked to authenticate)<br /> * copy the full URL you were redirected to into the &lt;code&gt;Authorisation code&lt;/code&gt; field&lt;br&gt;(it will be something like &lt;nowiki&gt;https://login/microsoftonline.com/common/oauth2/nativeclient#code=0.AQIjdkSjkD...&amp;session_state=e7cd...&lt;/nowiki&gt; )<br /> * click &lt;code&gt;Authorise&lt;/code&gt; button<br /> <br /> <br /> ===== Admin approval =====<br /> <br /> If your email account is managed by a third-party organisation, the attempt to get authorization code will likely fail. You need to '''ask your admin''' to approve the usage of the registered app and grant the API permissions in the organisation tenancy. Sometimes you will see a form where you can enter justification for the approval and request it with a simple button click. However, most of the time, you will need to contact your '''IT support''' on your own. In such a situation, provide a link to the registered app and some basic information about Claws Mail.<br /> <br /> ===== Re-authorisation =====<br /> It is sometimes necessary to re-authorise after a certain amount of time (e.g. a couple of months).<br /> It should be sufficient to click the &lt;code&gt;Authorise&lt;/code&gt; button to reactivate the account.<br /> <br /> ===== References =====<br /> <br /> [https://docs.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth Authenticate an IMAP, POP or SMTP connection using OAuth] - documentation from Microsoft</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3229 Oauth2 2023-07-17T16:56:11Z <p>Claws: /* Re-authorisation */</p> <hr /> <div>__FORCETOC__<br /> <br /> == Claws Mail Account Settings for OAuth 2.0 ==<br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt; 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> == Setting up OAuth 2.0 for Gmail == <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: If you use more than one Google/Gmail account, make sure you are signed in to Google Cloud Platform with the desired account before creating a project or changing any settings. (It is possible to be signed into multiple accounts; just make sure the browser tab/window you are working in is controlled by the correct account.)<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'In Production'<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, the initial default is 'Testing'. To change this to 'In Production' click on the 'Publish App' button in the 'Publishing status' section of the 'OAuth Consent Screen', and then click on 'Confirm'. This results in the status changing to ‘In Production’ and a new section ‘Verification Status’ showing with a ‘Needs verification’ status, which can be safely ignored. If this doesn't work for some reason, you can switch back to 'Testing' status on the same 'OAuth Consent Screen' page you used before. For this status to work you need to make sure you've added the desired email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). Note that with this status each authorization code will only last for seven days, after which you will be unable to connect and will see authorization errors in the network log. To get a new authorization code, go to the 'OAuth2' page of the Claws Mail settings and repeat the steps for getting an authorization code and completing authorization. (Note that there is no need to get a new client ID or client secret.) (as of 17 Apr 2022)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the Client ID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the Client ID to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> <br /> Select &quot;Edit OAuth Credentials&quot;, then copy the Client Secret to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable (like trusting the app and its developer, as of 8 Jun 2022).<br /> <br /> <br /> <br /> == Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ==<br /> <br /> ===== Step 1: Log in to Azure (Microsoft's cloud service) =====<br /> <br /> * go to https://portal.azure.com and log in<br /> * click on &lt;code&gt;Azure Active Directory&lt;/code&gt;<br /> * click on &lt;code&gt;App registrations&lt;/code&gt; (in the side menu)<br /> <br /> You can use the [https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps direct link] as well.<br /> <br /> ===== Step 2: Register Claws Mail as a new app =====<br /> <br /> * click &lt;code&gt;New registration&lt;/code&gt; (in the top bar)<br /> * enter &lt;code&gt;Name&lt;/code&gt; (e.g. &lt;q&gt;Claws Mail&lt;/q&gt;)<br /> * set &lt;code&gt;Supported account types&lt;/code&gt; to the most premissive option: ''&lt;q&gt;Accounts in any organizational directory and personal Microsoft accounts&lt;/q&gt;''<br /> * set &lt;code&gt;Redirect URI&lt;/code&gt; to ''&lt;q&gt;Public client/native&lt;/q&gt;'' and ''&lt;q&gt;&lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;&lt;/q&gt;''<br /> * click &lt;code&gt;Register&lt;/code&gt; button (at the bottom)<br /> <br /> ===== Step 3: Configure the app =====<br /> <br /> * click on &lt;code&gt;Authentication&lt;/code&gt; (in the side menu)<br /> * make sure the ''&lt;q&gt;&lt;nowiki&gt;https://login.microsoftonline.com/common/oauth2/nativeclient&lt;/nowiki&gt;&lt;/q&gt;'' is checked, and that the redirect URI is there<br /> * click on &lt;code&gt;API permissions&lt;/code&gt; (in the side menu)<br /> * click on &lt;code&gt;Add a permission -&gt; Microsoft Graph -&gt; Delegated permissions&lt;/code&gt; and add the following permissions&lt;br /&gt;(use the search box to filter the list, then tick the box next to a permission name to select it):<br /> - offline_access<br /> - SMTP.Send<br /> - IMAP.AccessAsUser.All<br /> - POP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - User.Read<br /> <br /> * once all permissions are selected, click &lt;code&gt;Add permissions&lt;/code&gt; button (at the bottom)<br /> <br /> ===== Step 4: Configure OAuth2 in Claws Mail =====<br /> <br /> * choose &lt;code&gt;Service Provider&lt;/code&gt; (e.g. &lt;q&gt;MS Exchange&lt;/q&gt;) - ''TODO: explain the difference''<br /> * enter &lt;code&gt;Client ID&lt;/code&gt; (called &lt;code&gt;Application ID&lt;/code&gt; in Azure - shown at app &lt;code&gt;Overview&lt;/code&gt; page)<br /> * leave &lt;code&gt;Secret&lt;/code&gt; field empty<br /> * click &lt;code&gt;Copy link&lt;/code&gt; button and open the request in your browser (you will be asked to authenticate)<br /> * copy the full URL you were redirected to into the &lt;code&gt;Authorisation code&lt;/code&gt; field&lt;br&gt;(it will be something like &lt;nowiki&gt;https://login/microsoftonline.com/common/oauth2/nativeclient#code=0.AQIjdkSjkD...&amp;session_state=e7cd...&lt;/nowiki&gt; )<br /> * click &lt;code&gt;Authorise&lt;/code&gt; button<br /> <br /> <br /> ===== Admin approval =====<br /> <br /> If your email account is managed by a third-party organisation, the attempt to get authorization code will likely fail. You need to '''ask your admin''' to approve the usage of the registered app and grant the API permissions in the organisation tenancy. Sometimes you will see a form where you can enter justification for the approval and request it with a simple button click. However, most of the time, you will need to contact your '''IT support''' on your own. In such a situation, provide a link to the registered app and some basic information about Claws Mail.<br /> <br /> ===== Re-authorisation =====<br /> It has been reported that sometimes it is necessary to re-authorise after a certain amount of time (e.g. a couple of months).<br /> It should be sufficient to click the &lt;code&gt;Authorise&lt;/code&gt; button to reactivate the account.<br /> <br /> ===== References =====<br /> <br /> [https://docs.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth Authenticate an IMAP, POP or SMTP connection using OAuth] - documentation from Microsoft</div> Claws https://www.claws-mail.org/faq/index.php?title=Composing_Mails_Or_News&diff=3227 Composing Mails Or News 2023-05-03T08:11:59Z <p>Claws: </p> <hr /> <div>=== When I send mail, the Content-Type header says the mail is in US-ASCII, even when I specified ISO-8859-1? ===<br /> <br /> If no ISO-8859-1 characters (&gt;= 0x80) are used in the message body, Claws Mail will automatically set the charset value in the Content-Type header as US-ASCII.<br /> <br /> (Unless the hidden option 'outgoing_fallback_to_ascii' is set. See the manual for further information: https://www.claws-mail.org/manual/claws-mail-manual.html#adv_hidden)<br /> <br /> === Why does it look like word wrap is not working? ===<br /> <br /> Check your Wrapping settings in '/Configuration/Preferences/Compose/Wrapping'.<br /> <br /> === Why can't I use gvim as external editor? ===<br /> <br /> If one wishes to use gvim as an external editor it's necessary to start it with the no-fork option -f, i.e. in the configuration dialog box you need to enter &quot;gvim -f %s&quot;. If not the editor forks and open up a separate file and when one quits the editor the changes are lost and don't show up in the composer window.<br /> <br /> === Can I quote just parts of the original message when replying? ===<br /> <br /> Yes, select the part in the textview and choose &quot;reply&quot;.<br /> <br /> === Can I reply without quoting at all? ===<br /> <br /> Use the Reply button's dropdown list, (click the arrow on the right of the Reply button), and select 'Reply without quote'. (This also applies to message forwarding.)<br /> <br /> Tip: You can also assign hotkeys to these menu entries.<br /> <br /> === Address completion in composition window ===<br /> <br /> In the address fields, type a few letters, hit &lt;TAB&gt;, select wanted address, and hit &lt;ENTER&gt;.<br /> <br /> === Moving through the fields with the keyboard ===<br /> <br /> Use the TAB key to move forwards through the fields. Use TAB+Shift to move backwards through the fields.<br /> <br /> If Shift-Tab does not work for you for some reason, try Ctrl-Tab or Alt-D to get to the start of the Header tab and then use TAB to move forward, or hit F6 to get to the last address line/field you were on before you moved to the Subject line. (Be careful; if the address was tab-completed, you will not land on the &quot;Clear address&quot; icon on the far right. Don't hit enter!).<br /> <br /> === Why does the spell checker split words containing accents/umlaut/&quot;special characters&quot;? ===<br /> <br /> Because your system is not configured to support non-English text: Claws Mail must be run with one of LC_ALL or LC_CTYPE environment variables set to a value representing your language. For example, if you want to be able to spell check French, you can run Claws Mail with &quot;LC_CTYPE=fr_FR@euro claws-mail&quot;. As French character set is iso-8859-15, you will be able to spell check all other European languages with this setting. You can set LC_CTYPE in one of your startup scripts to avoir setting it at each launch. For example, for an English locale supporting ISO-8859-15, you can use the Irish locale and put &quot;export LC_ALL=en_IE@euro&quot; in $HOME/.bashrc. See the locale man-pages ('man locale') for more information about locales and environment variables. See the man-pages of your shell for the startup scripts used by your shell. I have no idea on how GNOME or KDE desktops set locales.<br /> <br /> === Non-latin1 characters cause problems when corresponding with Yahoo acounts ===<br /> <br /> By non-latin1 (or &quot;special&quot;) characters we mean special characters used by languages other than English.<br /> <br /> There are two problems when corresponding with Yahoo accounts. First, Yahoo will ignore any Content-Type specified for a message and display it with the Latin1/ISO-8859-1 character set. This will make special characters appear strange. You can fix this in your browser by manually changing the character encoding to the proper one. But you have to know which one the message you received uses, or you have to look in the &quot;full headers&quot; at the Content-Type header.<br /> <br /> Secondly, Yahoo places a character set of US-ASCII on all outgoing email, regardless of actual contents. Claws Mail will see the set is US-ASCII and will behave in strange ways. At the very least, you'll see garbled characters instead of the proper characters. Just like in the browser, you can override the Content Type from the View menu. Again, you need to guess what the proper set is.<br /> <br /> This is definitely wrong behaviour from the part of Yahoo and it's not certain whether the Claws Mail developers will agree to implement a workaround.<br /> <br /> === Can I save a message in the Sent folder before encrypting it? ===<br /> <br /> Yes. In the Account Preferences, on the Privacy page, use the option 'Save sent encrypted message as clear text'<br /> <br /> === Can I set up an alias for a list of recipients? ===<br /> <br /> Yes, using the address book <br /> <br /> Open the address book: '/Tools/Address Book'<br /> Right click an address book, create a Group using 'New Group'<br /> Add addresses to that Group.<br /> <br /> In the Compose window use TAB-auto-completion to select and use that Group.</div> Claws https://www.claws-mail.org/faq/index.php?title=Composing_Mails_Or_News&diff=3226 Composing Mails Or News 2023-05-03T08:11:43Z <p>Claws: standardise</p> <hr /> <div>=== When I send mail, the Content-Type header says the mail is in US-ASCII, even when I specified ISO-8859-1? ===<br /> <br /> If no ISO-8859-1 characters (&gt;= 0x80) are used in the message body, Claws Mail will automatically set the charset value in the Content-Type header as US-ASCII.<br /> <br /> (Unless the hidden option 'outgoing_fallback_to_ascii' is set. See the manual for further information: https://www.claws-mail.org/manual/claws-mail-manual.html#adv_hidden)<br /> <br /> === Why does it look like word wrap is not working? ===<br /> <br /> Check your Wrapping settings in '/Configuration/Preferences/Compose/Wrapping'.<br /> <br /> === Why can't I use gvim as external editor? ===<br /> <br /> If one wishes to use gvim as an external editor it's necessary to start it with the no-fork option -f, i.e. in the configuration dialog box you need to enter &quot;gvim -f %s&quot;. If not the editor forks and open up a separate file and when one quits the editor the changes are lost and don't show up in the composer window.<br /> <br /> === Can I quote just parts of the original message when replying? ===<br /> <br /> Yes, select the part in the textview and choose &quot;reply&quot;.<br /> <br /> === Can I reply without quoting at all? ===<br /> <br /> Use the Reply button's dropdown list, (click the arrow on the right of the Reply button), and select 'Reply without quote'. (This also applies to message forwarding.)<br /> <br /> Tip: You can also assign hotkeys to these menu entries.<br /> <br /> === Address completion in composition window ===<br /> <br /> In the address fields, type a few letters, hit &lt;TAB&gt;, select wanted address, and hit &lt;ENTER&gt;.<br /> <br /> === Moving through the fields with the keyboard ===<br /> <br /> Use the TAB key to move forwards through the fields. Use TAB+Shift to move backwards through the fields.<br /> <br /> If Shift-Tab does not work for you for some reason, try Ctrl-Tab or Alt-D to get to the start of the Header tab and then use TAB to move forward, or hit F6 to get to the last address line/field you were on before you moved to the Subject line. (Be careful; if the address was tab-completed, you will not land on the &quot;Clear address&quot; icon on the far right. Don't hit enter!).<br /> <br /> === Why does the spell checker split words containing accents/umlaut/&quot;special characters&quot;? ===<br /> <br /> Because your system is not configured to support non-English text: Claws Mail must be run with one of LC_ALL or LC_CTYPE environment variables set to a value representing your language. For example, if you want to be able to spell check French, you can run Claws Mail with &quot;LC_CTYPE=fr_FR@euro claws-mail&quot;. As French character set is iso-8859-15, you will be able to spell check all other European languages with this setting. You can set LC_CTYPE in one of your startup scripts to avoir setting it at each launch. For example, for an English locale supporting ISO-8859-15, you can use the Irish locale and put &quot;export LC_ALL=en_IE@euro&quot; in $HOME/.bashrc. See the locale man-pages ('man locale') for more information about locales and environment variables. See the man-pages of your shell for the startup scripts used by your shell. I have no idea on how GNOME or KDE desktops set locales.<br /> <br /> === Non-latin1 characters cause problems when corresponding with Yahoo acounts ===<br /> <br /> By non-latin1 (or &quot;special&quot;) characters we mean special characters used by languages other than English.<br /> <br /> There are two problems when corresponding with Yahoo accounts. First, Yahoo will ignore any Content-Type specified for a message and display it with the Latin1/ISO-8859-1 character set. This will make special characters appear strange. You can fix this in your browser by manually changing the character encoding to the proper one. But you have to know which one the message you received uses, or you have to look in the &quot;full headers&quot; at the Content-Type header.<br /> <br /> Secondly, Yahoo places a character set of US-ASCII on all outgoing email, regardless of actual contents. Claws Mail will see the set is US-ASCII and will behave in strange ways. At the very least, you'll see garbled characters instead of the proper characters. Just like in the browser, you can override the Content Type from the View menu. Again, you need to guess what the proper set is.<br /> <br /> This is definitely wrong behaviour from the part of Yahoo and it's not certain whether the Claws Mail developers will agree to implement a workaround.<br /> <br /> === Can I save a message in the Sent folder before encrypting it? ===<br /> <br /> Yes. In the Account Preferences, on the Privacy page, use the option 'Save sent encrypted message as clear text'<br /> <br /> === Can I set up an alias for a list of recipients ? ===<br /> <br /> Yes, using the address book <br /> <br /> Open the address book: '/Tools/Address Book'<br /> Right click an address book, create a Group using 'New Group'<br /> Add addresses to that Group.<br /> <br /> In the Compose window use TAB-auto-completion to select and use that Group.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3223 Oauth2 2022-07-24T18:05:47Z <p>Claws: </p> <hr /> <div>__FORCETOC__<br /> <br /> == Claws Mail Account Settings for OAuth 2.0 ==<br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt; 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> == Setting up OAuth 2.0 for Gmail == <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: If you use more than one Google/Gmail account, make sure you are signed in to Google Cloud Platform with the desired account before creating a project or changing any settings. (It is possible to be signed into multiple accounts; just make sure the browser tab/window you are working in is controlled by the correct account.)<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'In Production'<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, the initial default is 'Testing'. To change this to 'In Production' click on the 'Publish App' button in the 'Publishing status' section of the 'OAuth Consent Screen', and then click on 'Confirm'. This results in the status changing to ‘In Production’ and a new section ‘Verification Status’ showing with a ‘Needs verification’ status, which can be safely ignored. If this doesn't work for some reason, you can switch back to 'Testing' status on the same 'OAuth Consent Screen' page you used before. For this status to work you need to make sure you've added the desired email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). Note that with this status each authorization code will only last for seven days, after which you will be unable to connect and will see authorization errors in the network log. To get a new authorization code, go to the 'OAuth2' page of the Claws Mail settings and repeat the steps for getting an authorization code and completing authorization. (Note that there is no need to get a new client ID or client secret.) (as of 17 Apr 2022)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the Client ID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the Client ID to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> <br /> Select &quot;Edit OAuth Credentials&quot;, then copy the Client Secret to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable (like trusting the app and its developer, as of 8 Jun 2022).<br /> <br /> <br /> <br /> == Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ==<br /> <br /> ===== Step 1: Log in to Azure (Microsoft's cloud service) =====<br /> <br /> * go to https://portal.azure.com and log in<br /> * click on &lt;code&gt;Azure Active Directory&lt;/code&gt;<br /> * click on &lt;code&gt;App registrations&lt;/code&gt; (in the side menu)<br /> <br /> You can use the [https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps direct link] as well.<br /> <br /> ===== Step 2: Register Claws Mail as a new app =====<br /> <br /> * click &lt;code&gt;New registration&lt;/code&gt; (in the top bar)<br /> * enter &lt;code&gt;Name&lt;/code&gt; (e.g. &lt;q&gt;Claws Mail&lt;/q&gt;)<br /> * set &lt;code&gt;Supported account types&lt;/code&gt; to the most premissive option: ''&lt;q&gt;Accounts in any organizational directory and personal Microsoft accounts&lt;/q&gt;''<br /> * set &lt;code&gt;Redirect URI&lt;/code&gt; to ''&lt;q&gt;Public client/native&lt;/q&gt;'' and ''&lt;q&gt;&lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;&lt;/q&gt;''<br /> * click &lt;code&gt;Register&lt;/code&gt; button (at the bottom)<br /> <br /> ===== Step 3: Configure the app =====<br /> <br /> * click on &lt;code&gt;Authentication&lt;/code&gt; (in the side menu)<br /> * make sure the ''&lt;q&gt;&lt;nowiki&gt;https://login.microsoftonline.com/common/oauth2/nativeclient&lt;/nowiki&gt;&lt;/q&gt;'' is checked, and that the redirect URI is there<br /> * click on &lt;code&gt;API permissions&lt;/code&gt; (in the side menu)<br /> * click on &lt;code&gt;Add a permission -&gt; Microsoft Graph -&gt; Delegated permissions&lt;/code&gt; and add the following permissions&lt;br /&gt;(use the search box to filter the list, then tick the box next to a permission name to select it):<br /> - offline_access<br /> - SMTP.Send<br /> - IMAP.AccessAsUser.All<br /> - POP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - User.Read<br /> <br /> * once all permissions are selected, click &lt;code&gt;Add permissions&lt;/code&gt; button (at the bottom)<br /> <br /> ===== Step 4: Configure OAuth2 in Claws Mail =====<br /> <br /> * choose &lt;code&gt;Service Provider&lt;/code&gt; (e.g. &lt;q&gt;MS Exchange&lt;/q&gt;) - ''TODO: explain the difference''<br /> * enter &lt;code&gt;Client ID&lt;/code&gt; (called &lt;code&gt;Application ID&lt;/code&gt; in Azure - shown at app &lt;code&gt;Overview&lt;/code&gt; page)<br /> * leave &lt;code&gt;Secret&lt;/code&gt; field empty<br /> * click &lt;code&gt;Copy link&lt;/code&gt; button and open the request in your browser (you will be asked to authenticate)<br /> * copy the full URL you were redirected to into the &lt;code&gt;Authorisation code&lt;/code&gt; field&lt;br&gt;(it will be something like &lt;nowiki&gt;https://login/microsoftonline.com/common/oauth2/nativeclient#code=0.AQIjdkSjkD...&amp;session_state=e7cd...&lt;/nowiki&gt; )<br /> * click &lt;code&gt;Authorise&lt;/code&gt; button<br /> <br /> <br /> ===== Admin approval =====<br /> <br /> If your email account is managed by a third-party organisation, the attempt to get authorization code will likely fail. You need to '''ask your admin''' to approve the usage of the registered app and grant the API permissions in the organisation tenancy. Sometimes you will see a form where you can enter justification for the approval and request it with a simple button click. However, most of the time, you will need to contact your '''IT support''' on your own. In such a situation, provide a link to the registered app and some basic information about Claws Mail.<br /> <br /> ===== References =====<br /> <br /> [https://docs.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth Authenticate an IMAP, POP or SMTP connection using OAuth] - documentation from Microsoft</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3220 Oauth2 2022-07-14T15:38:00Z <p>Claws: easier to see section headings</p> <hr /> <div>__FORCETOC__<br /> <br /> == Claws Mail Account Settings for OAuth 2.0 ==<br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt; 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> == Setting up OAuth 2.0 for Gmail == <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: If you use more than one Google/Gmail account, make sure you are signed in to Google Cloud Platform with the desired account before creating a project or changing any settings. (It is possible to be signed into multiple accounts; just make sure the browser tab/window you are working in is controlled by the correct account.)<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'In Production'<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, the initial default is 'Testing'. To change this to 'In Production' click on the 'Publish App' button in the 'Publishing status' section of the 'OAuth Consent Screen', and then click on 'Confirm'. This results in the status changing to ‘In Production’ and a new section ‘Verification Status’ showing with a ‘Needs verification’ status, which can be safely ignored. If this doesn't work for some reason, you can switch back to 'Testing' status on the same 'OAuth Consent Screen' page you used before. For this status to work you need to make sure you've added the desired email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). Note that with this status each authorization code will only last for seven days, after which you will be unable to connect and will see authorization errors in the network log. To get a new authorization code, go to the 'OAuth2' page of the Claws Mail settings and repeat the steps for getting an authorization code and completing authorization. (Note that there is no need to get a new client ID or client secret.) (as of 17 Apr 2022)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the Client ID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the Client ID to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> <br /> Select &quot;Edit OAuth Credentials&quot;, then copy the Client Secret to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable (like trusting the app and its developer, as of 8 Jun 2022).<br /> <br /> <br /> <br /> == Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ==<br /> <br /> '''Step 1: Get into 'Azure', Microsoft's cloud computing service.'''<br /> <br /> Go to https://portal.azure.com , making sure you are signed in with the Microsoft account you are wanting to set up. Go to 'Azure Active Directory' (click on the 'View' button under 'Manage Azure Active Directory') and then the 'App registrations' page (via the link in the side-pane). Here is a direct link to this page: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps .<br /> <br /> <br /> '''Step 2: Register Claws Mail as a new app.'''<br /> <br /> Click on 'New Registration' to get to the 'Register an application page', then adjust the settings as follows:<br /> &lt;pre&gt;<br /> Display name: Anything you choose.<br /> <br /> Supported account types - set to &quot;Accounts in any organizational directory… and personal Microsoft accounts…&quot; (Note: This will be shown on the app’s ‘Authentication’ page.) (It will also be represented on the app's ‘Overview’ page as &quot;All Microsoft account users&quot;.)<br /> <br /> Select a platform: &quot;Public client/native...&quot;<br /> <br /> Redirect URI: &lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> Once you've adjusted settings as desired, click on the 'Register' button.<br /> <br /> (Note: Creating a new registration will result in the auto-generation of an application (client) ID, an object ID, and a directory (tenant) ID, all of which will then be visible on the app’s ‘Overview’ page.)<br /> <br /> <br /> '''Step 3: Configure the Claws Mail app.'''<br /> <br /> The various configuration pages can be accessed via the links in the side-pane. Nothing needs to be changed on the following pages:<br /> &lt;pre&gt;<br /> Quickstart<br /> Integration assistant<br /> Branding<br /> Certificates &amp; secrets<br /> Token configuration<br /> Expose an API<br /> Owners<br /> Manifest<br /> &lt;/pre&gt;<br /> <br /> Check/adjust settings on the following pages:<br /> &lt;pre&gt;<br /> 'Authentication' - Confirm that the ‘redirect URI’ you set during registration has its box checked. You can also add/delete redirect URI’s on this page, as necessary.<br /> <br /> 'API permissions' - Click on 'Add a permission' &gt; 'Microsoft Graph' &gt; 'Delegated permissions', and add the following permissions. First, select each permission by typing some/all of its name in the search/filter box to narrow the results, expanding categories as needed, and clicking on the box beside the permission so that a check mark shows. Once you've selected all the permissions, click on the 'Add permissions' button to add them all at the same time. Any permissions that have been successfully added will now show up in the 'Configured permissions' list on the 'API permissions' page.<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> - User.Read<br /> &lt;/pre&gt;<br /> Once the Claws Mail app is configured, the Client ID (also called Application ID) can be copied to Claws Mail's corresponding Client ID field. (The Client ID is shown on the app's 'Overview' page in Azure.) No Client Secret is needed, so Claws Mail's Client Secret field should be empty.<br /> <br /> Note: If you are using an email account managed by a third-party organization using Microsoft’s email systems, then when you attempt to get an authorization code you may see a screen that says something like ‘Approval Required’ // ‘This app requires your admin’s approval...’. This is likely because Claws Mail is not ‘published’ by a ‘verified publisher’ or because for some other reason the organization has decided to limit the apps to which users can give permissions. There may be a field where you can enter justification for requesting this app, after which you can click on ‘Request approval’. Then you may see a notice that says the request has been sent to your ‘admin’ and that you’ll receive an email in regards to whether it’s been approved or not. You may want to reach out to your email administrator to see if they got the request, to let them know it is a legitimate request from you, and perhaps provide a link to the Claws Mail website and/or other information about the ‘app’ for which you are wanting them to give you consent permissions. (The above details may be different depending on how the organization has configured their 'user consent' settings.) Ultimately it will be up to the organization (rather than Microsoft or yourself) as to whether you will be able to give Claws the access it needs.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3219 Oauth2 2022-07-07T07:48:24Z <p>Claws: Undo revision 3216 by Paulh177 (talk)</p> <hr /> <div>__FORCETOC__<br /> <br /> === Claws Mail Account Settings for OAuth 2.0 === <br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt; 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> === Setting up OAuth 2.0 for Gmail === <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: If you use more than one Google/Gmail account, make sure you are signed in to Google Cloud Platform with the desired account before creating a project or changing any settings. (It is possible to be signed into multiple accounts; just make sure the browser tab/window you are working in is controlled by the correct account.)<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'In Production'<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, the initial default is 'Testing'. To change this to 'In Production' click on the 'Publish App' button in the 'Publishing status' section of the 'OAuth Consent Screen', and then click on 'Confirm'. This results in the status changing to ‘In Production’ and a new section ‘Verification Status’ showing with a ‘Needs verification’ status, which can be safely ignored. If this doesn't work for some reason, you can switch back to 'Testing' status on the same 'OAuth Consent Screen' page you used before. For this status to work you need to make sure you've added the desired email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). Note that with this status each authorization code will only last for seven days, after which you will be unable to connect and will see authorization errors in the network log. To get a new authorization code, go to the 'OAuth2' page of the Claws Mail settings and repeat the steps for getting an authorization code and completing authorization. (Note that there is no need to get a new client ID or client secret.) (as of 17 Apr 2022)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the Client ID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the Client ID to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> <br /> Select &quot;Edit OAuth Credentials&quot;, then copy the Client Secret to the corresponding field on Claws Mail's account settings' 'Oauth2' page.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable (like trusting the app and its developer, as of 8 Jun 2022).<br /> <br /> <br /> <br /> === Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ===<br /> <br /> '''Step 1: Get into 'Azure', Microsoft's cloud computing service.'''<br /> <br /> Go to https://portal.azure.com , making sure you are signed in with the Microsoft account you are wanting to set up. Go to 'Azure Active Directory' (click on the 'View' button under 'Manage Azure Active Directory') and then the 'App registrations' page (via the link in the side-pane). Here is a direct link to this page: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps .<br /> <br /> <br /> '''Step 2: Register Claws Mail as a new app.'''<br /> <br /> Click on 'New Registration' to get to the 'Register an application page', then adjust the settings as follows:<br /> &lt;pre&gt;<br /> Display name: Anything you choose.<br /> <br /> Supported account types - set to &quot;Accounts in any organizational directory… and personal Microsoft accounts…&quot; (Note: This will be shown on the app’s ‘Authentication’ page.) (It will also be represented on the app's ‘Overview’ page as &quot;All Microsoft account users&quot;.)<br /> <br /> Select a platform: &quot;Public client/native...&quot;<br /> <br /> Redirect URI: &lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> Once you've adjusted settings as desired, click on the 'Register' button.<br /> <br /> (Note: Creating a new registration will result in the auto-generation of an application (client) ID, an object ID, and a directory (tenant) ID, all of which will then be visible on the app’s ‘Overview’ page.)<br /> <br /> <br /> '''Step 3: Configure the Claws Mail app.'''<br /> <br /> The various configuration pages can be accessed via the links in the side-pane. Nothing needs to be changed on the following pages:<br /> &lt;pre&gt;<br /> Quickstart<br /> Integration assistant<br /> Branding<br /> Certificates &amp; secrets<br /> Token configuration<br /> Expose an API<br /> Owners<br /> Manifest<br /> &lt;/pre&gt;<br /> <br /> Check/adjust settings on the following pages:<br /> &lt;pre&gt;<br /> 'Authentication' - Confirm that the ‘redirect URI’ you set during registration has its box checked. You can also add/delete redirect URI’s on this page, as necessary.<br /> <br /> 'API permissions' - Click on 'Add a permission' &gt; 'Microsoft Graph' &gt; 'Delegated permissions', and add the following permissions. First, select each permission by typing some/all of its name in the search/filter box to narrow the results, expanding categories as needed, and clicking on the box beside the permission so that a check mark shows. Once you've selected all the permissions, click on the 'Add permissions' button to add them all at the same time. Any permissions that have been successfully added will now show up in the 'Configured permissions' list on the 'API permissions' page.<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> - User.Read<br /> &lt;/pre&gt;<br /> Once the Claws Mail app is configured, the Client ID (also called Application ID) can be copied to Claws Mail's corresponding Client ID field. (The Client ID is shown on the app's 'Overview' page in Azure.) No Client Secret is needed, so Claws Mail's Client Secret field should be empty.<br /> <br /> Note: If you are using an email account managed by a third-party organization using Microsoft’s email systems, then when you attempt to get an authorization code you may see a screen that says something like ‘Approval Required’ // ‘This app requires your admin’s approval...’. This is likely because Claws Mail is not ‘published’ by a ‘verified publisher’ or because for some other reason the organization has decided to limit the apps to which users can give permissions. There may be a field where you can enter justification for requesting this app, after which you can click on ‘Request approval’. Then you may see a notice that says the request has been sent to your ‘admin’ and that you’ll receive an email in regards to whether it’s been approved or not. You may want to reach out to your email administrator to see if they got the request, to let them know it is a legitimate request from you, and perhaps provide a link to the Claws Mail website and/or other information about the ‘app’ for which you are wanting them to give you consent permissions. (The above details may be different depending on how the organization has configured their 'user consent' settings.) Ultimately it will be up to the organization (rather than Microsoft or yourself) as to whether you will be able to give Claws the access it needs.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3218 Oauth2 2022-07-07T07:47:49Z <p>Claws: Reverted edits by Claws (talk) to last revision by Paulh177</p> <hr /> <div>__FORCETOC__<br /> <br /> <br /> == Claws Mail Account Settings for OAuth 2.0 ==<br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt;<br /> 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> == Setting up OAuth 2.0 for Gmail ==<br /> <br /> '''There are some instructions here:'''https://support.google.com/googleapi/answer/6158849''' but the instructions below may be more helpful.'''<br /> <br /> <br /> === Preamble ===<br /> In order to use Gmail in Claws, the end user has to obtain their own OAuth2 credentials from Google to make it work.<br /> <br /> Getting these can appear quite complicated for the regular non-technical end user, but provided you follow the workflow carefully, it shouldn't take too long.<br /> <br /> Almost everything has to be done in the Google Cloud console, which is designed for software developers to use, so it can appear confusing to a non-technical end-user, and it can be easy to get lost in the multitude of screens and menus.<br /> <br /> <br /> Google also have an unfortunate habit of rejigging their interfaces so that today's workflow might not be tomorrow's.<br /> <br /> However the outline below worked in June 2022.<br /> <br /> The critical thing is to follow the order of activities exactly. Trying to skip ahead or doing something incompletely &amp; hoping to return later can cause problems.<br /> <br /> <br /> The sequence of operations is:<br /> <br /> # Setup Google Cloud Project<br /> # Obtain credentials for your project<br /> # Enter credentials into ClawsMail<br /> # Authorise ClawsMail with Google<br /> <br /> <br /> This sequence will have to be followed for '''each''' Gmail account that you want to use with ClawsMail.<br /> <br /> <br /> === Setting up your Google Cloud Project ===<br /> <br /> You need to get into the Google Cloud Console, so go to '''https://console.cloud.google.com/projectselector2/apis/dashboard?supportedpurview=project'''<br /> <br /> If you are already signed into the Google (Gmail) account that you want to set up OAuth2 for, you won't need to sign in.<br /> <br /> If you aren't, sign in with the Google (Gmail) account for which you want to set up OAuth2.<br /> <br /> Once signed in, you need to create a &quot;Project&quot; so that you can generate credentials.<br /> <br /> So, click on &quot;Create Project&quot; on the right hand side of the screen.<br /> <br /> (You can call it whatever you like, but if you're going to create more than one project &amp; set of credentials, it might be helpful to use names that relate uniquely to each email address you are using.)<br /> <br /> '''NB''' If you get into trouble or make mistakes that you can't rectify, you can simply delete the project &amp; start again.<br /> <br /> <br /> '''FIRST'''<br /> <br /> Select &quot;Oauth Consent Screen&quot;<br /> <br /> (you won't be able to create any credentials until you have done this step)<br /> <br /> &lt;pre&gt;For &quot;type&quot;, select &quot;External&quot; &amp; click &quot;CREATE&quot;.<br /> <br /> You're now in &quot;Edit app registration&quot;<br /> <br /> For &quot;App name&quot; you can enter whatever you like.<br /> (Again, it might be helpful to use names related to the email address you're doing this for.)<br /> <br /> Ignore &quot;App domain&quot; fields, they can be left blank.<br /> <br /> In the &quot;User Support Email&quot; and &quot;Developer Contact Email&quot; fields enter the Gmail address for which you want to set up OAuth2 credentials.<br /> <br /> Click &quot;Save and Continue&quot;<br /> &lt;/pre&gt;<br /> <br /> <br /> '''NEXT'''<br /> <br /> Select &quot;add or remove scopes&quot;<br /> You need to select &quot;Gmail&quot; from the list (table) that opens on the RHS of the screen, but it might not appear.<br /> <br /> &lt;blockquote&gt;<br /> If it doesn't appear, you will need to paste<br /> &quot;https://mail.google.com/&quot;<br /> into the &quot;manually add scopes&quot; box,<br /> <br /> then click &quot;update table&quot;,<br /> <br /> then click &quot;update&quot;.<br /> &lt;/blockquote&gt;<br /> <br /> You should now see &quot;GMAIL Scopes&quot; under &quot;Your restricted scopes&quot;<br /> <br /> Click &quot;save and continue&quot;<br /> <br /> <br /> '''NEXT'''<br /> <br /> Click on '''&quot;+ Add users&quot;'''. If you don't add yourself as a test user at this point the authorisation process that comes later will fail.<br /> <br /> Once again, enter the email address that you want to access with Claws Mail.<br /> <br /> Then click &quot;back to dashboard&quot;, which should take you to the &quot;OAuth Consent screen&quot; page.<br /> <br /> On this page you should see a heading of '''&quot;Publishing status&quot;''', under which it should now say '''&quot;Testing&quot;'''.<br /> <br /> <br /> '''Do not be tempted to click &quot;Publish App&quot; at this point.'''<br /> <br /> <br /> '''NEXT'''<br /> <br /> You can now create the credentials you need to authorise ClawsMail to use your Gmail account.<br /> <br /> &lt;pre&gt;<br /> Click &quot;Credentials&quot;, then &quot;create credentials&quot;, and then &quot;OAuth client ID&quot;.<br /> <br /> For &quot;Application Type&quot; select &quot;Desktop app&quot;.<br /> <br /> You can either accept the default name offered, or, as before, enter something relating to the email account for which you're doing this.<br /> <br /> Then click &quot;Create&quot;<br /> <br /> &lt;/pre&gt;<br /> <br /> <br /> A popup box will show you the Client ID &amp; Client Secret.<br /> <br /> You need these to enter into ClawsMail, so copy them.<br /> <br /> There is also an option to download them as a JSON file.<br /> <br /> (This is convenient for the more technically minded user, but perhaps a bit insecure. If you do this, keep it somewhere safe)<br /> <br /> <br /> === Authorising Clawsmail with Google/Gmail ===<br /> '''NEARLY FINALLY'''<br /> <br /> Now that you have your credentials, you have to enter them into ClawsMail itself for your Gmail account.<br /> <br /> Remember that you must also set the &quot;Send&quot; and &quot;Receive&quot; authentication method to &quot;OAuth2&quot; for your account in those screens.<br /> <br /> You need to go to Configuration/Edit accounts &amp; select and edit the account for which you've created the credentials.<br /> <br /> &lt;pre&gt;<br /> Select &quot;Oauth2&quot;.<br /> <br /> From the dropdown &quot;Select OAuth2 Service Email Provider&quot;, select &quot;Google/Gmail&quot;<br /> <br /> You now need to copy into the &quot;Client ID&quot; and &quot;Client Secret&quot; boxes the credentials you copied in the previous step.<br /> <br /> Now click &quot;Open default browser with request&quot;.<br /> <br /> Gmail should launch in your browser, taking you to login screens with multiple warnings about how unsafe what you are doing is.<br /> <br /> Don't &quot;go back to safety&quot;, because what you're doing is safe.<br /> <br /> Eventually you will get a screen offering you an authorisation code.<br /> <br /> Copy this.<br /> &lt;/pre&gt;<br /> <br /> <br /> '''FINAL STEP'''<br /> <br /> Now go back to the ClawsMail OAuth2 page that you launched the browser page from.<br /> <br /> Paste in the code you copied from the Gmail screen in the previous step into the &quot;Authorisation code&quot; box, then click &quot;Authorise&quot; and &quot;Apply&quot;.<br /> <br /> <br /> Now see if you can fetch email from Gmail in Clawsmail.<br /> <br /> <br /> === Epilogue ===<br /> <br /> Unfortunately, because neither your project nor ClawsMail are verified apps as far as Google is concerned, this is not quite the end of the story.<br /> <br /> From now on, every 7 days after the initial authorisation, it will revert to unauthorised &amp; ClawsMail won't be able to access you Gmail account.<br /> <br /> Fortunately, you don't have to go through the whole process again, but just the final step:<br /> <br /> Go to ClawsMail OAuth2 page, launch browser, get an authorisation code &amp; then paste it back into the Authorisation code box &amp; click authorise.<br /> <br /> <br /> <br /> == Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ==<br /> <br /> '''Step 1: Get into 'Azure', Microsoft's cloud computing service.'''<br /> <br /> Go to https://portal.azure.com , making sure you are signed in with the Microsoft account you are wanting to set up. Go to 'Azure Active Directory' (click on the 'View' button under 'Manage Azure Active Directory') and then the 'App registrations' page (via the link in the side-pane). Here is a direct link to this page: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps .<br /> <br /> <br /> '''Step 2: Register Claws Mail as a new app.'''<br /> <br /> Click on 'New Registration' to get to the 'Register an application page', then adjust the settings as follows:<br /> &lt;pre&gt;<br /> Display name: Anything you choose.<br /> <br /> Supported account types - set to &quot;Accounts in any organizational directory… and personal Microsoft accounts…&quot; (Note: This will be shown on the app’s ‘Authentication’ page.) (It will also be represented on the app's ‘Overview’ page as &quot;All Microsoft account users&quot;.)<br /> <br /> Select a platform: &quot;Public client/native...&quot;<br /> <br /> Redirect URI: &lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> Once you've adjusted settings as desired, click on the 'Register' button.<br /> <br /> (Note: Creating a new registration will result in the auto-generation of an application (client) ID, an object ID, and a directory (tenant) ID, all of which will then be visible on the app’s ‘Overview’ page.)<br /> <br /> <br /> '''Step 3: Configure the Claws Mail app.'''<br /> <br /> The various configuration pages can be accessed via the links in the side-pane. Nothing needs to be changed on the following pages:<br /> &lt;pre&gt;<br /> Quickstart<br /> Integration assistant<br /> Branding<br /> Certificates &amp; secrets<br /> Token configuration<br /> Expose an API<br /> Owners<br /> Manifest<br /> &lt;/pre&gt;<br /> <br /> Check/adjust settings on the following pages:<br /> &lt;pre&gt;<br /> 'Authentication' - Confirm that the ‘redirect URI’ you set during registration has its box checked. You can also add/delete redirect URI’s on this page, as necessary.<br /> <br /> 'API permissions' - Click on 'Add a permission' &gt; 'Microsoft Graph' &gt; 'Delegated permissions', and add the following permissions. First, select each permission by typing some/all of its name in the search/filter box to narrow the results, expanding categories as needed, and clicking on the box beside the permission so that a check mark shows. Once you've selected all the permissions, click on the 'Add permissions' button to add them all at the same time. Any permissions that have been successfully added will now show up in the 'Configured permissions' list on the 'API permissions' page.<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> - User.Read<br /> &lt;/pre&gt;<br /> Once the Claws Mail app is configured, the Client ID (also called Application ID) can be copied to Claws Mail's corresponding Client ID field. (The Client ID is shown on the app's 'Overview' page in Azure.) No Client Secret is needed, so Claws Mail's Client Secret field should be empty.<br /> <br /> Note: If you are using an email account managed by a third-party organization using Microsoft’s email systems, then when you attempt to get an authorization code you may see a screen that says something like ‘Approval Required’ // ‘This app requires your admin’s approval...’. This is likely because Claws Mail is not ‘published’ by a ‘verified publisher’ or because for some other reason the organization has decided to limit the apps to which users can give permissions. There may be a field where you can enter justification for requesting this app, after which you can click on ‘Request approval’. Then you may see a notice that says the request has been sent to your ‘admin’ and that you’ll receive an email in regards to whether it’s been approved or not. You may want to reach out to your email administrator to see if they got the request, to let them know it is a legitimate request from you, and perhaps provide a link to the Claws Mail website and/or other information about the ‘app’ for which you are wanting them to give you consent permissions. (The above details may be different depending on how the organization has configured their 'user consent' settings.) Ultimately it will be up to the organization (rather than Microsoft or yourself) as to whether you will be able to give Claws the access it needs.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3217 Oauth2 2022-07-05T10:37:16Z <p>Claws: /* Preamble */</p> <hr /> <div>__FORCETOC__<br /> <br /> <br /> == Claws Mail Account Settings for OAuth 2.0 ==<br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt;<br /> 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> == Setting up OAuth 2.0 for Gmail ==<br /> <br /> '''There are some instructions here:'''https://support.google.com/googleapi/answer/6158849''' but the instructions below may be more helpful.'''<br /> <br /> <br /> === Preamble ===<br /> In order to use Gmail in Claws, you have to obtain OAuth2 credentials from Google.<br /> <br /> Getting these can appear quite complicated for the regular non-technical end user, but provided you follow the workflow carefully, it shouldn't take too long.<br /> <br /> Almost everything has to be done in the Google Cloud console, which is designed for software developers to use, so it can appear confusing to a non-technical end-user, and it can be easy to get lost in the multitude of screens and menus.<br /> <br /> <br /> Google also have an unfortunate habit of rejigging their interfaces so that today's workflow might not be tomorrow's.<br /> <br /> However the outline below worked in June 2022.<br /> <br /> The critical thing is to follow the order of activities exactly. Trying to skip ahead or doing something incompletely &amp; hoping to return later can cause problems.<br /> <br /> <br /> The sequence of operations is:<br /> <br /> # Setup Google Cloud Project<br /> # Obtain credentials for your project<br /> # Enter credentials into ClawsMail<br /> # Authorise ClawsMail with Google<br /> <br /> <br /> This sequence will have to be followed for '''each''' Gmail account that you want to use with ClawsMail.<br /> <br /> === Setting up your Google Cloud Project ===<br /> <br /> You need to get into the Google Cloud Console, so go to '''https://console.cloud.google.com/projectselector2/apis/dashboard?supportedpurview=project'''<br /> <br /> If you are already signed into the Google (Gmail) account that you want to set up OAuth2 for, you won't need to sign in.<br /> <br /> If you aren't, sign in with the Google (Gmail) account for which you want to set up OAuth2.<br /> <br /> Once signed in, you need to create a &quot;Project&quot; so that you can generate credentials.<br /> <br /> So, click on &quot;Create Project&quot; on the right hand side of the screen.<br /> <br /> (You can call it whatever you like, but if you're going to create more than one project &amp; set of credentials, it might be helpful to use names that relate uniquely to each email address you are using.)<br /> <br /> '''NB''' If you get into trouble or make mistakes that you can't rectify, you can simply delete the project &amp; start again.<br /> <br /> <br /> '''FIRST'''<br /> <br /> Select &quot;Oauth Consent Screen&quot;<br /> <br /> (you won't be able to create any credentials until you have done this step)<br /> <br /> &lt;pre&gt;For &quot;type&quot;, select &quot;External&quot; &amp; click &quot;CREATE&quot;.<br /> <br /> You're now in &quot;Edit app registration&quot;<br /> <br /> For &quot;App name&quot; you can enter whatever you like.<br /> (Again, it might be helpful to use names related to the email address you're doing this for.)<br /> <br /> Ignore &quot;App domain&quot; fields, they can be left blank.<br /> <br /> In the &quot;User Support Email&quot; and &quot;Developer Contact Email&quot; fields enter the Gmail address for which you want to set up OAuth2 credentials.<br /> <br /> Click &quot;Save and Continue&quot;<br /> &lt;/pre&gt;<br /> <br /> <br /> '''NEXT'''<br /> <br /> Select &quot;add or remove scopes&quot;<br /> You need to select &quot;Gmail&quot; from the list (table) that opens on the RHS of the screen, but it might not appear.<br /> <br /> &lt;blockquote&gt;<br /> If it doesn't appear, you will need to paste<br /> &quot;https://mail.google.com/&quot;<br /> into the &quot;manually add scopes&quot; box,<br /> <br /> then click &quot;update table&quot;,<br /> <br /> then click &quot;update&quot;.<br /> &lt;/blockquote&gt;<br /> <br /> You should now see &quot;GMAIL Scopes&quot; under &quot;Your restricted scopes&quot;<br /> <br /> Click &quot;save and continue&quot;<br /> <br /> <br /> '''NEXT'''<br /> <br /> Click on '''&quot;+ Add users&quot;'''. If you don't add yourself as a test user at this point the authorisation process that comes later will fail.<br /> <br /> Once again, enter the email address that you want to access with Claws Mail.<br /> <br /> Then click &quot;back to dashboard&quot;, which should take you to the &quot;OAuth Consent screen&quot; page.<br /> <br /> On this page you should see a heading of '''&quot;Publishing status&quot;''', under which it should now say '''&quot;Testing&quot;'''.<br /> <br /> <br /> '''Do not be tempted to click &quot;Publish App&quot; at this point.'''<br /> <br /> <br /> '''NEXT'''<br /> <br /> You can now create the credentials you need to authorise ClawsMail to use your Gmail account.<br /> <br /> &lt;pre&gt;<br /> Click &quot;Credentials&quot;, then &quot;create credentials&quot;, and then &quot;OAuth client ID&quot;.<br /> <br /> For &quot;Application Type&quot; select &quot;Desktop app&quot;.<br /> <br /> You can either accept the default name offered, or, as before, enter something relating to the email account for which you're doing this.<br /> <br /> Then click &quot;Create&quot;<br /> <br /> &lt;/pre&gt;<br /> <br /> <br /> A popup box will show you the Client ID &amp; Client Secret.<br /> <br /> You need these to enter into ClawsMail, so copy them.<br /> <br /> There is also an option to download them as a JSON file.<br /> <br /> (This is convenient for the more technically minded user, but perhaps a bit insecure. If you do this, keep it somewhere safe)<br /> <br /> <br /> === Authorising Clawsmail with Google/Gmail ===<br /> '''NEARLY FINALLY'''<br /> <br /> Now that you have your credentials, you have to enter them into ClawsMail itself for your Gmail account.<br /> <br /> Remember that you must also set the &quot;Send&quot; and &quot;Receive&quot; authentication method to &quot;OAuth2&quot; for your account in those screens.<br /> <br /> You need to go to Configuration/Edit accounts &amp; select and edit the account for which you've created the credentials.<br /> <br /> &lt;pre&gt;<br /> Select &quot;Oauth2&quot;.<br /> <br /> From the dropdown &quot;Select OAuth2 Service Email Provider&quot;, select &quot;Google/Gmail&quot;<br /> <br /> You now need to copy into the &quot;Client ID&quot; and &quot;Client Secret&quot; boxes the credentials you copied in the previous step.<br /> <br /> Now click &quot;Open default browser with request&quot;.<br /> <br /> Gmail should launch in your browser, taking you to login screens with multiple warnings about how unsafe what you are doing is.<br /> <br /> Don't &quot;go back to safety&quot;, because what you're doing is safe.<br /> <br /> Eventually you will get a screen offering you an authorisation code.<br /> <br /> Copy this.<br /> &lt;/pre&gt;<br /> <br /> <br /> '''FINAL STEP'''<br /> <br /> Now go back to the ClawsMail OAuth2 page that you launched the browser page from.<br /> <br /> Paste in the code you copied from the Gmail screen in the previous step into the &quot;Authorisation code&quot; box, then click &quot;Authorise&quot; and &quot;Apply&quot;.<br /> <br /> <br /> Now see if you can fetch email from Gmail in Clawsmail.<br /> <br /> <br /> === Epilogue ===<br /> <br /> Unfortunately, because neither your project nor ClawsMail are verified apps as far as Google is concerned, this is not quite the end of the story.<br /> <br /> From now on, every 7 days after the initial authorisation, it will revert to unauthorised &amp; ClawsMail won't be able to access you Gmail account.<br /> <br /> Fortunately, you don't have to go through the whole process again, but just the final step:<br /> <br /> Go to ClawsMail OAuth2 page, launch browser, get an authorisation code &amp; then paste it back into the Authorisation code box &amp; click authorise.<br /> <br /> <br /> <br /> == Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ==<br /> <br /> '''Step 1: Get into 'Azure', Microsoft's cloud computing service.'''<br /> <br /> Go to https://portal.azure.com , making sure you are signed in with the Microsoft account you are wanting to set up. Go to 'Azure Active Directory' (click on the 'View' button under 'Manage Azure Active Directory') and then the 'App registrations' page (via the link in the side-pane). Here is a direct link to this page: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps .<br /> <br /> <br /> '''Step 2: Register Claws Mail as a new app.'''<br /> <br /> Click on 'New Registration' to get to the 'Register an application page', then adjust the settings as follows:<br /> &lt;pre&gt;<br /> Display name: Anything you choose.<br /> <br /> Supported account types - set to &quot;Accounts in any organizational directory… and personal Microsoft accounts…&quot; (Note: This will be shown on the app’s ‘Authentication’ page.) (It will also be represented on the app's ‘Overview’ page as &quot;All Microsoft account users&quot;.)<br /> <br /> Select a platform: &quot;Public client/native...&quot;<br /> <br /> Redirect URI: &lt;nowiki&gt;http://127.0.0.1:8888&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> Once you've adjusted settings as desired, click on the 'Register' button.<br /> <br /> (Note: Creating a new registration will result in the auto-generation of an application (client) ID, an object ID, and a directory (tenant) ID, all of which will then be visible on the app’s ‘Overview’ page.)<br /> <br /> <br /> '''Step 3: Configure the Claws Mail app.'''<br /> <br /> The various configuration pages can be accessed via the links in the side-pane. Nothing needs to be changed on the following pages:<br /> &lt;pre&gt;<br /> Quickstart<br /> Integration assistant<br /> Branding<br /> Certificates &amp; secrets<br /> Token configuration<br /> Expose an API<br /> Owners<br /> Manifest<br /> &lt;/pre&gt;<br /> <br /> Check/adjust settings on the following pages:<br /> &lt;pre&gt;<br /> 'Authentication' - Confirm that the ‘redirect URI’ you set during registration has its box checked. You can also add/delete redirect URI’s on this page, as necessary.<br /> <br /> 'API permissions' - Click on 'Add a permission' &gt; 'Microsoft Graph' &gt; 'Delegated permissions', and add the following permissions. First, select each permission by typing some/all of its name in the search/filter box to narrow the results, expanding categories as needed, and clicking on the box beside the permission so that a check mark shows. Once you've selected all the permissions, click on the 'Add permissions' button to add them all at the same time. Any permissions that have been successfully added will now show up in the 'Configured permissions' list on the 'API permissions' page.<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> - User.Read<br /> &lt;/pre&gt;<br /> Once the Claws Mail app is configured, the Client ID (also called Application ID) can be copied to Claws Mail's corresponding Client ID field. (The Client ID is shown on the app's 'Overview' page in Azure.) No Client Secret is needed, so Claws Mail's Client Secret field should be empty.<br /> <br /> Note: If you are using an email account managed by a third-party organization using Microsoft’s email systems, then when you attempt to get an authorization code you may see a screen that says something like ‘Approval Required’ // ‘This app requires your admin’s approval...’. This is likely because Claws Mail is not ‘published’ by a ‘verified publisher’ or because for some other reason the organization has decided to limit the apps to which users can give permissions. There may be a field where you can enter justification for requesting this app, after which you can click on ‘Request approval’. Then you may see a notice that says the request has been sent to your ‘admin’ and that you’ll receive an email in regards to whether it’s been approved or not. You may want to reach out to your email administrator to see if they got the request, to let them know it is a legitimate request from you, and perhaps provide a link to the Claws Mail website and/or other information about the ‘app’ for which you are wanting them to give you consent permissions. (The above details may be different depending on how the organization has configured their 'user consent' settings.) Ultimately it will be up to the organization (rather than Microsoft or yourself) as to whether you will be able to give Claws the access it needs.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_Gmail&diff=3212 Using Claws Mail with Gmail 2022-05-07T09:46:50Z <p>Claws: /* Claws Mail account setup */</p> <hr /> <div>== Gmail account setup ==<br /> In your Gmail settings, turn on &quot;Enable less secure app access&quot;. (Gmail's &quot;enable less secure app access&quot; is a euphemism for &quot;apps that don't support OAUTH2&quot;, it does not mean programs such as Claws Mail, are less secure.)<br /> <br /> You will also need to use [https://support.google.com/accounts/answer/185833?authuser=0 an App Password] to log in if using two factor authentication on your account.<br /> <br /> == Claws Mail account setup ==<br /> <br /> <br /> Open your account preferences, and make sure these options are set:<br /> <br /> ; on 'Basic' page<br /> : server for receiving: imap.gmail.com<br /> : SMTP server (send): smtp.gmail.com<br /> : User ID: [your complete gmail email address]<br /> <br /> ; on 'Receive' page<br /> : Authentication method: Automatic<br /> : IMAP server directory: [leave empty]<br /> <br /> ; on 'Send' page<br /> :[x] SMTP Authentication (SMTP AUTH)<br /> : Authentication method: Automatic<br /> <br /> ; on 'TLS' page<br /> : IMAP: Use TLS<br /> : Send (SMTP): Use STARTTLS command to start encrypted session<br /> <br /> ; on 'Advanced' page<br /> : SMTP port: 587<br /> : IMAP port: 993<br /> <br /> Set the [Gmail]/Trash folder as Folder Type 'Trash' on the General page of the folder Properties, so that emptying Trash really deletes the messages it contains.<br /> <br /> Additionally, as gmail cannot handle incremental saves to the Drafts folder, turn off 'Automatically save to Drafts folder every n characters' on the /Configuration/Preferences/Compose/Writing page.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3208 Oauth2 2022-03-28T11:37:32Z <p>Claws: Protected &quot;Oauth2&quot; ([Move=Allow only administrators] (indefinite))</p> <hr /> <div>__FORCETOC__<br /> <br /> === Claws Mail Account Settings for OAuth 2.0 === <br /> <br /> When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:<br /> &lt;pre&gt; 'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'.<br /> <br /> 'Receive' page (IMAP): Authentication method = 'OAuth2'.<br /> <br /> 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.<br /> &lt;/pre&gt;<br /> <br /> <br /> === Setting up OAuth 2.0 for Gmail === <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'Testing' (initial default)<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the ClientID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in<br /> Claws Mail Oauth2 account preferences screen.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable.<br /> <br /> <br /> === Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ===<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3206 Oauth2 2022-03-24T16:58:41Z <p>Claws: improve layout</p> <hr /> <div>__FORCETOC__<br /> <br /> === Setting up OAuth 2.0 for Gmail === <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> &lt;pre&gt; Project name: Anything of your choice<br /> <br /> Publishing status (of project): 'Testing' (initial default)<br /> <br /> User type: External<br /> &lt;/pre&gt;<br /> '''Notes related to the above:'''<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> &lt;pre&gt; App name: Anything of your choice<br /> <br /> User support email: Your own email<br /> <br /> Developer email: Your own email<br /> <br /> App domain entries: Leave blank<br /> &lt;/pre&gt;<br /> '''Scopes settings:'''<br /> &lt;pre&gt; Click on 'Add or Remove Scopes'.<br /> <br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and<br /> permanently delete all your email from Gmail&quot;<br /> <br /> (Note that the list is in alphabetical order and you may need to go to a later page to find this entry.<br /> Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> <br /> Click on 'Update'.<br /> <br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> <br /> Click on 'Save and Continue'.<br /> &lt;/pre&gt;<br /> '''Getting the ClientID'''<br /> &lt;pre&gt;<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in<br /> Claws Mail Oauth2 account preferences screen.<br /> &lt;/pre&gt;<br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to login to Gmail's webmail and change your security settings there to allow access to 'less-secure' third-party apps.<br /> <br /> <br /> === Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ===<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3205 Oauth2 2022-03-24T16:53:10Z <p>Claws: normalise the section headings</p> <hr /> <div>__FORCETOC__<br /> <br /> === Setting up OAuth 2.0 for Gmail === <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Publishing status (of project): 'Testing' (initial default)<br /> User type: External<br /> <br /> Notes related to the above:<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> '''Scopes settings:'''<br /> Click on 'Add or Remove Scopes'.<br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail&quot;<br /> (For the above, note that the list is in alphabetical order and you may need to go to a later page to find this entry.)<br /> (Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> Click on 'Update'.<br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> Click on 'Save and Continue'.<br /> <br /> '''Getting the ClientID'''<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to login to Gmail's webmail and change your security settings there to allow access to 'less-secure' third-party apps.<br /> <br /> <br /> === Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange ===<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3204 Oauth2 2022-03-24T16:52:07Z <p>Claws: force Table of contents</p> <hr /> <div>__FORCETOC__<br /> <br /> === Setting up OAuth 2.0 for Gmail === <br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Publishing status (of project): 'Testing' (initial default)<br /> User type: External<br /> <br /> Notes related to the above:<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> '''Scopes settings:'''<br /> Click on 'Add or Remove Scopes'.<br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail&quot;<br /> (For the above, note that the list is in alphabetical order and you may need to go to a later page to find this entry.)<br /> (Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> Click on 'Update'.<br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> Click on 'Save and Continue'.<br /> <br /> '''Getting the ClientID'''<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to login to Gmail's webmail and change your security settings there to allow access to 'less-secure' third-party apps.<br /> <br /> <br /> === Microsoft - for Outlook or Exchange ===<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3203 Oauth2 2022-03-24T16:48:58Z <p>Claws: more use of wiki syntax</p> <hr /> <div>=== Setting up OAuth 2.0 for Gmail ===<br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Publishing status (of project): 'Testing' (initial default)<br /> User type: External<br /> <br /> Notes related to the above:<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> '''Scopes settings:'''<br /> Click on 'Add or Remove Scopes'.<br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail&quot;<br /> (For the above, note that the list is in alphabetical order and you may need to go to a later page to find this entry.)<br /> (Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> Click on 'Update'.<br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> Click on 'Save and Continue'.<br /> <br /> '''Getting the ClientID'''<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to login to Gmail's webmail and change your security settings there to allow access to 'less-secure' third-party apps.<br /> <br /> <br /> === Microsoft - for Outlook or Exchange ===<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3202 Oauth2 2022-03-24T16:44:06Z <p>Claws: readability improvements</p> <hr /> <div>----------------------------------------<br /> '''''Setting up OAuth 2.0 for Gmail'''''<br /> ----------------------------------------<br /> <br /> '''Follow the instructions here:'''<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Publishing status (of project): 'Testing' (initial default)<br /> User type: External<br /> <br /> Notes related to the above:<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> '''Scopes settings:'''<br /> Click on 'Add or Remove Scopes'.<br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail&quot;<br /> (For the above, note that the list is in alphabetical order and you may need to go to a later page to find this entry.)<br /> (Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> Click on 'Update'.<br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> Click on 'Save and Continue'.<br /> <br /> '''Getting the ClientID'''<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to login to Gmail's webmail and change your security settings there to allow access to 'less-secure' third-party apps.<br /> <br /> <br /> ---------------------------------------------<br /> '''''Microsoft - for Outlook or Exchange'''''<br /> ---------------------------------------------<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3201 Oauth2 2022-03-24T16:42:23Z <p>Claws: readability improvements</p> <hr /> <div>----------------------------------------<br /> Setting up OAuth 2.0 for Gmail<br /> ----------------------------------------<br /> Follow the instructions here:<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Publishing status (of project): 'Testing' (initial default)<br /> User type: External<br /> <br /> Notes related to the above:<br /> <br /> 1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)<br /> <br /> 2. Regarding Google's above-linked instructions related to the &quot;Credentials&quot; page: Where it says &quot;Click 'New Credentials'&quot; it should read &quot;Click '+ CREATE CREDENTIALS'&quot; (as of 24 Mar 2022).<br /> <br /> 3. Regarding &quot;Publishing status&quot;, there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)<br /> <br /> <br /> '''OAuth consent screen settings:'''<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> '''Scopes settings:'''<br /> Click on 'Add or Remove Scopes'.<br /> Select (check the box) this entry: &quot;Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail&quot;<br /> (For the above, note that the list is in alphabetical order and you may need to go to a later page to find this entry.)<br /> (Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.)<br /> Click on 'Update'.<br /> Confirm that the section 'Your restricted scopes' shows the entry you just added.<br /> Click on 'Save and Continue'.<br /> <br /> '''Getting the ClientID'''<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> '''Troubleshooting:'''<br /> <br /> It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to login to Gmail's webmail and change your security settings there to allow access to 'less-secure' third-party apps.<br /> <br /> <br /> ---------------------------------------------<br /> Microsoft - for Outlook or Exchange<br /> ---------------------------------------------<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=GTK3_Porting_Checklist&diff=3199 GTK3 Porting Checklist 2022-03-19T13:01:21Z <p>Claws: /* Does not work */</p> <hr /> <div>== Does not work ==<br /> <br /> * Foldersel dialog doesn't show alternating colors in the folder list.<br /> <br /> * &quot;gtk-can-change-accels&quot; has been removed: 'GtkSettings:gtk-can-change-accels has been deprecated since version 3.10 and should not be used in newly-written code. This setting is ignored.'<br /> It seems that the only way to re-enable this is to switch to GtkApplication, and write our own acclerator implementation. https://developer.gnome.org/gtk3/stable/GtkApplication.html#gtk-application-add-accelerator<br /> <br /> == Works, but is ugly ==<br /> <br /> * GtkSpinButton is too wide with the -/+ buttons being large and next to each other, instead of small and one above another like in GTK2.<br /> <br /> == Deprecated API ==<br /> <br /> * GtkBox -&gt; GtkGrid (for GTK4)<br /> <br /> * GtkUIManager is deprecated in GTK3, to be removed in GTK4</div> Claws https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=3198 MediaWiki:Sidebar 2022-03-17T15:50:32Z <p>Claws: </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 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 /> ** https://www.claws-mail.org/|What is it?<br /> ** https://www.claws-mail.org/features.php|Features<br /> ** https://www.claws-mail.org/screenshots.php|Screenshots<br /> ** https://www.claws-mail.org/documentation.php|User manual<br /> ** https://www.claws-mail.org/downloads.php|Downloads<br /> ** https://www.claws-mail.org/plugins.php|Plugins<br /> ** https://www.claws-mail.org/themes.php|Themes<br /> ** https://www.claws-mail.org/tools.php|Tools<br /> ** https://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi|Bug Tracker<br /> ** https://www.claws-mail.org/devel.php|Developers<br /> ** https://www.claws-mail.org/git.php|Get GIT<br /> ** https://git.claws-mail.org/|Browse GIT<br /> ** https://www.claws-mail.org/i18n.php|i18n Status<br /> ** https://www.claws-mail.org/MLs.php|Community<br /> ** https://www.claws-mail.org/theteam.php|The Team<br /> ** https://www.claws-mail.org/MLs.php|Contact<br /> ** https://www.claws-mail.org/donations.php|Donations</div> Claws https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=3197 MediaWiki:Sidebar 2022-03-10T14:34:57Z <p>Claws: </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 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 /> ** https://www.claws-mail.org/|What is it?<br /> ** https://www.claws-mail.org/features.php|Features<br /> ** https://www.claws-mail.org/screenshots.php|Screenshots<br /> ** https://www.claws-mail.org/documentation.php|User manual<br /> ** https://www.claws-mail.org/downloads.php|Downloads<br /> ** https://www.claws-mail.org/plugins.php|Plugins<br /> ** https://www.claws-mail.org/themes.php|Themes<br /> ** https://www.claws-mail.org/tools.php|Tools<br /> ** https://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi|Bug Tracker<br /> ** https://www.claws-mail.org/devel.php|Developers<br /> ** https://www.claws-mail.org/git.php|Get GIT<br /> ** https://git.claws-mail.org/|Browse GIT<br /> ** https://www.claws-mail.org/i18n.php|i18n Status<br /> ** https://www.claws-mail.org/MLs.php|Community<br /> ** https://www.claws-mail.org/theteam.php|The Team<br /> ** https://www.claws-mail.org/MLs.php|Contact<br /> ** https://www.claws-mail.org/reviews.php|Reviews<br /> ** https://www.claws-mail.org/donations.php|Donations</div> Claws https://www.claws-mail.org/faq/index.php?title=MediaWiki:Sidebar&diff=3196 MediaWiki:Sidebar 2022-03-10T14:34:32Z <p>Claws: </p> <hr /> <div>https://www.claws-mail.org/img/nowar.jpg<br /> <br /> * 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 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 /> ** https://www.claws-mail.org/|What is it?<br /> ** https://www.claws-mail.org/features.php|Features<br /> ** https://www.claws-mail.org/screenshots.php|Screenshots<br /> ** https://www.claws-mail.org/documentation.php|User manual<br /> ** https://www.claws-mail.org/downloads.php|Downloads<br /> ** https://www.claws-mail.org/plugins.php|Plugins<br /> ** https://www.claws-mail.org/themes.php|Themes<br /> ** https://www.claws-mail.org/tools.php|Tools<br /> ** https://www.thewildbeast.co.uk/claws-mail/bugzilla/index.cgi|Bug Tracker<br /> ** https://www.claws-mail.org/devel.php|Developers<br /> ** https://www.claws-mail.org/git.php|Get GIT<br /> ** https://git.claws-mail.org/|Browse GIT<br /> ** https://www.claws-mail.org/i18n.php|i18n Status<br /> ** https://www.claws-mail.org/MLs.php|Community<br /> ** https://www.claws-mail.org/theteam.php|The Team<br /> ** https://www.claws-mail.org/MLs.php|Contact<br /> ** https://www.claws-mail.org/reviews.php|Reviews<br /> ** https://www.claws-mail.org/donations.php|Donations</div> Claws https://www.claws-mail.org/faq/index.php?title=General_Information&diff=3195 General Information 2022-02-28T13:16:30Z <p>Claws: /* How does Claws Mail store mails? */</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 /> === Where can I get Claws Mail? ===<br /> <br /> See the Downloads page https://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. Mbox format is also supported via the mailMBOX plugin.<br /> <br /> === Where does Claws Mail store mails? ===<br /> <br /> By default, Claws Mail stores mails in $HOME/Mail.<br /> <br /> The location of mail folders is defined in $HOME/.claws-mail/folderlist.xml<br /> <br /> To point Claws Mail at an alternative mail store, select File -&gt; Add Mailbox and specify the path to the mail folder. Claws Mail will scan for sub-folders automatically.<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 https://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 and in the '/Help/About' dialogue in Claws Mail itself.<br /> <br /> === How can I quickly update the views in Claws Mail? ===<br /> <br /> Just press Ctrl+Alt+U or select &quot;/View/Update summary&quot; from the main 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 /> Setting an alternate configuration directory (--alternate-config-dir option) overrides TMPDIR value<br /> and places the socket under the alternate directory.<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! :)<br /> <br /> === Why does the users' mailing list get mail from the bug tracker? ===<br /> <br /> Mail from the bug tracker gets delivered to the users' mailing list because it is believed and/or hoped that subscribers, as Claws Mail users, can help in bug reporting. Be that confirming, suggesting solutions, or whatever.<br /> <br /> Feature requests also delivered via the bug tracker, and this makes everyone aware of the requests, and enables everyone to voice an opinion on the usefulness of such a feature.<br /> <br /> All in all, it's about getting user involvement, and opening up an aspect of development to conversation, however slight that might turn out to be in practice.<br /> <br /> === What are the differences between Claws Mail and Sylpheed? ===<br /> <br /> Back in 2001 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 in 2006 became an entity in its own right, in part due to different goals and the fact that syncing both codebases stopped happening.<br /> <br /> Claws Mail has many extra features compared to Sylpheed and is more powerful, yet is just as fast, lightweight and stable.</div> Claws https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=3194 Main Page 2022-02-27T10:51:05Z <p>Claws: </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 /> ** [[SSL/TLS certificate verification errors]]<br /> ** [[LDAP and Claws Mail]]<br /> ** [[Connecting to MS Exchange]]<br /> ** [[Using Claws Mail with Gmail]]<br /> ** [[Connecting with Tor]]<br /> ** [[Oauth2]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Debugging Claws]]<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> Claws https://www.claws-mail.org/faq/index.php?title=Filtering_and_Processing_of_Messages&diff=3193 Filtering and Processing of Messages 2022-01-15T21:39:46Z <p>Claws: /* What is the difference between Filtering, Folder Processing, Pre/Post-processing? */</p> <hr /> <div>=== What is the difference between Filtering, Folder Processing, Pre/Post-processing? ===<br /> <br /> Filtering rules are global. Messages received on an Account can be filtered in 2 ways, automatically or manually. To have the messages filtered automatically the option 'Filter messages on receiving' must be checked on the 'Receive' tab in the Account Preferences. Manual filtering can be performed by using '/Tools/Filter all messages in folder' or '/Tools/Filter selected messages'.<br /> <br /> Folder Processing rules apply only to the messages contained in that particular folder. A folder's Processing rules are applied upon entering that folder, or on program startup if 'Process at startup' is checked in a folder's Properties, or on demand by using 'Run processing rules' from the folder's context menu.<br /> <br /> Pre and post-processing rules are global rules which are executed before and after the folder processing rules, respectively.<br /> In other words: Whenever you select a folder, first pre-processing rules are applied, then folder specific processing rules and lastly post-processing rules.<br /> <br /> === What type of value do the &quot;age ...&quot; match types in the filtering configuration expect? ===<br /> <br /> You simply have to add the value in days. If you want for example to select messages older than a month, enter 30 or 31.<br /> <br /> Example of a folder processing rule of the &quot;mailbox/claws-mail/&quot; Folder, that move messages older that 60 days to an archive folder:<br /> &lt;pre&gt;<br /> age_greater 60 move &quot;#mh/mailbox/claws-mail/archive&quot;<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' Age checks are done against the 'Date'-header in the mail. So if the sender has misconfigured his computer and sends mails with a wrong date, the rule could move mails instantly if the date is more then 60 days in the past or never when it is in the future.<br /> <br /> === Can I filter messages based on Content-Type of attachments, for example &quot;application/x-msdownload&quot;? ===<br /> <br /> Yes. Select Match Type 'Body part' and enter the Value &lt;code&gt;Content-Type: application/x-msdownload&lt;/code&gt;.<br /> <br /> Please note that application/octet-stream is also a potential infected content (.pif for instance).<br /> You can also use a more generic case-insensitive regexp matching rule against the 'Body part' like the following one:&lt;br&gt;<br /> &lt;pre&gt;<br /> Content\-Type: ~[[a-z0-9_/-]]+; name=&quot;~[[^\.]]+\.(bat|pif|cmd|vbs|vba|scr|lnk|com|exe|java|asp|cgi)&quot;<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' This will also match text inside the message and not only the Content-Type, so be aware of messages discussing the structure of MIME-Mails.<br /> <br /> === Can a filter modify the contents of a message? ===<br /> <br /> None of the built-in filters modify the contents of a message, but you can use the 'test' filter to run a command that can modify the contents of a message. See the next question for an example.<br /> <br /> === How do I configure a filter for running SpamAssassin? ===<br /> <br /> If you want to use SpamAssassin directly, instead of using the plugin, you can get the SpamAssassin headers added to each message, and/or tag the subject line of spam messages. First, you have to set up SpamAssassin correctly, which is beyond the scope of this FAQ. This example uses the spamc/spamd client server model, but it could easily be adapted for calling SpamAssassin directly. First, save this script somewhere in your PATH (eg $HOME/bin/sc-spamc).<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> #<br /> # sc-spamc : a script for using SpamAssassin header modification / subject<br /> # tagging vi Claws Mail filtering actions.<br /> #<br /> # Author: Robert Story<br /> # Send questions or comments to the claws-mail-users mailing list<br /> #<br /> # Based on a simpler script posted to the claws-mail-users mailing list<br /> # by Richard A Downing.<br /> #<br /> # Should return the return code from spamc (1=spam, 0=nospam/error)<br /> #<br /> <br /> die()<br /> {<br /> : error &quot;$@&quot;<br /> : exit 0<br /> }<br /> <br /> FILE=$*<br /> TEMP=sc-spamc.$$<br /> <br /> #<br /> # call spamc, redirect output to temporary file, and save return value<br /> #<br /> /usr/bin/spamc -E -t 30 &lt; &quot;$FILE&quot; &gt; &quot;$TEMP&quot;<br /> RC=$?<br /> <br /> #<br /> # make sure temp file exists before we replace original message<br /> #<br /> if ! test -s &quot;$TEMP&quot; ; then<br /> : die &quot;spamc result file doesn't exist or is 0 bytes&quot;<br /> fi<br /> <br /> #<br /> # backup original<br /> #<br /> mv &quot;$FILE&quot; &quot;$FILE.bak&quot;<br /> if test $? -ne 0; then<br /> : die &quot;'mv $@' failed!&quot;<br /> fi<br /> <br /> #<br /> # rename filtered file<br /> #<br /> mv &quot;$TEMP&quot; &quot;$FILE&quot;<br /> if test ! 0 = $?; then<br /> : mv &quot;$FILE.bak&quot; &quot;$FILE&quot;<br /> : die &quot;spam result rename failed, restoring backup&quot;<br /> else<br /> : rm &quot;$FILE.bak&quot;<br /> fi<br /> <br /> #<br /> # return spamc exit code<br /> #<br /> exit $RC<br /> <br /> &lt;/pre&gt;<br /> Now, set up a Filtering rule (test &quot;!(sc-spamc %F)&quot;), with an action for dealing with spam (eg color it, move it to a folder, etc).<br /> <br /> === How do I add a filter for SPF checking? ===<br /> <br /> To check if the sender IP address matches the SPF record you can download the script sylpheed-spf.pl from http://www.willamowius.de/claws-spf.html and add a filter with the following condition and move matching mails to your spam folder.<br /> <br /> &lt;pre&gt;<br /> test &quot;!(sylpheed-spf.pl -c &lt;%F)&quot;<br /> &lt;/pre&gt;<br /> <br /> === My ISP adds headers that identify spam and viruses. How do I filter on a custom header? ===<br /> <br /> You can filter on a custom header. The drop-down list of headers defaults to the commonly used headers, but you can edit the list and add new entries. Create a filter in the normal way and select &quot;Header&quot; as the condition. Simply start typing in the list box to edit or add a header.</div> Claws https://www.claws-mail.org/faq/index.php?title=Filtering_and_Processing_of_Messages&diff=3192 Filtering and Processing of Messages 2022-01-15T21:39:03Z <p>Claws: </p> <hr /> <div>=== What is the difference between Filtering, Folder Processing, Pre/Post-processing? ===<br /> <br /> Filtering rules are global. Messages received on an Account can be filtered in 2 ways, automatically or manually. To have the messages filtered automatically the option 'Filter messages on receiving' must be checked on the 'Receive' tab in the Account Preferences. Manual filtering can be performed by using '/Tools/Filter all messages in folder' or '/Tools/Filter selected messages'.<br /> <br /> Folder Processing rules apply only to the messages contained in that particular folder. A folder's Processing rules are applied upon entering that folder, or on program startup if 'Process at startup' is checked in a folder's Properties, or on demand by using 'Run processing rules' from the folder's context menu.<br /> <br /> Pre and post-processing rules are global rules which are executed before and after the folder processing rules, respectively.<br /> In other words: Whenever you select a folder, first pre-processing rules are applied, then folder specific processing rules and lastly post-processing rules. See [[Filtering_and_Processing_of_Messages#age|'age'-question]] for an example.<br /> <br /> === What type of value do the &quot;age ...&quot; match types in the filtering configuration expect? ===<br /> <br /> You simply have to add the value in days. If you want for example to select messages older than a month, enter 30 or 31.<br /> <br /> Example of a folder processing rule of the &quot;mailbox/claws-mail/&quot; Folder, that move messages older that 60 days to an archive folder:<br /> &lt;pre&gt;<br /> age_greater 60 move &quot;#mh/mailbox/claws-mail/archive&quot;<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' Age checks are done against the 'Date'-header in the mail. So if the sender has misconfigured his computer and sends mails with a wrong date, the rule could move mails instantly if the date is more then 60 days in the past or never when it is in the future.<br /> <br /> === Can I filter messages based on Content-Type of attachments, for example &quot;application/x-msdownload&quot;? ===<br /> <br /> Yes. Select Match Type 'Body part' and enter the Value &lt;code&gt;Content-Type: application/x-msdownload&lt;/code&gt;.<br /> <br /> Please note that application/octet-stream is also a potential infected content (.pif for instance).<br /> You can also use a more generic case-insensitive regexp matching rule against the 'Body part' like the following one:&lt;br&gt;<br /> &lt;pre&gt;<br /> Content\-Type: ~[[a-z0-9_/-]]+; name=&quot;~[[^\.]]+\.(bat|pif|cmd|vbs|vba|scr|lnk|com|exe|java|asp|cgi)&quot;<br /> &lt;/pre&gt;<br /> <br /> '''Note:''' This will also match text inside the message and not only the Content-Type, so be aware of messages discussing the structure of MIME-Mails.<br /> <br /> === Can a filter modify the contents of a message? ===<br /> <br /> None of the built-in filters modify the contents of a message, but you can use the 'test' filter to run a command that can modify the contents of a message. See the next question for an example.<br /> <br /> === How do I configure a filter for running SpamAssassin? ===<br /> <br /> If you want to use SpamAssassin directly, instead of using the plugin, you can get the SpamAssassin headers added to each message, and/or tag the subject line of spam messages. First, you have to set up SpamAssassin correctly, which is beyond the scope of this FAQ. This example uses the spamc/spamd client server model, but it could easily be adapted for calling SpamAssassin directly. First, save this script somewhere in your PATH (eg $HOME/bin/sc-spamc).<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> #<br /> # sc-spamc : a script for using SpamAssassin header modification / subject<br /> # tagging vi Claws Mail filtering actions.<br /> #<br /> # Author: Robert Story<br /> # Send questions or comments to the claws-mail-users mailing list<br /> #<br /> # Based on a simpler script posted to the claws-mail-users mailing list<br /> # by Richard A Downing.<br /> #<br /> # Should return the return code from spamc (1=spam, 0=nospam/error)<br /> #<br /> <br /> die()<br /> {<br /> : error &quot;$@&quot;<br /> : exit 0<br /> }<br /> <br /> FILE=$*<br /> TEMP=sc-spamc.$$<br /> <br /> #<br /> # call spamc, redirect output to temporary file, and save return value<br /> #<br /> /usr/bin/spamc -E -t 30 &lt; &quot;$FILE&quot; &gt; &quot;$TEMP&quot;<br /> RC=$?<br /> <br /> #<br /> # make sure temp file exists before we replace original message<br /> #<br /> if ! test -s &quot;$TEMP&quot; ; then<br /> : die &quot;spamc result file doesn't exist or is 0 bytes&quot;<br /> fi<br /> <br /> #<br /> # backup original<br /> #<br /> mv &quot;$FILE&quot; &quot;$FILE.bak&quot;<br /> if test $? -ne 0; then<br /> : die &quot;'mv $@' failed!&quot;<br /> fi<br /> <br /> #<br /> # rename filtered file<br /> #<br /> mv &quot;$TEMP&quot; &quot;$FILE&quot;<br /> if test ! 0 = $?; then<br /> : mv &quot;$FILE.bak&quot; &quot;$FILE&quot;<br /> : die &quot;spam result rename failed, restoring backup&quot;<br /> else<br /> : rm &quot;$FILE.bak&quot;<br /> fi<br /> <br /> #<br /> # return spamc exit code<br /> #<br /> exit $RC<br /> <br /> &lt;/pre&gt;<br /> Now, set up a Filtering rule (test &quot;!(sc-spamc %F)&quot;), with an action for dealing with spam (eg color it, move it to a folder, etc).<br /> <br /> === How do I add a filter for SPF checking? ===<br /> <br /> To check if the sender IP address matches the SPF record you can download the script sylpheed-spf.pl from http://www.willamowius.de/claws-spf.html and add a filter with the following condition and move matching mails to your spam folder.<br /> <br /> &lt;pre&gt;<br /> test &quot;!(sylpheed-spf.pl -c &lt;%F)&quot;<br /> &lt;/pre&gt;<br /> <br /> === My ISP adds headers that identify spam and viruses. How do I filter on a custom header? ===<br /> <br /> You can filter on a custom header. The drop-down list of headers defaults to the commonly used headers, but you can edit the list and add new entries. Create a filter in the normal way and select &quot;Header&quot; as the condition. Simply start typing in the list box to edit or add a header.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3191 Using Claws Mail with other programs 2021-10-11T13:35:45Z <p>Claws: /* System Integration */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration script ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior you need the following script somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> Name it &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> <br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> <br /> Every task created within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and gets annotated with the link to open it from Taskwarrior. Also, the task's description is the message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;. You can adjust that according to your preferences.<br /> <br /> ==== Add a User Action in Claws-mail ====<br /> <br /> You need to add the following action as a &quot;shell command&quot; in Claws Mail:<br /> <br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> <br /> Running this Action on a message will create a new Taskwarrior task.<br /> <br /> <br /> [See https://claws-mail.org/faq/index.php/Actions on setting up an Action]<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query a mail/news message with<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/Mail/Inbox/12345&lt;/code&gt; (for an MH mailbox)<br /> <br /> or<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt; (for an IMAP mailbox)<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for an email message and &lt;code&gt;message/news&lt;/code&gt; for an NNTP message.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> <br /> as &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure 2 new filetypes with:<br /> <br /> &lt;pre&gt;<br /> xdg-mime default claws-select.desktop message/rfc822<br /> <br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> <br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;<br /> $ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> &lt;/pre&gt;<br /> <br /> and<br /> <br /> &lt;pre&gt;<br /> $ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/news<br /> &lt;/pre&gt;<br /> <br /> ==== Testing ====<br /> <br /> Now you can test opening a mail/news message with &lt;code&gt;xdg-open&lt;/code&gt; in your &lt;code&gt;terminal&lt;/code&gt;.<br /> <br /> Finally, after you've created task #xyz within Claws Mail, you will be able to see it in Taskwarrior --- filter with<br /> &lt;code&gt;+inbox +email&lt;/code&gt; and then you will be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you will see it it higlighted in Claws Mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3190 Using Claws Mail with other programs 2021-10-11T13:35:08Z <p>Claws: /* System Integration */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration script ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior you need the following script somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> Name it &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> <br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> <br /> Every task created within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and gets annotated with the link to open it from Taskwarrior. Also, the task's description is the message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;. You can adjust that according to your preferences.<br /> <br /> ==== Add a User Action in Claws-mail ====<br /> <br /> You need to add the following action as a &quot;shell command&quot; in Claws Mail:<br /> <br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> <br /> Running this Action on a message will create a new Taskwarrior task.<br /> <br /> <br /> [See https://claws-mail.org/faq/index.php/Actions on setting up an Action]<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query a mail/news message with<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/Mail/Inbox/12345&lt;/code&gt; (for an MH mailbox)<br /> <br /> or<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt; (for an IMAP mailbox)<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for an email message and &lt;code&gt;message/news&lt;/code&gt; for an NNTP message.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> <br /> as &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure 2 new filetypes with:<br /> <br /> &lt;pre&gt;<br /> xdg-mime default claws-select.desktop message/rfc822<br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> <br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;<br /> $ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> &lt;/pre&gt;<br /> <br /> ==== Testing ====<br /> <br /> Now you can test opening a mail/news message with &lt;code&gt;xdg-open&lt;/code&gt; in your &lt;code&gt;terminal&lt;/code&gt;.<br /> <br /> Finally, after you've created task #xyz within Claws Mail, you will be able to see it in Taskwarrior --- filter with<br /> &lt;code&gt;+inbox +email&lt;/code&gt; and then you will be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you will see it it higlighted in Claws Mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3189 Using Claws Mail with other programs 2021-10-11T13:34:06Z <p>Claws: /* System Integration */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration script ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior you need the following script somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> Name it &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> <br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> <br /> Every task created within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and gets annotated with the link to open it from Taskwarrior. Also, the task's description is the message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;. You can adjust that according to your preferences.<br /> <br /> ==== Add a User Action in Claws-mail ====<br /> <br /> You need to add the following action as a &quot;shell command&quot; in Claws Mail:<br /> <br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> <br /> Running this Action on a message will create a new Taskwarrior task.<br /> <br /> <br /> [See https://claws-mail.org/faq/index.php/Actions on setting up an Action]<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query a mail/news message with<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/Mail/Inbox/12345&lt;/code&gt; (for an MH mailbox)<br /> <br /> or<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt; (for an IMAP mailbox)<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for an email message and &lt;code&gt;message/news&lt;/code&gt; for an NNTP message.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> <br /> as &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure 2 new filetypes with:<br /> <br /> &lt;pre&gt;<br /> xdg-mime default claws-select.desktop message/rfc822<br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> <br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;<br /> $ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> Checking /home/[USER]/.config/mimeapps.list<br /> claws-select.desktop<br /> &lt;/pre&gt;<br /> <br /> ==== Testing ====<br /> <br /> Now you can test opening a mail/news message with &lt;code&gt;xdg-open&lt;/code&gt; in your &lt;code&gt;terminal&lt;/code&gt;.<br /> <br /> Finally, after you've created task #xyz within Claws Mail, you will be able to see it in Taskwarrior --- filter with<br /> &lt;code&gt;+inbox +email&lt;/code&gt; and then you will be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you will see it it higlighted in Claws Mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3188 Using Claws Mail with other programs 2021-10-11T13:32:53Z <p>Claws: /* Integrating Claws-mail with Taskwarrior */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration script ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior you need the following script somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> Name it &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> <br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> <br /> Every task created within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and gets annotated with the link to open it from Taskwarrior. Also, the task's description is the message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;. You can adjust that according to your preferences.<br /> <br /> ==== Add a User Action in Claws-mail ====<br /> <br /> You need to add the following action as a &quot;shell command&quot; in Claws Mail:<br /> <br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> <br /> Running this Action on a message will create a new Taskwarrior task.<br /> <br /> <br /> [See https://claws-mail.org/faq/index.php/Actions on setting up an Action]<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query a mail/news message with<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/Mail/Inbox/12345&lt;/code&gt; (for an MH mailbox)<br /> <br /> or<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt; (for an IMAP mailbox)<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for an email message and &lt;code&gt;message/news&lt;/code&gt; for an NNTP message.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> <br /> as e.g. &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure new filetype with:<br /> <br /> &lt;pre&gt;<br /> xdg-mime default claws-select.desktop message/rfc822<br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> <br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;<br /> $ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> Checking /home/[USER]/.config/mimeapps.list<br /> claws-select.desktop<br /> &lt;/pre&gt;<br /> <br /> ==== Testing ====<br /> <br /> Now you can test opening a mail/news message with &lt;code&gt;xdg-open&lt;/code&gt; in your &lt;code&gt;terminal&lt;/code&gt;.<br /> <br /> Finally, after you've created task #xyz within Claws Mail, you will be able to see it in Taskwarrior --- filter with<br /> &lt;code&gt;+inbox +email&lt;/code&gt; and then you will be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you will see it it higlighted in Claws Mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3187 Using Claws Mail with other programs 2021-10-11T13:24:13Z <p>Claws: /* Integrating Claws-mail with Taskwarrior */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration script ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior you need the following script somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> Name it &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> <br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> <br /> Every task created within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and gets annotated with the link to open it from Taskwarrior. Also, the task's description is the message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;. You can adjust that according to your preferences.<br /> <br /> ==== Add a User Action in Claws-mail ====<br /> <br /> You need to add the following action as a &quot;shell command&quot; in Claws Mail:<br /> <br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> <br /> Running this Action on a message will create a new Taskwarrior task.<br /> <br /> <br /> [See https://claws-mail.org/faq/index.php/Actions on setting up an Action]<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query some mail/news message with e.g.<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt;<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for IMAP and &lt;code&gt;message/news&lt;/code&gt; for NNTP messages.<br /> <br /> Now, when i was checking default association on my system with:<br /> <br /> &lt;code&gt;xdg-mime query default message/rfc822 &lt;/code&gt;<br /> <br /> it was tied to Evolution, while &lt;code&gt;message/news&lt;/code&gt; was not tied to anything.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> as e.g. &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure new filetype with:<br /> <br /> &lt;pre&gt;xdg-mime default claws-select.desktop message/rfc822<br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;$ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> Checking /home/gour/.config/mimeapps.list<br /> claws-select.desktop<br /> &lt;/pre&gt;<br /> ==== Testing ====<br /> <br /> Now you can also try whether you can open mail/news messages with xdg-open in your terminal.<br /> <br /> Finally, after you create task #xyz within Claws-mail, you should be able to see it within Taskwarrior --- filter with e.g. &lt;code&gt;+inbox +email&lt;/code&gt; and then you should be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you should see it it higlighted in Claws-mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3186 Using Claws Mail with other programs 2021-10-11T13:15:32Z <p>Claws: /* Integrating Claws-mail with Taskwarrior */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration script ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior you need the following script somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> Name it &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> <br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> I want that every task created from within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and get annotated with the link to open it from Taskwarrior. Moreover, task's descriptions is message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;, so you're free to adjust it according to Your preferences.<br /> <br /> ==== Adding User Action to Claws-mail ====<br /> <br /> Now one needs to add the folowing action as shell command to Claws-mail which I put on the Toolbar and named Taskwarrior:<br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> Now clicking on certain mail or news (NNTP) message should create a new Taskwarrior task.<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query some mail/news message with e.g.<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt;<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for IMAP and &lt;code&gt;message/news&lt;/code&gt; for NNTP messages.<br /> <br /> Now, when i was checking default association on my system with:<br /> <br /> &lt;code&gt;xdg-mime query default message/rfc822 &lt;/code&gt;<br /> <br /> it was tied to Evolution, while &lt;code&gt;message/news&lt;/code&gt; was not tied to anything.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> as e.g. &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure new filetype with:<br /> <br /> &lt;pre&gt;xdg-mime default claws-select.desktop message/rfc822<br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;$ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> Checking /home/gour/.config/mimeapps.list<br /> claws-select.desktop<br /> &lt;/pre&gt;<br /> ==== Testing ====<br /> <br /> Now you can also try whether you can open mail/news messages with xdg-open in your terminal.<br /> <br /> Finally, after you create task #xyz within Claws-mail, you should be able to see it within Taskwarrior --- filter with e.g. &lt;code&gt;+inbox +email&lt;/code&gt; and then you should be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you should see it it higlighted in Claws-mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3185 Using Claws Mail with other programs 2021-10-11T13:11:24Z <p>Claws: /* How to integrate Claws-mail with Taskwarrior? */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;<br /> <br /> === Integrating Claws-mail with Taskwarrior ===<br /> <br /> ==== System Requirements ====<br /> <br /> You need Claws-mail and Taskwarrior installed, then [https://github.com/GothenburgBitFactory/tasklib Tasklib] package as well as [https://github.com/jschlatow/taskopen Taskopen].<br /> <br /> ==== Integration scipt ====<br /> <br /> In order to integrate Claws-mail &amp;amp; Taskwarrior I modified the [https://github.com/alkim0/task-attach/blob/master/bin/mutt2task mutt2task] script from task-attach project and you have to put it somewhere in your &lt;code&gt;PATH&lt;/code&gt;.<br /> <br /> I named it as &lt;code&gt;claws2task&lt;/code&gt;.<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;#!/usr/bin/env python3<br /> <br /> &amp;quot;&amp;quot;&amp;quot; <br /> Creates a new task with the given message's filename as annotation attachment.<br /> &amp;quot;&amp;quot;&amp;quot;<br /> <br /> import email<br /> import sys<br /> <br /> from tasklib import TaskWarrior, Task<br /> <br /> <br /> def get_task_description(message):<br /> description = 'claws: &amp;quot;{}&amp;quot;'.format(message['subject'])<br /> return description <br /> <br /> <br /> def main():<br /> try:<br /> file_name = sys.argv[1]<br /> fp = open(file_name)<br /> message = email.message_from_file(fp)<br /> desc = get_task_description(message)<br /> tw = TaskWarrior(data_location='~/task', create=False)<br /> tw.overrides['gc'] = '0'<br /> task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> task.add_annotation(str(file_name))<br /> except Exception as e:<br /> print(e)<br /> sys.exit(2)<br /> <br /> if __name__ == &amp;quot;__main__&amp;quot;:<br /> main()<br /> &lt;/pre&gt;<br /> ==== Tagging Messages ====<br /> <br /> &lt;pre class=&quot;Python&quot;&gt;task = Task(tw, description=desc, tags=['inbox','email'])<br /> task.save()<br /> &lt;/pre&gt;<br /> I want that every task created from within Claws-mail gets two tags: &lt;code&gt;+inbox&lt;/code&gt; and &lt;code&gt;+email&lt;/code&gt; and get annotated with the link to open it from Taskwarrior. Moreover, task's descriptions is message's &lt;code&gt;Subject&lt;/code&gt; prepended with &lt;code&gt;claws:&lt;/code&gt;, so you're free to adjust it according to Your preferences.<br /> <br /> ==== Adding User Action to Claws-mail ====<br /> <br /> Now one needs to add the folowing action as shell command to Claws-mail which I put on the Toolbar and named Taskwarrior:<br /> <br /> &lt;code&gt;/path/to/the/script/claws2task %f&lt;/code&gt;<br /> <br /> Now clicking on certain mail or news (NNTP) message should create a new Taskwarrior task.<br /> <br /> ==== MIME Setup ====<br /> <br /> In order to be able to (task)open the message in Claws-mail, we need to configure it for &lt;code&gt;xdg-open&lt;/code&gt;.<br /> <br /> If you query some mail/news message with e.g.<br /> <br /> &lt;code&gt;xdg-mime query filetype ~/.claws-mail/imapcache/some/mail/account/INBOX/12345&lt;/code&gt;<br /> <br /> you should get:<br /> <br /> &lt;code&gt;message/rfc822 &lt;/code&gt;for IMAP and &lt;code&gt;message/news&lt;/code&gt; for NNTP messages.<br /> <br /> Now, when i was checking default association on my system with:<br /> <br /> &lt;code&gt;xdg-mime query default message/rfc822 &lt;/code&gt;<br /> <br /> it was tied to Evolution, while &lt;code&gt;message/news&lt;/code&gt; was not tied to anything.<br /> <br /> ===== System Integration =====<br /> <br /> Create the following file:<br /> <br /> &lt;pre&gt;[Desktop Entry]<br /> Version=1.0<br /> Type=Application<br /> Name=Claws-mail Select Handler<br /> Comment=Claws-mail integration with Taskwarrior<br /> Icon=applications-other<br /> Exec=claws-mail --select %u<br /> MimeType=x-scheme-handler/claws-select;<br /> &lt;/pre&gt;<br /> as e.g. &lt;code&gt;~/.local/share/applications/claws-select.desktop&lt;/code&gt; and then configure new filetype with:<br /> <br /> &lt;pre&gt;xdg-mime default claws-select.desktop message/rfc822<br /> xdg-mime default claws-select.desktop message/news<br /> &lt;/pre&gt;<br /> Check that everything is OK with:<br /> <br /> &lt;pre&gt;$ env XDG_UTILS_DEBUG_LEVEL=10 xdg-mime query default message/rfc822<br /> Checking /home/gour/.config/mimeapps.list<br /> claws-select.desktop<br /> &lt;/pre&gt;<br /> ==== Testing ====<br /> <br /> Now you can also try whether you can open mail/news messages with xdg-open in your terminal.<br /> <br /> Finally, after you create task #xyz within Claws-mail, you should be able to see it within Taskwarrior --- filter with e.g. &lt;code&gt;+inbox +email&lt;/code&gt; and then you should be able to issue:<br /> <br /> &lt;code&gt;$ task open #xyz &lt;/code&gt;<br /> <br /> and you should see it it higlighted in Claws-mail.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3182 Oauth2 2021-07-22T17:24:01Z <p>Claws: </p> <hr /> <div>----------------------------------------<br /> Setting up OAuth 2.0 for Gmail<br /> ----------------------------------------<br /> Follow the instructions here:<br /> https://support.google.com/googleapi/answer/6158849<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Project status: In production<br /> User type: External<br /> <br /> OAuth consent screen settings:<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> Scopes settings:<br /> Under restricted scopes select: Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail<br /> <br /> Getting the ClientID<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> <br /> ---------------------------------------------<br /> Microsoft - for Outlook or Exchange<br /> ---------------------------------------------<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration&diff=3181 Installation and Configuration 2021-07-02T14:22:08Z <p>Claws: /* What do I need to compile Claws Mail? */</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+ 3.20.x''' or later ''OR'' '''GTK+ 2.24.x''' or later (''depending on which version you are building'')<br /> ; A recent ANSI C compiler (gcc 2.7.2.3 should also work) <br /> <br /> Otherwise ./configure will fail.<br /> <br /> &lt;u&gt;Optional requirements:&lt;/u&gt;<br /> <br /> ; compface : for X-Face support<br /> ; GnuPG 1.2.1 or later and GPGME 0.4.5 or later : for GnuPG support (see [[Installation_and_Configuration#How_do_I_enable_GPG_support_in_Claws_Mail.3F|How do I enable GPG support in Claws Mail?]])<br /> ; GnuTLS 2.2 or later : for SSL/TLS support<br /> ; libEtPan! 0.57 or later : for IMAP4 support and NNTP support<br /> ; OpenLDAP 2.0.7 or later : for LDAP support<br /> ; Enchant (and dictionaries) : for spell-checker support<br /> ; J-Pilot : for J-Pilot support<br /> ; D-Bus : for interprocess communication support<br /> ; Network Manager : for support for detection of network connection changes<br /> <br /> === How to build Claws Mail on Mac OS X? ===<br /> <br /> The steps to build Claws Mail on Mac OS X have been originally posted by Damien Krotkine, on his dedicated page and his former post to his blog. None of them are avaliable anymore. The procedure below is based on his work.<br /> There's an additional [https://lists.claws-mail.org/pipermail/users/2012-September/003648.html procedure posted on users list] by Stainless Steel Rat.<br /> <br /> &lt;u&gt;Compiling against X.org&lt;/u&gt;<br /> <br /> Installing Claws Mail will require X.org, GTK+ 2.6, and a working POSIX building environment (including the gcc/make toolchain). Let's consider using Fink to install the software requirements on your Mac OS X system.<br /> <br /> Install Fink (http://www.finkproject.org/).<br /> <br /> Download and unpack the Claws Mail sources.<br /> <br /> Run &lt;code&gt;./configure --prefix=/sw&lt;/code&gt; to quickly see what packages are missing, and install them using Fink (&lt;code&gt;fink&lt;/code&gt; or &lt;code&gt;FinkCommander&lt;/code&gt;). Some of the required packages are available in unstable only, so you might need to enable unstable packages in the Fink prefs, then do &lt;code&gt;fink selfupdate scanpackages&lt;/code&gt;. You'll need a complete gcc/make toolchain as well as few extra requirements:<br /> &lt;pre&gt;<br /> xorg (binary)<br /> pkgconfig (binary)<br /> glib2-dev (compiled from source - we recommend &gt;=2.10 from unstable)<br /> gtk+2-dev (compiled from source - must be &gt;=2.6 from unstable)<br /> &lt;/pre&gt;<br /> <br /> Getting IMAP support in Claws Mail requires libetpan, but there is no Fink package for it. Darwin ports provide one, but let's compile it from source directly. Get the tarball from the etpan homepage (http://sourceforge.net/projects/libetpan). Unpack it, and compile the sources with:<br /> &lt;pre&gt;<br /> % ./configure --prefix=/sw &amp;&amp; make &amp;&amp; sudo make install<br /> &lt;/pre&gt;<br /> <br /> If you need SSL support (for IMAP for instance), install openssl-dev, via Fink, but before that, make sure you enable &quot;Use unstable cryptography packages&quot; in the Fink preferences.<br /> <br /> You could also enable support for compface, libgnomeprint/libgnomeprintui, aspell, jpilot, gnupg and gpgme (&gt;=1.0.0) by installing the appropriate packages from Fink.<br /> <br /> If you want to compile any of the dillo-viewer, spamassassin or bogofilter plugins with Claws Mail 2.9.2, you have to apply this patch: http://www.mollux.org/projects/contrib/claws-mail/patches/pending/claws-mail-osx-build-core-plugins-rev1.diff into the Claws Mail sources directory. SpamAssassin can be installed from &lt;code&gt;cpan&lt;/code&gt; (see http://developer.apple.com/server/fighting_spam.html) or from the sources.<br /> <br /> Now configure the sources:<br /> &lt;pre&gt;<br /> % ./configure --prefix=/sw --disable-trayicon-plugin<br /> &lt;/pre&gt;<br /> <br /> If &lt;code&gt;./configure&lt;/code&gt; runs well, it should output something like this:<br /> &lt;pre&gt;<br /> claws-mail 2.9.2<br /> <br /> JPilot : yes<br /> LDAP : yes<br /> OpenSSL : yes<br /> iconv : yes<br /> compface : yes<br /> IPv6 : yes<br /> GNU/aspell : yes<br /> IMAP4 : yes<br /> Crash dialog : no<br /> Libgnomeprint : yes<br /> LibSM : no<br /> Manual : yes<br /> Plugins : dillo-viewer pgpinline pgpmime pgpcore bogofilter spamassassin<br /> Maemo build : no<br /> Config dir : .claws-mail<br /> The binary will be installed in /sw/bin<br /> &lt;/pre&gt;<br /> <br /> Now let's build Claws Mail:<br /> &lt;pre&gt;<br /> % make<br /> &lt;/pre&gt;<br /> <br /> And install it:<br /> &lt;pre&gt;<br /> % sudo make install<br /> &lt;/pre&gt;<br /> <br /> If everything compiled correctly, you should be able to run Claws Mail. You first need to start X: as we've installed the Fink X.org server, you have to run &lt;code&gt;startx&lt;/code&gt;, and now from within a &lt;code&gt;xterm&lt;/code&gt;, run &lt;code&gt;claws-mail&lt;/code&gt;.<br /> <br /> Most of the extra plugins can be installed: you'd need to download and unpack the extra plugin sources tarball and enter the commands below after entering any of the plugins directories you need.<br /> <br /> Available plugins:<br /> &lt;pre&gt;<br /> att_remover<br /> attachwarning<br /> cachesaver<br /> fetchinfo_plugin<br /> gtkhtml2_viewer (libgtkhtml2 required)<br /> mailmbox<br /> notification_plugin<br /> pdf_viewer (poppler &gt;=0.5.1 required)<br /> perl_plugin<br /> smime<br /> synce_plugin<br /> vcalendar<br /> &lt;/pre&gt;<br /> <br /> The following plugins can't be used yet:<br /> &lt;pre&gt;<br /> acpi_notifier (probably not applicable, plugin doesn't compile anyway)<br /> newmail (plugin won't load)<br /> rssyl (plugin will crash)<br /> &lt;/pre&gt;<br /> <br /> Commands to build and install a plugin:<br /> &lt;pre&gt;<br /> % ./configure --prefix=/sw &amp;&amp; sudo make install<br /> &lt;/pre&gt;<br /> <br /> === How do I set up Claws Mail? ===<br /> <br /> When you run Claws Mail for the first time, the Installation Wizard will appear and prompt you for the minimum required information necessary to start using Claws Mail in less than 5 minutes.<br /> <br /> === Why did the creation of the mailbox fail? ===<br /> <br /> Claws Mail reports such an error if it can't create the default mailboxes (inbox, outbox, etc ...). This can be because &lt;homedir&gt;/Mail already contains files with the same names. This occurs when switching from Kmail to Claws Mail, in this case backup and remove the existing Mail directory or use another name for the Claws Mail mail directory.<br /> <br /> === How do I create a new account? ===<br /> <br /> You can add an account by using the menu item '/Configuration/Create new account'<br /> <br /> === Why does Claws Mail not delete my mails when I press &quot;delete&quot;? I set a filter, and Claws Mail does not filter. I moved a mail to a different mailbox and it did not move. ===<br /> <br /> You have the configuration option 'Execute immediately when moving or deleting messages' on the /Configuration/Preferences/Display/Summaries page disabled.<br /> <br /> === Can I set up special addresses/ports for my mailserver / newsserver? ===<br /> <br /> Yes, you can. In the Account preferences, on the 'Advanced' tab you can specify the port addresses that you want to use.<br /> <br /> === Does Claws Mail have options for threading messages? ===<br /> <br /> Yes. You can switch it on and off in the View Menu, just select &quot;Thread View&quot; or press Ctrl+T. (This only affects the currently selected folder; i.e. it is a folder property.)<br /> <br /> === Can I create multiple levels of subfolders to store mail? ===<br /> <br /> Absolutely. This is no problem.<br /> <br /> 1. right-click on an existing folder<br /> <br /> 2. choose 'Create new folder ...' from the resulting menu<br /> <br /> 3. type in a name for your new folder (you can check 'inherit properties from parent folder' if you want to do that)<br /> <br /> === How do I apply a patch after downloading it? ===<br /> <br /> Copy patch to Claws Mail directory Apply the patch:<br /> &lt;pre&gt;&lt;nowiki&gt;<br /> % patch -p0 &lt; some.patch<br /> &lt;/nowiki&gt;&lt;/pre&gt;<br /> Or, if it's gzipped:<br /> &lt;pre&gt;&lt;nowiki&gt;<br /> % gzip -dc some.patch.gz | patch -p0<br /> &lt;/nowiki&gt;&lt;/pre&gt;<br /> <br /> Run &lt;code&gt;./autogen.sh [OPTIONS]&lt;/code&gt;, then &lt;code&gt;make&lt;/code&gt;.<br /> <br /> === How do I compile in support for compface pictures? ===<br /> <br /> You have to have a package called libcompface installed, so this is available for compiling into Claws Mail. You can find out more and download it at http://freshmeat.net/projects/compface/ . Also, Tim Jackson has a spec file, which you can use to build an RPM of compface, at http://www.timj.co.uk/linux/rpms.php .<br /> <br /> === How do I make my own compface image? ===<br /> <br /> You can use the gif2xface.pl script, which converts a 48x48 gif to the format suitable for compface. This script can be found in the 'tools' directory, along with a README. It is also available from this site: https://www.claws-mail.org/tools.php.<br /> You can also let Claws Mail create it by itself from a .xbm file.<br /> <br /> Or, if that doesn't work.<br /> <br /> 1. Find/create 48x48 image, png works well.&lt;br&gt;<br /> 2. Convert it to pbm without dither (this also makes it black and white: convert -dither image.png image.pbm&lt;br&gt;<br /> 3. Convert the pbm to icon: pbmtoicon image.pbm &gt; image.icon&lt;br&gt;<br /> 4. Edit the icon file in a text editor. Delete any comment at the beginning, and put the values in colums of three with comma separation like so:<br /> <br /> 0xfoo, 0xfoo, 0xfoo,<br /> <br /> 5. The final line shouldn't have a comma ending it <br /> <br /> 0xfoo, 0xfoo, 0xfoo<br /> <br /> 6. Make certain there are exactly 48 lines and save.&lt;br&gt;<br /> 7. Run compface on it: compface &lt;image.icon&gt; image.xface&lt;br&gt;<br /> 8. Then follow the instructions below.<br /> <br /> Or you can take the super easy way out and just use this website:<br /> <br /> http://www.dairiki.org/xface/<br /> <br /> === How can I make Claws Mail send my compface image in the mails? ===<br /> <br /> On the Send page of the Account preferences check 'Add user-defined header' and press the 'Edit' button. In the dialogue that appears, add a header named &quot;X-Face&quot; and fill the value field with your face data. Alternatively, you can select a .xbm file in this dialog. Note that if you paste the data from a terminal into the field some spurious newlines can be added, and these can mangle your face, be careful.<br /> <br /> === How can I make Claws Mail send a colour Face image in the mails? ===<br /> <br /> Face headers contain base64-encoded 48x48 PNG image, and don't have any external dependency at compile-time or at run-time. You'll find more details here:<br /> http://quimby.gnus.org/circus/face/<br /> <br /> Once you have your .png file that complies to the specs of the Face header (max length 725 bytes), go to the Send page of the Account preferences, check 'Add user-defined header' and press the 'Edit' button. In the dialogue that appears, add a header named &quot;Face&quot; and click the 'From file' button to select your .png file.<br /> <br /> Note: there's nothing that prevents you from having both a X-Face (see previous FAQ entry) and a Face header in your mails.<br /> <br /> === How do I make my own Face image? ===<br /> <br /> For a color face image, a simple command-line use is all that's needed:<br /> <br /> home:~$ djpeg my.jpg | ppmnorm | pnmscale -width 48 -height 48 | ppmquant 9 | pnmtopng &gt; my.png<br /> <br /> The number after 'ppmquant' can be changed as needed until you have an image that is as close to 725 bytes as possible. It cannot be larger than 725 bytes.<br /> <br /> === How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program? ===<br /> <br /> In the settings part of the program, use &lt;code&gt;claws-mail --compose &quot;%t?subject=%s&amp;body=%d&quot;&lt;/code&gt;<br /> <br /> ; Specific options for typical browsers :<br /> ; Firefox 3<br /> In Firefox go to /Edit/Preferences/Applications. Search for 'mailto'. Under 'Action', select 'Use other...', and locate and select the 'claws-mail' executable, (typically /usr/bin/claws-mail or /usr/local/bin/claws-mail).<br /> ; Firefox 2<br /> Enter 'about:config' in the address bar.<br /> Add or Edit the following values:<br /> &lt;pre&gt;network.protocol-handler.external.mailto : default : boolean : true<br /> network.protocol-handler.app.mailto : user set : string : claws-mail&lt;/pre&gt;<br /> ; Opera:<br /> &lt;pre&gt;claws-mail --compose &lt;nowiki&gt;mailto:%t?[subject=%s&amp;][body=%m]&lt;/nowiki&gt;&lt;/pre&gt;<br /> ; Galeon:<br /> &lt;pre&gt;claws-mail --compose &lt;nowiki&gt;&quot;mailto:%t?subject=%s&amp;body=%d&quot;&lt;/nowiki&gt;&lt;/pre&gt;<br /> ; Konqueror : See [[Installation_and_Configuration#konqueror|How do I make Claws Mail the default mail application for KDE]]?<br /> <br /> === How do I enable GPG support in Claws Mail? ===<br /> <br /> GunPG support requires GnuPG &gt;= 0.4.x and GPGME &gt;= 1.x.x.<br /> <br /> Caution: according to some user experience, you might need to install GnuPG 1.x and GPGME 1.x.x in a separate location (isolated from the system ones), and to make sure GPGME is configured to use this specific GnuPG binary (`configure --prefix=/path/to/the/isolated/gpg1 --with-gpg=/path/to/the/isolated/gpg1/bin/gpg`). This is at least the case on RHEL6 and variants (SL6/CentOS6, Fedora 11+, probably RHEL5 and variants too), who come with GnuPG2 only, and where GPGME is configured to use `/usr/bin/gpg2` (see `gpgme-config --get-gpg`)- so it's useless on these systems to install GnuPG 1.x in system paths and to make sure the `gpg` found on the PATH points to the real GnuPG 1 version. Once this is done, GnuPG 1 and system's GnuPG 2 can both work fine with user's .gnupg/ config (GnuPG 1/2 are designed to do so). You'll need to update your environment where PATH and LD_LIBRARY_PATH must point to /path/to/the/isolated/gpg1 subdirectories prior to start `claws-mail`.<br /> <br /> You need to load the PGP/Core, PGP/MIME, and PGP/inline plugins. '/Configuration/Plugins/Load plugin'.<br /> <br /> === Mutt does not recognize Claws Mail's MH structure ===<br /> <br /> For this to work you need to use the &lt;code&gt;touch&lt;/code&gt; command in every MH folder. &lt;code&gt;touch&lt;/code&gt; the file &lt;code&gt;.xmhcache&lt;/code&gt; and Mutt should do just fine.<br /> <br /> === How can I make Claws Mail notify me when new mail arrives? ===<br /> <br /> Go to '/Configuration/Preferences/Common', on the 'Receive' tab use the settings for 'Run command when new mail arrives'. You can also use the Acpi-notifier (if you have a supported laptop) or the Notification plugin, which are available on the [https://www.claws-mail.org/plugins.php Plugins page].<br /> <br /> === Can I use a spell checker with Claws Mail? ===<br /> <br /> Install Enchant (with dictionaries) and run &lt;code&gt;./configure&lt;/code&gt;<br /> <br /> === I checked out the sources using git and cant find any configure script. What can I do? ===<br /> <br /> The git versions are meant to be used by developers rather than ''normal'' users, so the source (or binary) distributions are easier to use.<br /> <br /> - Yeah, but the latest features from git really look sexy...<br /> <br /> You need to generate the configure script by running &lt;code&gt;./autogen.sh&lt;/code&gt;. Building from git requires a lot of extra dependencies that the release tarballs don't have.<br /> <br /> === Running &quot;autogen.sh&quot; gives errormessages that AM_PATH_GDK_PIXBUF or AM_PATH_(whatever) is not found. What can I do? ===<br /> <br /> There are some *.m4 files in the &lt;code&gt;ac/missing&lt;/code&gt; directory. Try to copy them into the &lt;code&gt;ac&lt;/code&gt; directory and run &lt;code&gt;autogen.sh&lt;/code&gt; again.<br /> <br /> If there are still some .m4 files not found (e.g. those from Gtk), try to run<br /> % locate m4 | less<br /> or<br /> % locate aclocal | less<br /> to find additional directories containing those macros. If you find e.g. a &quot;gtk.m4&quot; in &quot;/opt/gnome/share/aclocal&quot;, change following line in &quot;autogen.sh&quot; from<br /> aclocal -I ac \<br /> to<br /> aclocal -I ac -I /opt/gnome/share/aclocal \<br /> and run it again.<br /> <br /> === I dont want to compile in support for ... any longer, but after running &lt;code&gt;configure&lt;/code&gt;, those libraries are still used. What can I do? ===<br /> <br /> Remove the &lt;code&gt;config.cache&lt;/code&gt; file and run &lt;code&gt;configure&lt;/code&gt; again. You should also use &lt;code&gt;make clean&lt;/code&gt; to avoid undefined references.<br /> <br /> === How can I select different applications to open with specific MIME types? ===<br /> <br /> The MIME-type-&gt;application associations are kept in &lt;code&gt;~/.mailcap&lt;/code&gt; and &lt;code&gt;/etc/mailcap&lt;/code&gt;.<br /> <br /> === How can I change the suggested mimetype for attachments I am sending? ===<br /> <br /> The extension-&gt;MIME-type associations are kept in either &lt;code&gt;/usr/share/mime/globs&lt;/code&gt; or &lt;code&gt;/etc/mime.types&lt;/code&gt;, depending on your system. &lt;br&gt;Right-click an attachment in the compose window's &quot;Attachments&quot; tab, and select Properties to change the MIME-type.<br /> <br /> === Why is the folder list not updated after I manually moved/copied folders? ===<br /> <br /> You need to update Claws Mail's cache. Right click on the mailbox and choose &quot;Check for new folders&quot;.<br /> <br /> === How can I revert original settings, e.g. for fonts, keybindings, etc.? ===<br /> <br /> Claws Mail keeps its configuration files in &lt;code&gt;$HOME/.claws-mail/clawsrc&lt;/code&gt; and creates default entries, if none are found. So the easiest way is to quit claws-mail, temporarily renaming your &lt;code&gt;$HOME/.claws-mail&lt;/code&gt; e.g. to &lt;code&gt;*.bak&lt;/code&gt; and restarting claws-mail in order to get default entries.<br /> <br /> === What environment variables have effect on Claws Mail? ===<br /> <br /> ; Here are the most common variables : <br /> ; HOME : location of .claws-mail (config directory) and default folder for Mailboxes.<br /> ; LANG<br /> ; LC_ALL<br /> ; LC_CTYPE<br /> ; LC_MESSAGES : locale settings, e.g. language and date format.<br /> <br /> For a more detailed list see manual page (man claws-mail).<br /> <br /> === Why are special characters (e.g. umlauts) not displayed correctly? ===<br /> <br /> In most cases, this is caused by emails with broken encodings. You can try to force it using the View/Character Encoding submenu.<br /> <br /> === How can I convert my old mailbox / addressbook from (some mail client). ===<br /> <br /> If you can export your old mailbox to &lt;code&gt;MH&lt;/code&gt; or &lt;code&gt;mbox&lt;/code&gt; format it can be imported directly into Claws Mail. If the mailbox is in &lt;code&gt;MH&lt;/code&gt; format you can use /File/Add Mailbox/MH... If the mailbox is in &lt;code&gt;mbox&lt;/code&gt; format, it can be imported with /File/Import mbox file/...<br /> <br /> The Claws Mail addressbook supports direct import from Mutt, Pine, and LDIF and vCard formats, which are standard formats exported by most email clients.<br /> <br /> In addition, several scripts are provided on the Claws Mail [https://www.claws-mail.org/tools.php website] to convert various mailbox and addressbook formats.<br /> <br /> If your old addressbook only supports CSV export, and it is not supported by the &lt;code&gt;csv2addressbook.pl&lt;/code&gt; script on the [https://www.claws-mail.org/tools.php website], you can convert it to vCard format using this [http://homepage.mac.com/phrogz/CSV2vCard_v2.html online tool]. Another [http://labs.brotherli.ch/vcfconvert/ online tool] can convert from vCard to LDIF format.<br /> <br /> === What configuration files are there, and what are they used for? ===<br /> <br /> The default location for Claws Mail's configuration files is &lt;code&gt;$HOME/.claws-mail/&lt;/code&gt;. (The command '&lt;code&gt;claws-mail --config-dir&lt;/code&gt;' shows the location.) They are in plain text format and quite easy to understand, so don't fear to take a look into them using a text editor.<br /> <br /> ; clawsrc : main configuration: nearly all options from the settings window, e.g. mailbox location, font entries, etc.<br /> ; accountrc : settings for POP/IMAP/NNTP/local accounts<br /> ; actionsrc : user defined actions<br /> ; customheaderrc : user defined header lines<br /> ; dispheaderrc : headers to display above the mail body<br /> ; folderitemrc : folder specific settings<br /> ; folderlist.xml : additional folder specific settings, e.g. hiding read messages, sort order, etc.<br /> ; matcherrc : filtering, processing and scoring settings<br /> ; menurc : Key bindings<br /> ; addrbook/addrbook-*.xml : contents of your address book (before version 3.1.0 the address book files were kept directly in &lt;code&gt;.claws-mail/&lt;/code&gt;)<br /> <br /> === What's a good method for printing an e-mail? ===<br /> Primarily, using the /File/Print menu item.<br /> <br /> An alternative: Use [http://muttprint.sf.net muttprint]. The print-command would then look something like this: &lt;code&gt;muttprint -f %s&lt;/code&gt;<br /> <br /> Using KDE or gv you also get a &quot;print preview&quot; for free! <br /> <br /> Try &lt;code&gt;muttprint -f %s -p - |kghostview -&lt;/code&gt; or &lt;code&gt;muttprint -f %s -p - |gv -&lt;/code&gt; respectively... BTW: muttprint, like enscript, may optionally print two logical pages on one physical page. Just have a look at the docs!<br /> <br /> === Claws refuses to send mail, and says the queue folder cannot be found ===<br /> <br /> This problem happens for people using only IMAP accounts.<br /> Claws Mail requires a queue folder for outgoing mail. If there is none, it will display an error message (&quot;can't find queue folder&quot;) and refuse to send mail.<br /> This feature prevents loss of messages, in the case Claws Mail would be killed while sending an e-mail, or should there be a network problem. It provides extra security against data loss.<br /> <br /> You are advised to create a local folder (/File/Add Mailbox/MH). Outgoing messages will be queued there, and sending will work.<br /> <br /> You can also decide not to use a local folder for the queue, and use the IMAP server for this. It is not recommended because Claw Mail's queued messages have a special header that might not be handled correctly by the IMAP server. <br /> If you really want to create a queueing folder in an IMAP server, create an ordinary folder in it. Right click on it, select /Properties/, and change /Type/ to be &quot;Queue&quot;.<br /> (Might be unneeded : Go to /Configuration/Edit accounts/, select your account, click /Edit/, click /Advanced/. On this screen you can tick /Put queued messages in/ and select the folder you have created.)<br /> <br /> === What is the purpose of this bizarre &quot;Enable Alternate Dictionary&quot; option? ===<br /> <br /> It is useful only if you routinely compose messages that use two or more languages. If this option is enabled, then when you switch to another language, the last one you used is not swapped out from memory, thus, when you switch again to it, there is no delay. Moreover, whenever you use two dictionaries, if you check a word and if the spell checker considers it misspelled in the current language, you can switch to the alternate language and recheck the word in one operation by selecting the &quot;Check with ALTERNATE_LANGUAGE&quot; item (keyboard short-cut: &lt;x&gt;) in the suggestions menu. This is very handy when the message contains paragraphs in two languages.<br /> <br /> === Why doesn't the spell checker have a more traditional user interface, like KMail, Evolution etc? ===<br /> <br /> Because the developer (Melvin Hadasht) noted that by using the keyboard shortcuts the spell checking can be done faster while typing (more on that below). Moreover, there is the option &lt;Spelling/Check All or Check selection&gt; allows to do a spell checking of the whole text or just a selection. Just keep an eye where the suggestions menu shows up to look at the misspelled word, then hit one of the letters corresponding to the suggestion (&amp;lt;a&amp;gt; through &amp;lt;p&amp;gt;, press also &lt;ALT&gt; to make the selected suggestion listed as the first suggestion the next time you do exactly the same mistake --- this is the &quot;learn by mistake&quot; feature), or hit &lt;r&gt; to type a replacement, or hit &lt;ALT-SPACE&gt; to accept the word in the current message, or hit &lt;ALT-RETURN&gt; to accept the word and to add it definitively to your personal dictionary associated to this language. If you have enabled the &quot;Alternate Dictionary&quot;, you can switch to it by hitting &lt;x&gt;.<br /> <br /> If you prefer checking while you type, just bind the &lt;Spelling/Check backwards misspelled word&gt; and &lt;Spelling/Forward to next misspelled word&gt; to two quick keyboard short cuts. Then, as soon as you mistype a word, call the &lt;Check backwards...&gt; short-cut ---you do not need to move the cursor--- and without using the mouse select the suggestion. As Enchant does a good job at suggesting a replacement, you will often end to type &lt;a&gt;, and as the cursor did not move, just continue typing. In contrast, the other option, &lt;Forward to next...&gt; does move the cursor. This is because if you have text after the cursor, that also means in general that you are only editing a message, and not writing it, so advancing the cursor to the misspelled word is in general the wanted behaviour.<br /> &lt;div id=konqueror&gt;<br /> <br /> === How do I make Claws Mail the default mail application for KDE? ===<br /> <br /> KDE does not support passing the full URL to a mailer (see [http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=658 bug 658] and the corresponding [http://bugs.kde.org/show_bug.cgi?id=81598 KDE bug entry]).<br /> But there is a workaround - do the following as root:<br /> &lt;pre&gt;<br /> wget https://www.claws-mail.org/tools/claws-mail-compose.pl<br /> mv claws-mail-compose.pl /usr/local/bin<br /> chmod +x /usr/local/bin/claws-mail-compose.pl<br /> &lt;/pre&gt;<br /> Then go to the KDE Control Center -&gt; KDE Components -&gt; Component Chooser -&gt; Email Client, choose &quot;Use a different email client&quot; and enter the following into the textbox:<br /> &lt;pre&gt;<br /> /usr/local/bin/claws-mail-compose.pl --to=&quot;%t&quot; --cc=&quot;%c&quot; --bcc=&quot;%b&quot; --subject=&quot;%s&quot; --body=&quot;%B&quot; --attach=&quot;%A&quot;<br /> &lt;/pre&gt;<br /> <br /> If your binary has a name other than &quot;claws-mail&quot;, you must append another parameter:<br /> &lt;pre&gt;<br /> --claws-mail=&quot;/usr/bin/claws-mail&quot;<br /> &lt;/pre&gt;<br /> where /usr/bin/claws-mail is the full path to claws-mail on your system.<br /> <br /> In case you don't want that perlscript or you can't use it - there is this alternative. But be aware that passing multiple lines or non-standard characters to Claws Mail from an application (e.g. konqueror trying to send form-data via email) will '''not''' work!<br /> &lt;pre&gt;<br /> claws-mail --compose &lt;nowiki&gt;&quot;~mailto:%t?cc=%c&amp;bcc=%b&amp;subject=%s&amp;body=%B&quot; --attach &quot;%A&quot;&lt;/nowiki&gt;<br /> &lt;/pre&gt;<br /> Replace &quot;claws-mail&quot; with the actual name of your binary here as well.<br /> &lt;/div&gt;<br /> <br /> === Why does Claws Mail tell me that a gpg signature has expired? ===<br /> <br /> The sender used a key with a time limit, you have to update your keyring regularly to receive the updated signatures, e.g. like this: <br /> <br /> &lt;code&gt;gpg --refresh-keys&lt;/code&gt;<br /> <br /> Note: Most keyservers have problems syncing OpenPGP type keys (see http://keyserver.kjsl.com/~jharris/keyserver.html). It is recommended to switch to SKS keyservers, e.g. subkeys.pgp.net or sks.keyserver.penguin.de .<br /> <br /> <br /> === Why does Claws Mail tell me that there is one unread message in some folders? ===<br /> <br /> If the message count in a folder indicates that you have one unread message but all are marked as read you have to do the following: Right click on toplevel MH folder and use &quot;Check for new messages&quot;, or use '/View/Update Summary'<br /> <br /> === How can I use my free Hotmail, Yahoo, or AOL email account via Claws Mail? ===<br /> <br /> [http://www.freepops.org/en/ FreePOPs] should allow you to create kind of a &quot;bridge&quot; between these proprietary email services and Claws Mail. Simply install FreePOPs, which is probably packaged in your distribution and configure it. After that, you can add an POP3 account to Claws Mail, which receiving server will be &lt;code&gt;localhost&lt;/code&gt; and set the port to use to &lt;code&gt;2000&lt;/code&gt; in the Advanced tab. The username to use consists of a complete email address, like &lt;code&gt; johndoe@hotmail.com&lt;/code&gt;, so that FreePOP can know which type of account it is. For more information, see [http://www.freepops.org/en/files/html-manual/ FreePOPs' user manual].<br /> <br /> === Does Claws Mail work with Gmail accounts? ===<br /> <br /> Yes, provided that you have enabled POP or IMAP access in your Gmail account.<br /> <br /> See:&lt;br&gt;<br /> all about POP access: http://gmail.google.com/support/bin/topic.py?topic=12805&lt;br&gt;<br /> enabling POP in Gmail: http://gmail.google.com/support/bin/answer.py?answer=13273&lt;br&gt;<br /> configure other email client for POP access: http://mail.google.com/support/bin/answer.py?answer=13287&lt;br&gt;<br /> <br /> all about IMAP access: http://gmail.google.com/support/bin/topic.py?topic=12806&lt;br&gt;<br /> enabling IMAP in Gmail: http://gmail.google.com/support/bin/answer.py?answer=77695&amp;topic=13294&lt;br&gt;<br /> configure other email clients for IMAP access: http://mail.google.com/support/bin/answer.py?hl=en&amp;answer=78799&lt;br&gt;<br /> <br /> Information about using Claws with Gmail effectively: https://www.claws-mail.org/faq/index.php?title=Using_Claws_with_Gmail<br /> <br /> === Claws Mail doesn't retrieve emails from my Gmail (POP3) account. Sending messages doesn't work either. What can I do? ===<br /> <br /> Try prefixing your user name, which is usually your email address, with 'recent:' (without the quotes).<br /> <br /> Also make sure that under the 'Send' tab of your Claws Mail Account settings , the 'Authenticate with POP3 before sending' option is turned off.<br /> <br /> Finally, be aware that if the 'Remove messages on server when received' option is set in the 'Receive' tab of your Claws Mail Account, when you retrieve your messages they will be removed from the Gmail 'All emails' folder and they won't be available anymore from the Gmail web interface.<br /> <br /> === Can I have different mailboxes for my accounts even though they aren't IMAP or News? ===<br /> <br /> Yes, you can.<br /> <br /> Use File -&gt; Add mailbox -&gt; MH<br /> <br /> Then in the account preferences on the 'receive' tab set the inbox, on the 'advanced' tab set up the other folders.<br /> <br /> === How can I permanently delete messages? ===<br /> <br /> When you press the [del] key, the selected messages are moved to the Trash folder. You can, of course, empty the trash at any time by using the Trash folder's contextual menu.<br /> <br /> If, however, you want to permanently delete the message without moving it to trash, you have two options:<br /> ;Delete menu: First possibility is to select the /Message/Delete menu item in the main window, (to which you can assign a keyboard shortcut, like [shift+del]), or the message's context menu entry.<br /> ;Trash subfolder: If you systematically want to permanently delete messages from a folder, (for instance, your Junk folder that contains spam messages), you should create that folder as a subfolder of Trash. It will then inherit the behavior of the trash folder, and permanently delete messages when you press [del].<br /> <br /> <br /> === How can I compose email without internet connection (offline)? ===<br /> If you need to create email in offline (e.g. when you are travelling with your notebook and temporaly have no internet connection), you should do the following steps<br /> 1. Create MH mail box (File/Add mailbox) for local storage of messages.<br /> 2. At your account preferences, advanced-tab you should override &quot;put queued messages in&quot; and &quot;put queued draft in&quot; with folders of your MH mail box, e.g.<br /> #mh/local/queue<br /> #mh/local/draft<br /> <br /> When you compose your messages in offline mode, you should press &quot;send later&quot;, to put them into local queue. Entering online you press &quot;send&quot; button in main application screen to actually transmit them.</div> Claws https://www.claws-mail.org/faq/index.php?title=Oauth2&diff=3180 Oauth2 2021-07-02T10:00:13Z <p>Claws: Created page with &quot;---------------------------------------- Setting up OAuth 2.0 for Gmail ---------------------------------------- Follow the instructions here: https://support.google.com/cloud...&quot;</p> <hr /> <div>----------------------------------------<br /> Setting up OAuth 2.0 for Gmail<br /> ----------------------------------------<br /> Follow the instructions here:<br /> https://support.google.com/cloud/answer/6158849<br /> <br /> When setting up the project use these settings:<br /> Project name: Anything of your choice<br /> Project status: In production<br /> User type: External<br /> <br /> OAuth consent screen settings:<br /> App name: Anything of your choice<br /> User support email: Your own email<br /> Developer email: Your own email<br /> App domain entries: Leave blank<br /> <br /> Scopes settings:<br /> Under restricted scopes select: Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail<br /> <br /> Getting the ClientID<br /> APIs and Services on the left menu, then Credentials entry<br /> <br /> Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen.<br /> <br /> Select &quot;Edit Oauth Credentials&quot; (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.<br /> <br /> <br /> ---------------------------------------------<br /> Microsoft - for Outlook or Exchange<br /> ---------------------------------------------<br /> <br /> Sign in to microsoft account<br /> <br /> Go to Azure Active Directory &gt; App registrations<br /> <br /> Direct link: https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps<br /> <br /> Choose &quot;New Registration&quot;<br /> <br /> Display name: Anything you choose<br /> Application (client) ID - will be auto generated<br /> Object ID - will be auto generated<br /> Directory (tenant) ID - will be auto generated<br /> Supported account types - set to &quot;All Microsoft account users&quot;<br /> <br /> Once app is registered you can configure it:<br /> <br /> Branding tab - any entries you like<br /> <br /> Authentication tab -<br /> Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient<br /> Supported account types: &quot;Accounts in any organizational directory (Any<br /> Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)&quot;<br /> <br /> Certificates &amp; secrets tab - No entries needed<br /> <br /> Token configuration - No entries needed<br /> <br /> API permissions tab - Add these:<br /> <br /> Microsoft Graph:<br /> - IMAP.AccessAsUser.All<br /> - Mail.ReadWrite<br /> - Mail.Send<br /> - offline_access<br /> - POP.AccessAsUser.All<br /> - SMTP.Send<br /> <br /> Expose an API tab - No entries needed<br /> <br /> Owners tab - No entries needed<br /> <br /> Manifest tab - Leave at defaults<br /> <br /> Quickstart tab - Leave alone<br /> <br /> Integration assistant - Leave alone<br /> <br /> Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_other_programs&diff=3179 Using Claws Mail with other programs 2021-03-29T12:58:07Z <p>Claws: /* How can I use Claws Mail with mairix? */</p> <hr /> <div>=== How can I use Claws Mail with bogofilter? ===<br /> The simplest method is to use the Bogofilter plugin, see the [[Plugins]] FAQ Page for further information. If you use that plugin, the following will not be needed<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> First of all, make sure you have trained bogofilter; for different training methods, see [http://bogofilter.sourceforge.net/faq.shtml#training http://bogofilter.sourceforge.net/faq.shtml#training]. Method 4 is recommended, but requires a large number of ham and spam messages.<br /> <br /> Add a new filtering rule: you need a filtering condition which runs bogofilter on incoming messages; and an action that has to be performed if the message was recognised as spam.<br /> Go to the Filtering Configuration dialog, and type the following in the condition entry field:<br /> &lt;br&gt;<br /> &lt;pre&gt;test &quot;bogofilter -u &lt; %F&quot;&lt;/pre&gt;<br /> Note 1: this assumes that bogofilter is in your path!&lt;br&gt;<br /> Note 2: the -u parameter of bogofilter registers the message automatically as either spam or ham.<br /> <br /> Next add an action in the Action field. The best way is to use the Define... button next to the field. As an example, if you wanted to move a spam messages to a directory called Spam, then the final action, put in the field, could look like this:<br /> &lt;br&gt;<br /> &lt;pre&gt;move &quot;#mh/Mailbox/Spam&quot;&lt;/pre&gt;<br /> <br /> After having added the filtering rule you probably want to create two Claws Mail Actions: one for marking messages as spam, and one for marking messages as ham. These actions can be used to correct bogofilter and/or to train it with additional messages. For example, if the above filtering rule did not detect a spam message correctly, delivering it to your inbox, you can manually correct this by invoking a &quot;Mark As Spam&quot; action. As an added bonus, Actions are automatically added to the main menu (under Tools|Actions), and can also be added to the main toolbar.<br /> <br /> Open the Actions dialog (Configuration | Actions...). In the Menu name field, enter the following:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Spam&lt;/pre&gt;<br /> This is just the text as it would appear in the Tools|Actions submenu.<br /> <br /> The accompanying command line for Mark As Spam should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Ns -B %F&lt;/pre&gt;<br /> (Don't forget to use the Add button!)<br /> <br /> Likewise, the same thing you should do for marking messages as ham. Select &quot;New&quot; in the Current actions list, and enter the following in the Menu name:<br /> &lt;br&gt;<br /> &lt;pre&gt;Mark As Ham&lt;/pre&gt;<br /> <br /> The command line for this action should be:<br /> &lt;br&gt;<br /> &lt;pre&gt;bogofilter -Sn -B %F&lt;/pre&gt;<br /> And add the action by clicking the Add button.<br /> <br /> This gives you a basic setup for bogofilter and Claws Mail.<br /> <br /> === How can I use Claws Mail with Popfile? ===<br /> You can reclass messages received trough a Popfile filter with a header link or a button in Claws Mail.<br /> Popfile lives @ http://getpopfile.org/ <br /> <br /> First read the Popfile documentation on how to set up the mail client to use Popfile.<br /> <br /> You have 2 options to reclass received messages: a simple one (header link) and a difficult one (toolbar button).<br /> <br /> '''1) Simple method'''<br /> <br /> * Open the Popfile control center, go to the &quot;Buckets&quot; tab, and make sure ALL buckets have the ''X-POPFile-Link Header'' turned on.<br /> * Open Claws Mail preferences window, go to Message view -&gt; Text options.<br /> * Edit the header display options, in the &quot;Displayed header configuration&quot; dialog add ''X-POPFile-Link'' to the displayed headers.<br /> * All messages received via Popfile will have a header link (just above the message body) called ''X-POPFile-Link'', something like this: ''X-POPFile-Link: http://127.0.0.1:7070/jump_to_message?view=6491'' - you can click on it and Claws will open the link with the browser you set up in preferences.<br /> <br /> '''2) difficult method'''<br /> <br /> You will need 3 things:<br /> * a bash script<br /> * a Claws Mail action<br /> * change Popfile configuration a bit.<br /> <br /> '''The bash script:'''<br /> &lt;pre&gt;<br /> #!/bin/bash<br /> url=`cat $1 | grep -e X-POPFile-Link:.* -o|grep http.* -o`<br /> firefox $url<br /> &lt;/pre&gt;<br /> <br /> Save it as /some/path/popreclass.sh<br /> &lt;br&gt;''Change firefox to another browser executable if needed.''<br /> <br /> '''The action:'''<br /> &lt;br&gt;/some/path/popreclass.sh &quot;%f&quot;<br /> &lt;br&gt;''You can set up a toolbar buttor for the action later''<br /> <br /> '''Popfile configuration'''<br /> &lt;br&gt;Go to http://127.0.0.1:8080/configuration, and make sure the '''X-POPFile-Link Header''' option is turned '''ON'''.<br /> &lt;br&gt;''Your popfile URL might be different.''<br /> <br /> You will be able to reclass messages that were received with the above option turned ON.<br /> <br /> === How can I use Claws Mail with SpamAssassin? ===<br /> The simplest method is to use the SpamAssassin plugin, see the [[Plugins]] FAQ Page for further information.<br /> <br /> ===== Filtering/Actions method =====<br /> <br /> To train spamassassin in Claws Mail (&gt;=1.9.6):<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Spam&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --spam %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt;<br /> Menu &gt; Configuration &gt; Actions<br /> &lt;br&gt; In 'Menu Name' add &quot;Mark as Ham&quot;<br /> &lt;br&gt; In 'Command line' add &quot;sa-learn --ham %F&quot;<br /> &lt;br&gt; click the Add button<br /> &lt;br&gt; then select a message, &lt;b&gt;Menu Tools &gt; Actions&lt;/b&gt;<br /> will have the new actions to mark your email as Spam/Ham. Once you click one of the buttons spamassassin will process your request - this takes time so be patient and dont click on the 'cancel' button.<br /> <br /> Note:<br /> &lt;br&gt;<br /> If you want to have the mail learned on a remote mail server, that's possible with a 'Command line' like this:<br /> &lt;br&gt; <br /> ssh host.domain sa-learn --ham &lt; %f<br /> &lt;br&gt; <br /> It works best if you have already setup ssh to use keys for authentication.<br /> <br /> === How can I use Claws Mail with Mozilla? (not Firefox) ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;mozilla -remote &quot;openurl(%s,new-window)&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> <br /> === How can I use Claws Mail with Firefox? ===<br /> <br /> Go to Menu &gt; Configuration &gt; Preferences &gt; Message View &gt; External Programs<br /> <br /> and write<br /> &lt;br&gt;<br /> &lt;pre&gt;firefox --new-tab &quot;%s&quot;&lt;/pre&gt;<br /> into the &quot;Web Browser&quot; field.<br /> See [http://kb.mozillazine.org/Command_line_arguments Firefox's Command line arguments] for more information.<br /> <br /> See also: [https://www.claws-mail.org/faq/index.php?title=Installation_and_Configuration#How_can_I_tell_my_browser.2Fnewsclient.2Fother_program_to_use_Claws_Mail_as_e-mail_program.3F How can I tell my browser/newsclient/other program to use Claws Mail as e-mail program?]<br /> <br /> === How can I use Claws Mail with mairix? ===<br /> <br /> In addition to the quicksearch, that allows filtering out messages in folders<br /> recursively, you can use mairix in Claws Mail in order to perform message searches across a wide range of folders.<br /> <br /> To illustrate this topic, we'll detail the necessary steps to make a global search in a MH config (in our example, ~/Mail).<br /> <br /> - install mairix from https://github.com/rc0/mairix or get it from your packages repository. mairix is a program for indexing and searching email messages stored in Maildir, MH or mbox folders. We recommend to avoid using version 0.20 (0.17 to 0.19 are fine).<br /> <br /> - create a folder in Claws Mail where the search results will be stored in (in<br /> our example: ~/Mail/Search).<br /> <br /> - create a mairix config file (~/.mairixrc for instance):<br /> <br /> &lt;pre&gt;<br /> base=~/Mail<br /> mh=*...<br /> omit=draft:queue:trash:Junk:Search<br /> database=~/.mairix_db<br /> mfolder=Search<br /> mformat=mh<br /> &lt;/pre&gt;<br /> <br /> in that example, the base directory is ~/Mail, the search will be performed across all folders and sub-folders (mh=*...) in the base directory. Search will omit drafts, queue, trash, Junk and Search folders located in the base directory, and will place results into the Search folder. If you're in the search folder prior to starting the search, you'll have to select click &quot;View/Update summary&quot; to refresh the messages list.<br /> <br /> See `man mairix` for more information about the mairix configuration file.<br /> <br /> - add an action in Claws Mail to start the mairix search:<br /> <br /> &lt;pre&gt;<br /> &gt; ~/.claws-mail/tools/mairix.sh ~/.mairixrc<br /> &lt;/pre&gt;<br /> <br /> make sure that you've installed mairix.sh from the Tools pages (https://www.claws-mail.org/tools/claws-mail-mairix.tar.gz) into ~/.claws-mail/tools or wherever you want, provided that you set the correct path in the action text.<br /> <br /> Now call the action. You'll be asked for the text to search for. Search results - symlinks to the existing message files, will be placed into the target folder, making it like a virtual folder. Removing messages from that folder will NOT remove the original message files. The text to search for is an expression to pass to mairix. See `man mairix` for all search<br /> patterns.<br /> <br /> <br /> You can create as many mairix config files as you want (be sure that you set a different database value in each of them), then create the corresponding actions that call mairix.sh with the config filename in parameter.<br /> <br /> === How can I use Claws Mail with httppc? ===<br /> <br /> If you need to use Claws Mail behind an HTTP proxy that supports &quot;CONNECT&quot; method (RFC 2616), you may want to use [http://httppc.sourceforge.net/ httppc library]: it's a simple and fast way to achieve this goal.<br /> <br /> An step-by-step example of how to set up version 0.8.5 follows.<br /> <br /> First we need to get the source archive from the SourceForge repository and unpack it:<br /> &lt;pre&gt;<br /> wget &quot;http://downloads.sourceforge.net/project/httppc/httppc/0.8.5/httppc-0.8.5.tar.gz&quot;<br /> tar xzf httppc-0.8.5.tar.gz<br /> cd httppc-0.8.5<br /> &lt;/pre&gt;<br /> <br /> Then we run the configure script:<br /> &lt;pre&gt;<br /> sh ./configure<br /> &lt;/pre&gt;<br /> '''''Note:''''' By default, the package's files are installed in `/usr/local/bin', `/usr/local/man', etc. If you wish to specify another location for these files, you can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Please refer to the INSTALL file for further information.<br /> <br /> Finally we build and install it:<br /> &lt;pre&gt;<br /> make<br /> make check #optional<br /> make install<br /> &lt;/pre&gt;<br /> <br /> '''''Note:''''' You may encounter an error while compiling driver.c, stating <br /> &lt;pre&gt;<br /> driver.c: In function 'getaddrinfo':<br /> driver.c:557:13: error: 'EAI_NODATA' undeclared<br /> &lt;/pre&gt;<br /> In this case, just insert the &quot;-D_GNU_SOURCE&quot; option in the Makefile, for instance in the &quot;DEFS&quot; line:<br /> &lt;pre&gt;<br /> DEFS = -D_GNU_SOURCE -DHAVE_CONFIG_H -DCONF_SYS_WIDE=\&quot;$(DESTDIR)$(sysconfdir)/$(PACKAGE)rc\&quot;<br /> &lt;/pre&gt;<br /> <br /> We now need to edit the configuration a bit to make it fully functional:<br /> * First, the proxed shell script (located at /usr/local/bin/proxed by default). Define at least the $HTTP_PROXY variable.<br /> * Then the httppc configuration file (located at /usr/local/etc/httppcrc by default). Define at least the proxy parameter, and most probably the ldns parameter if you have a local DNS server behind the HTTP proxy as well.<br /> <br /> We should be all set. The script should be in our path and can be launched with<br /> &lt;pre&gt;<br /> proxed claws-mail<br /> &lt;/pre&gt;<br /> <br /> '''''Tip:''''' We can add a shell alias to launch typing less (example for ~/.bashrc):<br /> &lt;pre&gt;<br /> alias claws-mail=&quot;proxed claws-mail &amp;&quot;<br /> &lt;/pre&gt;</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_Gmail&diff=3178 Using Claws Mail with Gmail 2021-02-11T09:25:37Z <p>Claws: /* Claws Mail account setup */</p> <hr /> <div>== Gmail account setup ==<br /> In your Gmail settings, turn on &quot;Enable less secure app access&quot;. (Gmail's &quot;enable less secure app access&quot; is a euphemism for &quot;apps that don't support OAUTH2&quot;, it does not mean programs such as Claws Mail, are less secure.)<br /> <br /> You will also need to use [https://support.google.com/accounts/answer/185833?authuser=0 an App Password] to log in if using two factor authentication on your account.<br /> <br /> == Claws Mail account setup ==<br /> <br /> <br /> Open your account preferences, and make sure these options are set:<br /> <br /> ; on 'Basic' page<br /> : server for receiving: imap.gmail.com<br /> : SMTP server (send): smtp.gmail.com<br /> : User ID: [your complete gmail email address]<br /> <br /> ; on 'Receive' page<br /> : Authentication method: Automatic<br /> : IMAP server directory: [leave empty]<br /> <br /> ; on 'Send' page<br /> :[x] SMTP Authentication (SMTP AUTH)<br /> : Authentication method: Automatic<br /> <br /> ; on 'SSL/TLS' page<br /> : IMAP: Use SSL/TLS<br /> : Send (SMTP): Use STARTTLS command to start encrypted session<br /> <br /> ; on 'Advanced' page<br /> : SMTP port: 587<br /> : IMAP port: 993<br /> <br /> Set the [Gmail]/Trash folder as Folder Type 'Trash' on the General page of the folder Properties, so that emptying Trash really deletes the messages it contains.<br /> <br /> Additionally, as gmail cannot handle incremental saves to the Drafts folder, turn off 'Automatically save to Drafts folder every n characters' on the /Configuration/Preferences/Compose/Writing page.</div> Claws https://www.claws-mail.org/faq/index.php?title=Using_Claws_Mail_with_Gmail&diff=3176 Using Claws Mail with Gmail 2021-02-02T13:01:22Z <p>Claws: /* Claws Mail account setup */</p> <hr /> <div>== Gmail account setup ==<br /> In your Gmail settings, turn on &quot;Enable less secure app access&quot;. (Gmail's &quot;enable less secure app access&quot; is a euphemism for &quot;apps that don't support OAUTH2&quot;, it does not mean programs such as Claws Mail, are less secure.)<br /> <br /> You will also need to use [https://support.google.com/accounts/answer/185833?authuser=0 an App Password] to log in if using two factor authentication on your account.<br /> <br /> == Claws Mail account setup ==<br /> <br /> <br /> Open your account preferences, and make sure these options are set:<br /> <br /> ; on 'Basic' page<br /> : server for receiving: imap.gmail.com<br /> : SMTP server (send): smtp.gmail.com<br /> : User ID: [your complete gmail email address]<br /> <br /> ; on 'Receive' page<br /> : Authentication method: Automatic<br /> : IMAP server directory: [leave empty]<br /> <br /> ; on 'Send' page<br /> :[x] SMTP Authentication (SMTP AUTH)<br /> : Authentication method: Automatic<br /> <br /> ; on 'SSL/TLS' page<br /> : IMAP: Use SSL/TLS<br /> : Send (SMTP): Use STARTTLS command to start encrypted session<br /> <br /> ; on 'Advanced' page<br /> : SMTP port: 587<br /> : IMAP port: 993<br /> <br /> <br /> <br /> Additionally, since gmail can't handle auto-saves to the Drafts folder, turn off 'Automatically save to Drafts folder every n characters' on the /Configuration/Preferences/Compose/Writing page<br /> <br /> Optionally, set the [Gmail]/Trash folder as Folder Type 'Trash' on the General page of the folder Properties, so that emptying wastebin really deletes the messages it contains.</div> Claws https://www.claws-mail.org/faq/index.php?title=File:Printer_btn.png&diff=3171 File:Printer btn.png 2020-12-06T11:57:55Z <p>Claws: </p> <hr /> <div></div> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_to_MS_Exchange&diff=3170 Connecting to MS Exchange 2020-12-06T10:25:32Z <p>Claws: </p> <hr /> <div>== MS Exchange 2003 ==<br /> This part needs '''Your''' attention<br /> <br /> == MS Exchange 2007 ==<br /> MS Exchange 2007 prefers, and is default configured to, use GSSAPI for both IMAP and SMTP. At present Claws-Mail only supports GSSAPI for IMAP. The next preferred authentication method for Exchange 2007 is NTLM which is not supported in Claws-Mail. Your only option for connecting to Exchange 2007 is if your company's mail administrator enables plain IMAP in Exchange - plain IMAP is not enabled by default.<br /> <br /> Apart from the above there is another misbehavour from Exchange 2007: although announcing the presence of Outbox (Queue) and Drafts folders, these are in read-only mode. This is causing a bit of annoyance since the IMAP specification RFC 2060 clearly states that the mail client, if these folders are announced, should use those folders for queueing and saving drafts. The only way of solving these issues is to instruct Claws-mail to use another folder for queue and draft. Also folders for sent and trash are named differently than the specication instructs: Sent is named &quot;Sent Items&quot; and trash is named &quot;Deleted Items&quot;.<br /> <br /> These are the required steps:<br /> * configure what ever settings is given to you about the company's connection - no MAPI though. Default is IMAPS (port 993) and SMTP-TLS (port 587) using AUTH LOGIN. To use the same username and password provided for IMAP4 leave the username and password field empty.<br /> <br /> <br /> * Edit Accounts -&gt; Advanced. VERY IMPORTANT: Make sure that you instruct claws to use a local/other imap account for queing and drafts.</div> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_with_Tor&diff=3169 Connecting with Tor 2020-11-11T19:01:17Z <p>Claws: /* Configuration */</p> <hr /> <div>[https://www.torproject.org/ Tor] (The Onion Router) is a software and communication infrastructure providing users with the ability to access services anonymously. Tor can be easily used with Claws Mail in order to retrieve and send emails.<br /> <br /> == Install Tor ==<br /> <br /> Install Tor (or the Tor Browser bundle) from [https://www.torproject.org/download/ torproject.org] or install it via your package manager.<br /> <br /> <br /> == Configuration ==<br /> <br /> &lt;u&gt;For all accounts&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Preferences&lt;/code&gt;) and choose the &lt;code&gt;Mail Handling/Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.<br /> <br /> For each account that you want to use the Proxy, go to each account's &lt;code&gt;Proxy&lt;/code&gt; page and check the boxes for &lt;code&gt;Use proxy server&lt;/code&gt; and &lt;code&gt;Use default settings&lt;/code&gt;<br /> <br /> &lt;u&gt;For one account&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Account Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Edit Accounts&lt;/code&gt;), select the account you want to edit and click the &lt;code&gt;Edit&lt;/code&gt; button. Go to the &lt;code&gt;Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Uncheck 'Use default settings'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.</div> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_with_Tor&diff=3168 Connecting with Tor 2020-11-11T18:57:16Z <p>Claws: </p> <hr /> <div>[https://www.torproject.org/ Tor] (The Onion Router) is a software and communication infrastructure providing users with the ability to access services anonymously. Tor can be easily used with Claws Mail in order to retrieve and send emails.<br /> <br /> == Install Tor ==<br /> <br /> Install Tor (or the Tor Browser bundle) from [https://www.torproject.org/download/ torproject.org] or install it via your package manager.<br /> <br /> <br /> == Configuration ==<br /> <br /> &lt;u&gt;For all accounts&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Preferences&lt;/code&gt;) and choose the &lt;code&gt;Mail Handling/Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.<br /> <br /> <br /> &lt;u&gt;For one account&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Account Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Edit Accounts&lt;/code&gt;), select the account you want to edit and click the &lt;code&gt;Edit&lt;/code&gt; button. Go to the &lt;code&gt;Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Uncheck 'Use default settings'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.</div> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_with_Tor&diff=3167 Connecting with Tor 2020-11-11T18:50:49Z <p>Claws: </p> <hr /> <div>[https://www.torproject.org/ Tor] (The Onion Routing) is a software and communication infrastructure providing users with the ability to access services anonymously. Tor can be easily used with Claws Mail in order to retrieve and send emails.<br /> <br /> == Install Tor ==<br /> <br /> Install Tor (or the Tor Browser bundle) from [https://www.torproject.org/download/ torproject.org] or install it via your package manager.<br /> <br /> <br /> == Configuration ==<br /> <br /> &lt;u&gt;For all accounts&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Preferences&lt;/code&gt;) and choose the &lt;code&gt;Mail Handling/Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.<br /> <br /> <br /> &lt;u&gt;For one account&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Account Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Edit Accounts&lt;/code&gt;), select the account you want to edit and click the &lt;code&gt;Edit&lt;/code&gt; button. Go to the &lt;code&gt;Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Uncheck 'Use default settings'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.</div> Claws https://www.claws-mail.org/faq/index.php?title=Main_Page&diff=3166 Main Page 2020-11-11T18:49:18Z <p>Claws: /* Claws Mail FAQ */</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 /> ** [[SSL/TLS certificate verification errors]]<br /> ** [[LDAP and Claws Mail]]<br /> ** [[Connecting to MS Exchange]]<br /> ** [[Using Claws Mail with Gmail]]<br /> ** [[Connecting with Tor]]<br /> * [[Interface]]<br /> * [[Composing Mails Or News]]<br /> * [[Debugging Claws]]<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> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_with_Tor&diff=3165 Connecting with Tor 2020-11-11T18:47:16Z <p>Claws: </p> <hr /> <div>[https://www.torproject.org/ Tor] (The Onion Routing) is a software and communication infrastructure providing users with the ability to access services anonymously. Tor can be easily used with Claws Mail in order to retrieve and send emails.<br /> <br /> == Install Tor ==<br /> <br /> Install Tor (or the Tor Browser bundle) from [https://www.torproject.org/download/ torproject.org] or install it via your package manager.<br /> <br /> <br /> == Configuration ==<br /> <br /> &lt;u&gt;For all accounts&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Preferences&lt;/code&gt;) and choose the &lt;code&gt;Mail Handling/Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.<br /> <br /> <br /> &lt;u&gt;For one account&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Account Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Edit Accounts&lt;/code&gt;), select the account you want to edit and click the &lt;code&gt;Edit&lt;/code&gt; button. Got to the &lt;code&gt;Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Uncheck 'Use default settings'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.</div> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_with_Tor&diff=3164 Connecting with Tor 2020-11-11T18:46:54Z <p>Claws: </p> <hr /> <div>[https://www.torproject.org/ Tor] (The Onion Routing) is a software and communication infrastructure providing users with the ability to access services anonymously. Tor can be easily used with Claws Mail in order to retrieve and send emails.<br /> <br /> == Install Tor ==<br /> <br /> Install Tor (or the Tor Browser bundle) from [https://www.torproject.org/download/ torproject.org] or install it via your package manager.<br /> <br /> <br /> == Configuration ==<br /> <br /> &lt;u&gt;For all accounts&lt;/u&gt;<br /> <br /> Open the &lt;code&gt;Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Preferences&lt;/code&gt;) and choose the &lt;code&gt;Mail Handling/Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.<br /> <br /> <br /> &lt;u&gt;For one account&lt;/u&gt;<br /> <br /> <br /> Open the &lt;code&gt;Account Preferences&lt;/code&gt; window (&lt;code&gt;Configuration/Edit Accounts&lt;/code&gt;), select the account you want to edit and click the &lt;code&gt;Edit&lt;/code&gt; button. Got to the &lt;code&gt;Proxy&lt;/code&gt; page.<br /> <br /> Check the box for 'Use proxy server'&lt;br /&gt;<br /> Uncheck 'Use default settings'&lt;br /&gt;<br /> Select the 'SOCKS5' type&lt;br /&gt;<br /> Enter &lt;code&gt;localhost&lt;/code&gt; for 'Hostname' and &lt;code&gt;9050&lt;/code&gt; for the 'Port'.</div> Claws https://www.claws-mail.org/faq/index.php?title=Connecting_with_Tor&diff=3162 Connecting with Tor 2020-11-11T16:18:08Z <p>Claws: Created blank page</p> <hr /> <div></div> Claws https://www.claws-mail.org/faq/index.php?title=Templates&diff=3161 Templates 2020-10-26T08:28:40Z <p>Claws: /* Response on top of quoted message */</p> <hr /> <div>=== Introduction ===<br /> <br /> Templates are used in composition windows, and act as a model for emails.<br /> Templates can be filled with static text and dynamic parts, such as the<br /> original sender's name (&quot;Dear %N, ...&quot;), the date, etc. When applying a<br /> template, the dynamic fields will be replaced with the relevant values. You<br /> can configure templates via the Tools menu.<br /> <br /> <br /> === Usage ===<br /> <br /> When applying a template, you will be asked to 'Insert' or 'Replace', the<br /> difference between replacing and inserting is only concerned with the message<br /> body. 'Replace' will replace the current composition window message body<br /> with the body defined in the template, clearing it if the template body is<br /> empty. 'Insert' will insert the template's body, if set, at the current<br /> cursor position.<br /> <br /> Whether you choose to Insert or Replace, any To, Cc or Bcc field that is<br /> defined in the template will be appended to the compose window's recipients<br /> list. If it is defined, the template's Subject will always replace the<br /> compose window's Subject.<br /> <br /> Symbols can be used in all parts of the templates and will be substituted<br /> with their respective dynamic value if possible, otherwise no value will<br /> be used. This often makes more sense if you apply a template when a replying<br /> or forwarding. There is no restriction on which symbols can be used in template<br /> parts, even if inserting the body (%M or %Q) may make no sense in common<br /> situations.<br /> <br /> When applying a template, the body is processed first, then the To, Cc, Bcc and<br /> Subject fields follow.<br /> <br /> === Examples ===<br /> <br /> ==== Response on top of quoted message ====<br /> <br /> &lt;code&gt;%X<br /> <br /> On %d, %f wrote:<br /> <br /> %Q<br /> &lt;/code&gt;</div> Claws https://www.claws-mail.org/faq/index.php?title=Templates&diff=3160 Templates 2020-10-26T08:28:24Z <p>Claws: /* Response on top of quoted message : */</p> <hr /> <div>=== Introduction ===<br /> <br /> Templates are used in composition windows, and act as a model for emails.<br /> Templates can be filled with static text and dynamic parts, such as the<br /> original sender's name (&quot;Dear %N, ...&quot;), the date, etc. When applying a<br /> template, the dynamic fields will be replaced with the relevant values. You<br /> can configure templates via the Tools menu.<br /> <br /> <br /> === Usage ===<br /> <br /> When applying a template, you will be asked to 'Insert' or 'Replace', the<br /> difference between replacing and inserting is only concerned with the message<br /> body. 'Replace' will replace the current composition window message body<br /> with the body defined in the template, clearing it if the template body is<br /> empty. 'Insert' will insert the template's body, if set, at the current<br /> cursor position.<br /> <br /> Whether you choose to Insert or Replace, any To, Cc or Bcc field that is<br /> defined in the template will be appended to the compose window's recipients<br /> list. If it is defined, the template's Subject will always replace the<br /> compose window's Subject.<br /> <br /> Symbols can be used in all parts of the templates and will be substituted<br /> with their respective dynamic value if possible, otherwise no value will<br /> be used. This often makes more sense if you apply a template when a replying<br /> or forwarding. There is no restriction on which symbols can be used in template<br /> parts, even if inserting the body (%M or %Q) may make no sense in common<br /> situations.<br /> <br /> When applying a template, the body is processed first, then the To, Cc, Bcc and<br /> Subject fields follow.<br /> <br /> === Examples ===<br /> <br /> ==== Response on top of quoted message ====<br /> <br /> &lt;code&gt;%X<br /> <br /> On %d, %f wrote :<br /> <br /> %Q<br /> &lt;/code&gt;</div> Claws https://www.claws-mail.org/faq/index.php?title=Templates&diff=3159 Templates 2020-10-26T08:01:07Z <p>Claws: </p> <hr /> <div>=== Introduction ===<br /> <br /> Templates are used in composition windows, and act as a model for emails.<br /> Templates can be filled with static text and dynamic parts, such as the<br /> original sender's name (&quot;Dear %N, ...&quot;), the date, etc. When applying a<br /> template, the dynamic fields will be replaced with the relevant values. You<br /> can configure templates via the Tools menu.<br /> <br /> <br /> === Usage ===<br /> <br /> When applying a template, you will be asked to 'Insert' or 'Replace', the<br /> difference between replacing and inserting is only concerned with the message<br /> body. 'Replace' will replace the current composition window message body<br /> with the body defined in the template, clearing it if the template body is<br /> empty. 'Insert' will insert the template's body, if set, at the current<br /> cursor position.<br /> <br /> Whether you choose to Insert or Replace, any To, Cc or Bcc field that is<br /> defined in the template will be appended to the compose window's recipients<br /> list. If it is defined, the template's Subject will always replace the<br /> compose window's Subject.<br /> <br /> Symbols can be used in all parts of the templates and will be substituted<br /> with their respective dynamic value if possible, otherwise no value will<br /> be used. This often makes more sense if you apply a template when a replying<br /> or forwarding. There is no restriction on which symbols can be used in template<br /> parts, even if inserting the body (%M or %Q) may make no sense in common<br /> situations.<br /> <br /> When applying a template, the body is processed first, then the To, Cc, Bcc and<br /> Subject fields follow.<br /> <br /> === Examples ===<br /> <br /> ==== Response on top of quoted message : ====<br /> <br /> &lt;code&gt;%X<br /> <br /> On %d, %f wrote :<br /> <br /> %Q<br /> &lt;/code&gt;</div> Claws