From: David Maus <dmaus@ictsoc.de>
To: org-mode <emacs-orgmode@gnu.org>
Subject: org-mime - issues and remarks
Date: Fri, 23 Apr 2010 18:12:11 +0200 [thread overview]
Message-ID: <877hny4084.wl%dmaus@ictsoc.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2056 bytes --]
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 before org-mime
should/could use the function to determine MIME media type of
message-mode and mime-edit-mode respectively.
For SEMI the function is `mime-find-file-type', called with the
file name as argument and returns a list whose first element is a
string with MIME media type and second element is MIME media
subtype.
- when creating an attachment for a image org-mime uses the path to
the image for the value of the content-id header. This violates
RFC2045, section 7.
The value of the content-iD header field is syntactically
identical to the message-id header.
addr-spec = local-part "@" domain
For SEMI the function for creating a message-id string is
`wl-draft-make-message-id-string' that is called without any
argument and returns a shiny new message-id header field value
/with/ the angle brackets.
Furthermore there are some minor glitches:
- the "filename" parameter is only defined for the
content-disposition header field; because images are attachments
they can/should be easily send with
content-disposition: attachment; filename="<filename>"
For SEMI (replace _ by -):
__[[type/subtype
content-disposition: attachment; filename="<filename>"][base64]]
- 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.
- org-mime /should/ add information to the user-agent mail header
field indicating that the message was created with the help of
org-mime.
HTH
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-04-23 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 16:12 David Maus [this message]
2010-04-23 21:00 ` org-mime - issues and remarks Sebastian Rose
2010-04-26 16:04 ` Eric Schulte
2010-04-27 18:14 ` David Maus
2010-04-27 19:26 ` Eric Schulte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877hny4084.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).