At Mon, 26 Apr 2010 10:04:12 -0600,
Eric Schulte wrote:
David Maus dm...@ictsoc.de writes:
While skimming the source code of org-mime I noticed two severe issues
with regards to the MIME specifications:
- when creating an attachment for a image org-mime (still) uses the
file
David Maus dm...@ictsoc.de writes:
At Mon, 26 Apr 2010 10:04:12 -0600,
Eric Schulte wrote:
David Maus dm...@ictsoc.de writes:
While skimming the source code of org-mime I noticed two severe issues
with regards to the MIME specifications:
- when creating an attachment for a image
Hi David,
If I find some time, I'll certainly take a look at these. More comments
below.
David Maus dm...@ictsoc.de writes:
While skimming the source code of org-mime I noticed two severe issues
with regards to the MIME specifications:
- when creating an attachment for a image org-mime
While skimming the source code of org-mime I noticed two severe issues
with regards to the MIME specifications:
- when creating an attachment for a image org-mime (still) uses the
file extension as MIME media subtype for Gnus messages. This not
in compliance with RFC 2046. As mentioned
Hi David,
David Maus dm...@ictsoc.de writes:
- org-mime uses `reporter-compose-outgoing' to open a new message
draft. This is not a could solution because (a) org-mine does not
want to send a bug report and (b) would depend on reporter.el
without necessity.
reporter.el is
