<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/mailcrypt/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 24 Apr 2012 11:59:39 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/mailcrypt/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Add support for Win7 64-bit</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Need to decrypt PKI email on win7 64-bit&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 24 Apr 2012 11:59:39 -0000</pubDate><guid>https://sourceforge.net398cdcafaa095a046dfe57f77d80fbcac8908b9d</guid></item><item><title>Allow encryption/signing of vm mail buffers with attachments</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;When a file is attached to a mail buffer in mail-mode with &lt;br /&gt;
vm-mime-attach-file the file isn't actually attached, instead &lt;br /&gt;
something is attached that is expanded on send to the &lt;br /&gt;
mime encoded version.  This expansion is done by &lt;br /&gt;
vm-mime-encode-composition.  It'd be really nice if &lt;br /&gt;
mailcrypt could call this before messages are signed or &lt;br /&gt;
encrypted so that they can properly be sent without the &lt;br /&gt;
user needing to manually do this. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jon Schewe</dc:creator><pubDate>Tue, 02 Dec 2003 23:26:16 -0000</pubDate><guid>https://sourceforge.netad9a6c4ba92a17834ae2f0425bc947186546f75b</guid></item><item><title>attachments for signing</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;the inline method mailcrypt uses for signatures&lt;br /&gt;
is rather archaic and annoying for users unaware&lt;br /&gt;
of GPG signatures; would it be possible to move towards&lt;br /&gt;
the attachement-based method? e.g.:&lt;/p&gt;
&lt;p&gt;Content-Type: text/plain; charset=us-ascii &lt;br /&gt;
Content-Disposition: inline &lt;br /&gt;
Content-Transfer-Encoding: quoted-printable &lt;/p&gt;
&lt;p&gt;[content]&lt;/p&gt;
&lt;p&gt;Content-Type: application/pgp-signature;&lt;br /&gt;
name=&amp;amp;quot;signature.asc&amp;amp;quot;   &lt;br /&gt;
Content-Description: Digital signature &lt;br /&gt;
Content-Disposition: inline &lt;/p&gt;
&lt;p&gt;[signature of content]&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 01 Dec 2003 21:01:56 -0000</pubDate><guid>https://sourceforge.net1731995dac484117536d334c06851497a717399b</guid></item><item><title>multiple keyring support</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm pondering how to improve multiple keyring support.&lt;br /&gt;
The main ideas:&lt;/p&gt;
&lt;p&gt;remailer keys should go on their own ring, which is&lt;br /&gt;
only searched when we're rewriting for a remailer chain&lt;/p&gt;
&lt;p&gt;it should be possible to make the user's private&lt;br /&gt;
keyring separate from their public one, so the private&lt;br /&gt;
keys are only searched during decrypt/sign operations.&lt;br /&gt;
This would make it easier to, say, keep the private key&lt;br /&gt;
on a removable floppy.&lt;/p&gt;
&lt;p&gt;Keyfetching should allow the user to specify where the&lt;br /&gt;
key should be added. This requires better control on&lt;br /&gt;
the backend (e.g., I've never figured out how to make&lt;br /&gt;
gnupg do this the way I want it to).&lt;/p&gt;
&lt;p&gt;-Brian&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Warner</dc:creator><pubDate>Thu, 26 Sep 2002 10:40:58 -0000</pubDate><guid>https://sourceforge.nete64839978b7ac442abb759fce772de59d6692eae</guid></item><item><title>symmetric encryption</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if Mailcrypt had the ability to create&lt;br /&gt;
symmetrically-encrypted messages. It has the ability to&lt;br /&gt;
decrypt such messages, after all. At the moment you can&lt;br /&gt;
get it to just armor the message (no encryption) if you&lt;br /&gt;
give it an empty list of recipients.. perhaps it would&lt;br /&gt;
make more sense to use this case to ask for an&lt;br /&gt;
encryption passphrase.&lt;/p&gt;
&lt;p&gt;Thanks to Tuyen Dinh for the suggestion.&lt;br /&gt;
-Brian&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Warner</dc:creator><pubDate>Thu, 26 Sep 2002 10:18:32 -0000</pubDate><guid>https://sourceforge.netf406bc47b8bd3335e4bfaf936c0aed95fc6ab648</guid></item><item><title>remailing to newsgroup</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Split out from a previous bug report:&lt;/p&gt;
&lt;p&gt;Also, I have a feature request. If the recipient&lt;br /&gt;
doesn't contain a &amp;amp;quot;@&amp;amp;quot; character, then its a news post.&lt;br /&gt;
I'd like to see Mailcrypt automagically change to:&lt;/p&gt;
&lt;p&gt;::&lt;br /&gt;
Anon-Post-To: recipient &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Warner</dc:creator><pubDate>Thu, 26 Sep 2002 08:33:18 -0000</pubDate><guid>https://sourceforge.net1d72d920e64477d7dfac7c5649b4369b9362eb87</guid></item><item><title>defcustom mc-default-scheme</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;After switching from PGP to GPG, I found mailcrypt no&lt;br /&gt;
longer worked, so I went searching for a variable to&lt;br /&gt;
set to tell it to use GPG instead and hacked in:&lt;/p&gt;
&lt;p&gt;(setq mc-default-scheme 'mc-scheme-gpg)&lt;/p&gt;
&lt;p&gt;I later found this in the docs:&lt;/p&gt;
&lt;p&gt;(mc-setversion &amp;amp;quot;2.6&amp;amp;quot;)    ; for PGP 2.6 (default); also&lt;br /&gt;
&amp;amp;quot;5.0&amp;amp;quot; and &amp;amp;quot;gpg&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;It might be more user-friendly to use a defcustom for&lt;br /&gt;
mc-default-scheme and have an mailcrypt menubar entry&lt;br /&gt;
for &amp;amp;quot;Customize mailcrypt&amp;amp;quot;.&lt;/p&gt;
&lt;p&gt;Alternatively (or additionally), use a default of nil,&lt;br /&gt;
and if the user hasn't customized it by setting the&lt;br /&gt;
variable, then use 'executable-find' to search for the&lt;br /&gt;
pgp or gpg commands on the system.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;
Peter Galbraith &amp;amp;lt;psg@debian.org&amp;amp;gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Peter S Galbraith</dc:creator><pubDate>Tue, 14 May 2002 15:25:13 -0000</pubDate><guid>https://sourceforge.netd3f974c7bc3abd2708cea28e72e9a94bc4f6a664</guid></item><item><title>choose backend by addresses</title><link>https://sourceforge.net/p/mailcrypt/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Some people have not yet upgraded to GPG.&lt;br /&gt;
It would be nice if mailcrypt could pick PGP2 based&lt;br /&gt;
upon the&lt;br /&gt;
recipients. GPG is not (yet?) sufficiently PGP2&lt;br /&gt;
compatible to&lt;br /&gt;
use GPG to encrypt to them.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Richardson</dc:creator><pubDate>Fri, 14 Sep 2001 17:48:57 -0000</pubDate><guid>https://sourceforge.net53663c4bda2016b6db7a1a50fb9bb320e3c943fc</guid></item></channel></rss>