tag:gpgtools.tenderapp.com,2011-11-04:/discussions/problems/18-gpg-mail-uses-smime-but-wont-allow-existing-smime-encryptionGPGTools: Discussion 2017-09-14T12:10:38Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892011-11-17T21:00:32Z2011-11-17T21:01:16ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Hi Steve,</p>
<p>it's true, at the moment GPGMail 2.0 is not capable of
coexisting peacefully with S/MIME. It's an either/or situation you
described.<br>
This is due to the fact the 2.0 version is a complete rewrite and
the version you're running still an alpha version.<br>
The final version will work seamlessly with S/MIME.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892011-11-17T21:05:38Z2011-11-17T21:05:38ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Luke,</p>
<p>PuuRrrfect!!!<br>
Just wanted be sure I wasn't doing something stupid... :)<br>
Love what you're doing by the way. I know it's a huge effort.<br>
It is appreciated.</p>
<p>I still can't believe Apple is not making this easier.</p>
<p>Steve</p></div>Stephen Claytontag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892011-11-17T21:08:28Z2011-11-17T21:08:28ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Thanks, we're really trying our best, it only takes time as the
team<br>
is very very small.<br>
Apple sure doesn't make it easy, but the new version of GPGMail
will be very nice and easy to use and it should be easier to update
it along with system updates, so it's all worth it.</p>
<p>Have fun, and just ask when you run into problems.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892012-02-28T15:48:09Z2012-02-28T15:48:09ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Hi Steve,</p>
<p>as promised, we've worked on better S/MIME | OpenPGP
switching.<br>
It would be great if you could test the current dev version:</p>
<p><a href=
"http://nightly.gpgtools.org/GPGMail-trunk.dmg">http://nightly.gpgtools.org/GPGMail-trunk.dmg</a></p>
<p>And let us know what you think.<br>
Be aware that this version could show other issues, so use it with
caution.</p>
<p>Thanks for the help</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892012-03-02T11:09:49Z2012-03-02T11:09:49ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Hi Luke,</p>
<p>your doing a great job!<br>
Tested it ... works fine !!!!<br>
Just a minor:<br>
Current Workflow was a little unintuitive, as follows:<br>
1) enabled Signature by Star Button in Mail.app(<em>)<br>
2) Got blue SMIME (nice)<br>
3) Switched to PGP (got gray PGP)<br>
4) AGAIN !!! had to enable Signature by Star Button in
Mail.app(</em>)<br>
5) Got green PGP (nice)</p>
<p>So the re-enabling is a little unintuitve, as I already
indicated that I want it signed :-)<br>
But, nevertheless GREAT WORK !!!</p></div>Henrichtag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892012-03-02T11:13:44Z2012-03-02T11:13:44ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Hi Henrich,</p>
<p>the next release will keep the star button active, if so chosen
before, BUT<br>
we've added a "intelligent" way of determining what security
method, sign status, and encrypt status should be set for new
messages.<br>
The method works by tracking the security method, sign status,
encrypt status used for each method and making the decision based
on that information for you.</p>
<p>So if you signed more often from a sender address to a
recipient, than not sign, the next message to the recipient(s) will
be signed as well.<br>
If you have S/MIME and PGP for a key and you've used one of the two
methods more often, based on recipients and sender, the method is
chosen which was used more often.<br>
And so on.<br>
We're still working out some kinks but this should really improve
your workflow and in the best case you should have to press either
of those buttons again.</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892012-03-02T13:35:59Z2012-03-02T13:35:59ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Hi Luke,</p>
<p>as much as I like automatic behaviour, and as much as this would
increase the usage of signature on the Internet,<br>
could you include a command line that deactivates the automatic
decision ;-)<br>
By the way, what kind of statistics (sender, receiver, used enc) do
you need to store locally on the machine, and is there way of
prohibiting this background logging, at the cost of loosing the
automation of course?</p>
<p>Thanks again for the great PlugIn.</p>
<p>Best Regards,<br>
Henrich</p></div>Henrich C. Pöhlstag:gpgtools.tenderapp.com,2011-11-04:Comment/114989892012-03-02T13:55:54Z2012-03-02T13:55:54ZGPG mail uses sMime but won't allow existing sMime encryption<div><p>Hi Henrich,</p>
<p>that's exactly what we plan to do if more people request it.<br>
Please add a reply to this ticket:<br>
<a href=
"http://gpgtools.lighthouseapp.com/projects/65764/tickets/457-if-needed-add-default-options">
http://gpgtools.lighthouseapp.com/projects/65764/tickets/457-if-nee...</a></p>
<p>I know tracking and statistics are bad words with all the
privacy issues being brought to light, but don't worry, we're
saving the email address in a hashed way and other than that only
the date and sign/no-sign, encrypt/no-encrypt status and security
method.<br>
There should not be a need to prohibit this.<br>
If you still feel disabling that should be possible, please add
that suggestion to the ticket mentioned above.</p>
<p>2.0 is being released soon, as this one is gonna be a hit :D</p></div>Luke Le