From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Ico <sup@zevv.nl>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Automatically saving all attachements
Date: Tue, 29 Jan 2013 15:40:28 -0800 [thread overview]
Message-ID: <1359502714-sup-1444@javelin> (raw)
In-Reply-To: <1359485303-sup-2521@pruts.nl>
No, but OfflineIMAP+Sup effectively does this (as the attachments
will be stored with your mail).
A hook like this wouldn't be too hard to implement, but you will need to
think carefully about intended semantics: if you open an email twice,
should it save the attachment twice? If the hook is on-receive, what
should the attachment be named? How hard is it to find the attachment
you actually want, esp if you receive many? How do you deal with
multipart messages (txt + HTML versions; the HTML counts as an
"attachment").
Cheers,
Edward
Excerpts from Ico's message of Tue Jan 29 10:50:23 -0800 2013:
> Does anyone happen to have a hook that automatically saves all
> attachements to a given directory when receiving or opening an e-mail?
>
> Thanks,
>
> Ico
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2013-01-29 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:50 Ico
2013-01-29 23:40 ` Edward Z. Yang [this message]
2013-01-30 9:32 ` Gaute Hope
2013-01-30 9:57 ` Ico
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1359502714-sup-1444@javelin \
--to=ezyang@mit.edu \
--cc=sup-talk@rubyforge.org \
--cc=sup@zevv.nl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox