Community Discussions and Support
mailto: cc, bcc not recognized

[quote user="Neil Fraser"]mailto: stopped working properly on upgrading to pmail 4.61.[/quote]

There's now an update available which enables handling of CC and BCC parameters, but it also introduces an optional warning if BCC addresses are included since they aren't immediately visible on Pegasus Mail's editor front page and thus might create a privacy/data leak issue (French and Italian translations incomplete, but released anyway as it provides another crash fix).

<p>[quote user="Neil Fraser"]mailto: stopped working properly on upgrading to pmail 4.61.[/quote]</p><p>There's now an <a href="/files/folders/community_add-ons_for_pegasus_mail/entry24145.aspx" mce_href="/files/folders/community_add-ons_for_pegasus_mail/entry24145.aspx" target="_blank">update available</a> which enables handling of CC and BCC parameters, but it also introduces an optional warning if BCC addresses are included since they aren't immediately visible on Pegasus Mail's editor front page and thus might create a privacy/data leak issue (French and Italian translations incomplete, but released anyway as it provides another crash fix).</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

mailto: stopped working properly on upgrading to pmail 4.61.

The following mailto: commands work fine in all other respects, but ignores the cc, bcc parameters:

mailto:abc@telkomsa.net?cc=sales@necon.co.za&subject=Megapulse enquiry&body=Dear Sirs,"

mailto:abc@telkomsa.net?bcc=me@necon.co.za&subject=Megapulse enquiry&body=Dear Sirs,"

mailto:abc@telkomsa.net?bcc=me@necon.co.za&cc=sales@necon.co.za&subject=Megapulse enquiry&body=Dear Sirs,"

Web browser used: Firefox 4.0.1

OS: MS Windows XP Professional 32-bit SP3

 

 

<p>mailto: stopped working properly on upgrading to pmail 4.61.</p><p>The following mailto: commands work fine in all other respects, but ignores the cc, bcc parameters:</p><p>mailto:abc@telkomsa.net?cc=sales@necon.co.za&subject=Megapulse enquiry&body=Dear Sirs," </p><p>mailto:abc@telkomsa.net?bcc=me@necon.co.za&subject=Megapulse enquiry&body=Dear Sirs," </p><p>mailto:abc@telkomsa.net?bcc=me@necon.co.za&cc=sales@necon.co.za&subject=Megapulse enquiry&body=Dear Sirs," </p><p>Web browser used: Firefox 4.0.1</p><p>OS: MS Windows XP Professional 32-bit SP3 </p><p> </p><p> </p>

[quote user="Neil Fraser"]mailto: stopped working properly on upgrading to pmail 4.61.[/quote]

Until recently the respective RFC 2368 regarded CC and BCC parameters as being "unsafe":

"Note that some headers are inherently unsafe to include in a message generated from a URL. For example, headers such as "From:", "Bcc:", and so on, should never be interpreted from a URL. In general, the fewer headers interpreted from the URL, the less likely it is that a sending agent will create an unsafe message."

The latest (Oct 2010) RFC 6068 still issues a warning against using them in general:

"'mailto' URIs on public Web pages expose mail addresses for harvesting. This applies to all mail addresses that are part of the 'mailto' URI, including the addresses in a "bcc" <hfvalue>. Those addresses will not be sent to the recipients in the 'to' field and in the "to" and "cc" <hfvalue>s, but will still be publicly visible in the URI. Addresses in a "bcc" <hfvalue> may also leak to other addresses in the same <hfvalue> or become known otherwise, depending on the mail user agent use."

But I'll see what I can do.

 

&lt;p&gt;[quote user=&quot;Neil Fraser&quot;]mailto: stopped working properly on upgrading to pmail 4.61.[/quote]&lt;/p&gt;&lt;p&gt;Until recently the respective &lt;a href=&quot;http://www.rfc-editor.org/rfc/rfc2368.txt&quot; mce_href=&quot;http://www.rfc-editor.org/rfc/rfc2368.txt&quot; target=&quot;_blank&quot;&gt;RFC 2368&lt;/a&gt; regarded CC and BCC parameters as being &quot;unsafe&quot;:&lt;/p&gt;&lt;p&gt;&lt;blockquote&gt;&lt;p&gt;&quot;Note that some headers are inherently unsafe to include in a message generated from a URL. For example, headers such as &quot;From:&quot;, &quot;Bcc:&quot;, and so on, should never be interpreted from a URL. In general, the fewer headers interpreted from the URL, the less likely it is that a sending agent will create an unsafe message.&quot; &lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;The latest (Oct 2010) &lt;a href=&quot;http://www.rfc-editor.org/rfc/rfc6068.txt&quot; mce_href=&quot;http://www.rfc-editor.org/rfc/rfc6068.txt&quot; target=&quot;_blank&quot;&gt;RFC 6068&lt;/a&gt; still issues a warning against using them in general:&lt;/p&gt;&lt;p&gt;&lt;blockquote&gt;&lt;p&gt;&quot;&#039;mailto&#039; URIs on public Web pages expose mail addresses for harvesting. This applies to all mail addresses that are part of the &#039;mailto&#039; URI, including the addresses in a &quot;bcc&quot; &amp;lt;hfvalue&amp;gt;. Those addresses will not be sent to the recipients in the &#039;to&#039; field and in the &quot;to&quot; and &quot;cc&quot; &amp;lt;hfvalue&amp;gt;s, but will still be publicly visible in the URI. Addresses in a &quot;bcc&quot; &amp;lt;hfvalue&amp;gt; may also leak to other addresses in the same &amp;lt;hfvalue&amp;gt; or become known otherwise, depending on the mail user agent use.&quot;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;But I&#039;ll see what I can do. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft