this:
>
> Hello,
>
> I sometimes get mail with small ASCII/UTF-8 text and big attachments
> (JPEG, PDF, ...). Fetching the full mail over data mobile or poor WLAN
> access is ofc terrible slow. Is there a way to only read the text and
> decide then to fetch the attachments or
Hello,
I sometimes get mail with small ASCII/UTF-8 text and big attachments
(JPEG, PDF, ...). Fetching the full mail over data mobile or poor WLAN
access is ofc terrible slow. Is there a way to only read the text and
decide then to fetch the attachments or not?
Thanks
matthias
, only HTML attachments
opened in Firefox do not reload. You may find mg_bgrun attached. Don't forget
to make it executable after placing it somewhere.
In order to make use of it, I have a `mailcap` file residing in `.mutt`, which
specifies how a number of file types should be opened. Inste
On Tue, Aug 15, 2023 at 06:03:22AM +0200, Fourhundred Thecat wrote:
> Hello,
>
> somehow, I got it working, that pdf attachments are opened in external
> viewer (evince). That is very nice.
>
> But, mutt waits for evince to close, before I can continue working in mutt.
>
&g
Hello,
somehow, I got it working, that pdf attachments are opened in external
viewer (evince). That is very nice.
But, mutt waits for evince to close, before I can continue working in mutt.
This prevents me from opening multiple pdf attachments and leave them
open, while continue working in
On Thu, Apr 27, 2023 at 11:28:32AM -0400, Ofer Inbar wrote:
> These days I usually do it by hitting 'v' on the original, separately
> saving the attachments I want as local files, and then re-attaching
> them to my reply or forward.
If you want to save them locally, fair en
I'm just writing to say that this is something I've long wished for
from mutt: A very easy to to either forward or reply and include the
same attachments that were attached to the original, as attachments
to my new email (my reply or forward). These days I usually do it by
hitting
On Fri, Apr 21, 2023 at 01:39:07PM -0700, Kevin J. McCarthy wrote:
> On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
> > Is there a configuration that will make mutt's forwarding behavior more
> > like other clients I have used: body is quoted in the message, and
Jan Eden via Mutt-users wrote on Sun, 23 Apr 2023 at
02:42:23 EDT in :
> On 2023-04-22 14:58, Akkana Peck wrote:
>
> > Thanks: I'd also been trying to find a way to forward with
> > attachments, and $forward_attachments helps as long as there's no
...
> I
On 2023-04-22 14:58, Akkana Peck wrote:
> > On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
> > > Is there a configuration that will make mutt's forwarding behavior more
> > > like other clients I have used: body is quoted in the message, and
> > >
> On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
> > Is there a configuration that will make mutt's forwarding behavior more
> > like other clients I have used: body is quoted in the message, and
> > attachments are automatically attached?
Kevin J. McCarthy writ
On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
Is there a configuration that will make mutt's forwarding behavior more
like other clients I have used: body is quoted in the message, and
attachments are automatically attached?
The options I have tried are:
1. Regular fo
Jason wrote on Tue, 18 Apr 2023
at 22:18:55 EDT in <20230419021855.7mdssofxkkngo...@abcmailbox.net>:
> I just did. It dumped the plain text file into the new message body
> below the original body text. Not what I want, but admittedly it's
Tangentially, but relatedly, I sometimes wonder at this.
On Wed, Apr 19, 2023 at 12:06:20AM +, Sam Kuper wrote:
> On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
> > 3. Open attachment view, tag all attachments including body, do 'tag
> > prefix' then 'forward', and select 'no' when asked whether
On Tue, Apr 18, 2023 at 04:02:36PM -0500, Jason wrote:
> 3. Open attachment view, tag all attachments including body, do 'tag
> prefix' then 'forward', and select 'no' when asked whether to send as
> attachments. This seems to do what I want for the most pa
Hello,
Is there a configuration that will make mutt's forwarding behavior more like
other clients I have used: body is quoted in the message, and attachments are
automatically attached?
The options I have tried are:
1. Regular forward. Attachments are not included.
2. Forward as attac
On Mon, Nov 14, 2022 at 10:49:25 +0100, Christopher Zimmermann wrote:
> Hi,
>
> mostly I'm only interested in the message text body, not possibly large
> attachments. Is it possible to configure mutt to not fetch the whole
> message, but only the text part, so that op
You're welcome. I just hoped it would
work ... I'm just rambling on from my
perspective on how I weed out odd
attachments to keep my mbsync:ed [1]
mailboxes nice and browsable ...
Best,
Rasmus
[1] http://isync.sourceforge.net
office365 has deleted all the other good
attachments at its end. Escpecially for
calendar invitations, where I only want
to keep the ical-file, and not the body
text in both html and text in the mime
... R
Thanks, this sounds nice, but it doesn't work for me. attachment-view
will also fetc
Hi! Sometimes, when there is a large
attachment or a pgp signature that does
not work, I just delete (d) that
attachment in attachment-view (v) before
viewing the message. But usually I end
up with a completely empty message when
office365 has deleted all the other good
attachments at its
> Is it possible to configure mutt to not fetch the whole
> message, but only the text part, so that opening multi-megabyte messages
> gets faster and using less bandwidth ?
I also wonder if Mutt can partially fetch message when opening pager view,
and stop at "Content-Disposition: attachment".
Hi,
mostly I'm only interested in the message text body, not possibly large
attachments. Is it possible to configure mutt to not fetch the whole
message, but only the text part, so that opening multi-megabyte messages
gets faster and using less bandwidth ?
Christopher
Hi all,
Using long time $edit_headers option, just discovered lovely
"Attach: " pseudo header, which makes it easy to specify new
attachments during message body edit.
However it works just one-way - once editor is finished, those
pseudo-headers are processed somehow and added to
On Thu, Feb 17, 2022 at 07:01:52PM +0100, li...@2ion.de wrote:
On Thu, Feb 17, 2022 at 12:35:32PM -0500, José María Mateos wrote:
I'd like to know if there's any config variable to set the destination folder
for saved attachments. I know the workaround is to start mutt in a different
* José María Mateos [2022-02-17 20:42]:
> Hi all,
>
> When I want to save an attachment, the default path is the path where mutt
> was launched (typically my home folder). I'd like to know if there's any
> config variable to set the destination folder for saved
On Thu, Feb 17, 2022 at 06:47:44PM +0100, Francesco Ariis wrote:
I have macros like
macro attach D ~/download/
macro attach T /tmp/
to save to different folder. Would that do?
It'd definitely work, but I'd like to know if there's some way to change
the default behaviour through a confi
On Thu, Feb 17, 2022 at 12:35:32PM -0500, José María Mateos wrote:
> I'd like to know if there's any config variable to set the destination folder
> for saved attachments. I know the workaround is to start mutt in a different
> place, but I'd prefer the confi
Hello José
Il 17 febbraio 2022 alle 12:35 José María Mateos ha scritto:
> When I want to save an attachment, the default path is the path where mutt
> was launched (typically my home folder). I'd like to know if there's any
> config variable to set the destination folder for sa
Hi all,
When I want to save an attachment, the default path is the path where
mutt was launched (typically my home folder). I'd like to know if
there's any config variable to set the destination folder for saved
attachments. I know the workaround is to start mutt in a different
On Wed, Dec 01, 2021 at 09:44:47AM -0800, Kevin J. McCarthy wrote:
> On Wed, Dec 01, 2021 at 04:02:15PM +, Chris Green wrote:
> > But, unlike in the index view, tagging doesn't mark the tagged
> > attachments in any way so with a long list and/or if you only want to
> &
On Wed, Dec 01, 2021 at 04:02:15PM +, Chris Green wrote:
But, unlike in the index view, tagging doesn't mark the tagged
attachments in any way so with a long list and/or if you only want to
attach some files from a long list it's a bit awkward.
$folder_format by default conta
I was about to ask how one could select a series of (for example)
pictures in a directory as attachments rather than having to 'a' each
one.
However, on trying it, I discovered that tagging the attachments and
then hitting Return on the last tagged attachment does attach all the
file
> application/pdf; pdftotext --text %s; copiousoutput;
I prefer this actually:
---
application/pdf; pdftotext -layout -nopgbrk -q '%s' - ; copiousoutput;
description=PDF; nametemplate=%s.pdf
application/x-pdf; pdftotext -layout -nopgbrk -q '%s' - ; copiousoutput;
description=PDF; na
For command line users, there is pdftotext available.
https://www.tutorialspoint.com/unix_commands/pdftotext.htm
A suitable entry in mailcap would enable its use.
## Plain text
text/plain; gedit %s; test=RunningX;
text/plain; nano %s;
#
## Images
image/bmp; fbi %s;
image/gif; fbi %s;
image/jpeg; f
On Fri, Apr 16, 2021 at 01:02:39PM -0600, Paul Gilmartin via Mutt-users wrote:
> On 2021-04-16, at 12:28:17, Chris Green wrote:
> >
> > As per subject, is there any easy way to print attachments such as PDF
> > files? Hitting 'p' against an attachment just says
On 2021-04-16, at 12:28:17, Chris Green wrote:
>
> As per subject, is there any easy way to print attachments such as PDF
> files? Hitting 'p' against an attachment just says "I don't know how
> to print that". Is there any way to tell mutt how to print i
On Fri, Apr 16, 2021 at 09:07:39PM +0200, Anders Damsgaard wrote:
> * Chris Green [2021-04-16 19:28:17 +0100]:
>
> > As per subject, is there any easy way to print attachments such as PDF
> > files? Hitting 'p' against an attachment just says "I don't know
As per subject, is there any easy way to print attachments such as PDF
files? Hitting 'p' against an attachment just says "I don't know how
to print that". Is there any way to tell mutt how to print it which
will also allow printing of plain text as normal.
--
Chris Green
The IMAP FETCH command allegedly supports retrieving individual sections of a
message, including the headers and parsed sections of the body based on MIME
parts. I have no idea what the support for this feature is like.
--
jh...@alum.mit.edu
John Hawkinson
2021-04-15 0:53 GMT-04:00, Matthias Apitz :
> I now even think, there is no other way, because the attachments are in
> a sequence in the mail body, separated by some describing head lines,
> and mutt must read the full body to present them.
Good point. In that case, the delete-entry c
El día miércoles, abril 14, 2021 a las 09:42:00p. m. -0400, No Suck escribió:
> Thank you for the idea. Unfortunately, testing with a bandwidth monitor
> (nethogs) shows that mutt downloads all attachments upon executing
> view-attachments from the index view. Can anyone con
Thank you for the idea. Unfortunately, testing with a bandwidth monitor
(nethogs) shows that mutt downloads all attachments upon executing
view-attachments from the index view. Can anyone confirm this? By the
way, I connect by executing change-folder with the following target:
imaps
El día miércoles, abril 14, 2021 a las 01:32:15a. m. -0400,
sunnycemet...@gmail.com escribió:
> Hello, everyone. I would like to save bandwidth. If an email has a large
> attachment that I know I do not need, is it possible to delete the
> attachment from mutt's index view and *then* open (down
Hello, everyone. I would like to save bandwidth. If an email has a
large attachment that I know I do not need, is it possible to delete
the attachment from mutt's index view and *then* open (download) the
message body? I found no such command in mutt's documentation.
Thank you.
On Sun, Jun 16, 2019 at 03:34:00PM +1000, Erik Christiansen wrote:
That looks quite useful. There's also the CheckAttach vim plugin, by
Christian Brabandt.
Starting in 1.10, there is also $abort_noattach in Mutt. It's not quite
as useful, because it waits until you hit send and then scans the
ted the compose mode
> (when the Attach: headers turn into actual mutt attachments) I don't lose
> that state either. (I've also got fcc_attach=yes, might be handy too.)
>
> And to ease using the Attach: header I have this vi macro:
>
> map ^A 1G}-:.r!exec /dev/tty; re
On 02Feb2018 04:13, Claus Assmann wrote:
Is there some fast way to save the attachments from multiple messages?
That is, without going to every individual message, viewing and
then saving the attachments? I can tag the attachments in a single
message and save them easily, but seemingly not for
Is there some fast way to save the attachments from multiple messages?
That is, without going to every individual message, viewing and
then saving the attachments? I can tag the attachments in a single
message and save them easily, but seemingly not for multiple messages
(AFAICT). Something like a
On 01Feb2018 21:54, Will Yardley wrote:
Also, you can configure the order mutt displays them in, for example, I
have:
alternative_order text/calendar text/plain text/enriched text/html test/*
Sometimes it does screw me up if the text/plain and text/html parts of a
multipart/mixed messages aren'
On Fri, Feb 02, 2018 at 02:30:16PM +1100, Cameron Simpson wrote:
> On 02Feb2018 10:45, Yubin Ruan wrote:
> > I got three attachments in a mail, as shown in the attachment view:
> >
> >[multipart/alternative, 7bit, 97K]
> >[text/plain, quoted, utf-8, 9.2K]
>
On Fri, Feb 02, 2018 at 02:30:16PM +1100, Cameron Simpson wrote:
> On 02Feb2018 10:45, Yubin Ruan wrote:
> > Hi,
> >
> > I got three attachments in a mail, as shown in the attachment view:
> >
> >[multipart/alternative, 7bit, 97K]
> >[text/plain,
On 02Feb2018 10:45, Yubin Ruan wrote:
Hi,
I got three attachments in a mail, as shown in the attachment view:
[multipart/alternative, 7bit, 97K]
[text/plain, quoted, utf-8, 9.2K]
[text/html, quoted, utf-8, 87K]
That's really 2 attachments. The text/plain and text/html part
Hi,
I got three attachments in a mail, as shown in the attachment view:
[multipart/alternative, 7bit, 97K]
[text/plain, quoted, utf-8, 9.2K]
[text/html, quoted, utf-8, 87K]
After using the editor to view the whole email, it seems to me that the
[multipart/alternative] part is an
On Fri, Jan 19, 2018 at 04:33:39PM +0100, Francesco Ariis wrote:
> On Thu, Jan 18, 2018 at 09:43:11PM -0600, Jason wrote:
> > When I press 's' on an attachment to save it, it wants to save it in
> > the home directory. Is it possible to have a default attachments
> >
On Thu, Jan 18, 2018 at 09:43:11PM -0600, Jason wrote:
> When I press 's' on an attachment to save it, it wants to save it in
> the home directory. Is it possible to have a default attachments
> folder set up that attachments automatically get saved to or at least have
> t
Hello,
When I press 's' on an attachment to save it, it wants to save it in
the home directory. Is it possible to have a default attachments
folder set up that attachments automatically get saved to or at least have
the suggested file name prefixed with the
/path/to/attachments
On Fri, Sep 01, 2017 at 07:51:54AM +0200, Kai Weber wrote:
> BTW, with either NeoMutt or Mutt 1.8.3 I get
>
>Error in /home/kai/.config/mutt/muttrc, line 13: header_cache:unknown
> variable
>source: errors in /home/kai/.config/mutt/muttrc
By default, Mutt has a minimal configuration.
On 08-31-17, Kevin J. McCarthy wrote:
Mutt 1.8.3 tarball works.
NeoMutt Github master works
Debian NeoMutt/Mutt package NeoMutt 20170609 (1.8.3) does not work
So, I have to file a bug against the Debian package?
It sounds like a good idea.
However, there is currently a freeze in the Debian mu
On Thu, Aug 31, 2017 at 11:31:13PM +0200, Kai Weber wrote:
> On 08-31-17, Kevin J. McCarthy wrote:
>
> > In an off-list reply, Kai mentioned he's running the Debian neomutt
> > package.
>
> Which was a mistake...
Yes, sorry I meant that as an explanation of why I was asking you to try
the mutt-1
On 2017-08-31 23:31, Kai Weber wrote:
> Mutt 1.8.3 tarball works.
> NeoMutt Github master works
> Debian NeoMutt/Mutt package NeoMutt 20170609 (1.8.3) does not work
This looks like some fix from mutt (the real thing) that has recently
been merged into neomutt, but only after debian froze their pa
On 08-31-17, Kevin J. McCarthy wrote:
In an off-list reply, Kai mentioned he's running the Debian neomutt
package.
Which was a mistake...
Kai, would you be willing to try compiling the mutt-1.8.3 tarball or
mercurial tip and see if the bug is present there?
Mutt 1.8.3 tarball works.
NeoMut
On 08-31-17, Kevin J. McCarthy wrote:
Browsing folders using '?' does change some state: it records the most
recent directory so the next browsing starts in the same place. Just
entering the folder name and hitting enter doesn't do that.
I'll have to dig in a bit to see the problem, but some r
On Thu, Aug 31, 2017 at 10:34:26PM +0200, Kai Weber wrote:
> On 08-31-17, Ian Zimmerman wrote:
>
> > I strongly suspect this is related to the following discussion:
> >
> > https://github.com/neomutt/neomutt/issues/609
> >
> > You could try neomutt, where my proposed patch has been integrated.
>
On 08-31-17, Ian Zimmerman wrote:
I strongly suspect this is related to the following discussion:
https://github.com/neomutt/neomutt/issues/609
You could try neomutt, where my proposed patch has been integrated.
I just build the Github master and it works.
On Thu, Aug 31, 2017 at 01:18:40PM -0700, Ian Zimmerman wrote:
> On 2017-08-31 12:49, Kevin J. McCarthy wrote:
>
> > I understand it was probably easy to forget, while in the midst of
> > dissing the "ultra-conservative" mutt devs and community, that I fixed
> > your patch and at least gave it ser
On 2017-08-31 12:49, Kevin J. McCarthy wrote:
> I understand it was probably easy to forget, while in the midst of
> dissing the "ultra-conservative" mutt devs and community, that I fixed
> your patch and at least gave it serious consideration.
The real reason it was easy to forget was the time t
On Thu, Aug 31, 2017 at 12:07:41PM -0700, Ian Zimmerman wrote:
> On 2017-08-31 10:56, Kevin J. McCarthy wrote:
>
> > > I strongly suspect this is related to the following discussion:
> > >
> > > https://github.com/neomutt/neomutt/issues/609
> >
> > Look like "your" patch contained my fixes, post
On 2017-08-31 10:56, Kevin J. McCarthy wrote:
> > I strongly suspect this is related to the following discussion:
> >
> > https://github.com/neomutt/neomutt/issues/609
>
> Look like "your" patch contained my fixes, posted in
> <20150608225607.gd8...@zaogao.lan> on mutt-dev. Thanks for the (lack
ge into.
> >
> > I have some macros to go directly to one folder:
> >
> >macro index ,i "=personal/INBOX"
> >
> > If I use this macro to go to a folder, when composing a mail adding
> > attachments does not work as expected:
>
> I str
:
>
>macro index ,i "=personal/INBOX"
>
> If I use this macro to go to a folder, when composing a mail adding
> attachments does not work as expected:
>
> 1. Use the macro to go into a folder
> 2. Start composing a mail
> 3. try to add attachments by pressing &
o index ,i "=personal/INBOX"
>
> If I use this macro to go to a folder, when composing a mail adding
> attachments does not work as expected:
I strongly suspect this is related to the following discussion:
https://github.com/neomutt/neomutt/issues/609
You could try neomutt, whe
o a folder, when composing a mail adding
attachments does not work as expected:
1. Use the macro to go into a folder
2. Start composing a mail
3. try to add attachments by pressing "a"
4. If it says Attach file ('?' for list): press "?"
5. Error message is: No su
Hi list,
the following task in mutt does always puzzle me:
I am tagging multiple attachements in an email message and want to save
them into a folder onto my disk. I execute
; s
so save all tagged attachment. Mutt asks me "Save to file:"
and I start entering the path, folder by folder, us
* Chris Green on Saturday, February 04, 2017 at 15:37:09 +
> When I forward an E-Mail with attachments (e.g. one with some
> pictures) the result is broken somehow. In the forwarded message the
> attachments are simply seen as part of the message rather than
> attachments.
&
On Sat, Feb 04, 2017 at 03:37:09PM +, Chris Green wrote:
> When I forward an E-Mail with attachments (e.g. one with some
> pictures) the result is broken somehow. In the forwarded message the
> attachments are simply seen as part of the message rather than
> attachments.
&
On Saturday, 4 February 2017 16:37:09 CET, Chris Green wrote:
When I forward an E-Mail with attachments (e.g. one with some
pictures) the result is broken somehow. In the forwarded message the
attachments are simply seen as part of the message rather than
attachments.
Is there something wrong
When I forward an E-Mail with attachments (e.g. one with some
pictures) the result is broken somehow. In the forwarded message the
attachments are simply seen as part of the message rather than
attachments.
Is there something wrong with my mutt configration, or do I need to do
something
* On 19 Nov 2016, Cameron Simpson wrote:
> Just to followup on this, here I am code reviewing some stuff for work and
> what does github use for Message-IDs? This:
>
> Message-ID:
Interesting. I guess I would be inclined to solve this by simply
urllib.quote()ing the string - consistent and pre
On 15Sep2016 11:52, Cameron Simpson wrote:
On 14Sep2016 18:35, David Champion wrote:
It will create a directory under /tmp/foo named for the message's
message-id, and store each attachment inside. Filenames are taken
from the MIME or generated sequentially if there is no filename.
Just an as
Mihail Konev wrote:
> When forwarding a message, mutt catenates all the attachments into the
> body.
>
> Is this a correct behaviour?
> How to avoid it?
The behavior is controlled by the mime_forward variable. The default
value is the traditional way mailers have always handle
On Thu, Nov 10, 2016 at 03:22:03PM -0700, Bob Proulx wrote:
> The behavior is controlled by the mime_forward variable. The default
> value is the traditional way mailers have always handled mail. It may
> optionally select mime attachments.
>
> Here is the section of the m
When forwarding a message, mutt catenates all the attachments into the
body.
Is this a correct behaviour?
How to avoid it?
On Sat, Nov 05, 2016 at 09:09:25PM +0500, Konstantin Ovsov wrote:
> Hi,
>
> i use a script (see attachment). Also required ripmime
> (https://github.com/inflex/ripMIME).
> The index-mode on the message press the F2-button and all attachments are
> stored in a folder with n
Hi,
i use a script (see attachment). Also required ripmime
(https://github.com/inflex/ripMIME).
The index-mode on the message press the F2-button and all attachments are
stored in a folder with name of subject the message.
The settings assigned to key:
macro index"~/.mutt/rip_ma.sh&q
El día Saturday, November 05, 2016 a las 09:07:02AM +, Chris Green escribió:
> If I understand you right that's at the sending end, no good at all,
Oh, sorry. You are right, it's the sending end. I have miss-read your
mail.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://w
On Fri, Nov 04, 2016 at 03:18:31PM +0100, Matthias Apitz wrote:
> El día Friday, November 04, 2016 a las 01:04:17PM +, Chris Green escribió:
>
> > I have just sent myself an E-Mail which has 50 or so attachments, they
> > are a load of VCARD files which I can't con
On Fri, Nov 04, 2016 at 05:15:21PM -0400, Jon LaBadie wrote:
> On Fri, Nov 04, 2016 at 01:04:17PM +, Chris Green wrote:
> > I have just sent myself an E-Mail which has 50 or so attachments, they
> > are a load of VCARD files which I can't concatenate at the sending
> &
On Fri, Nov 04, 2016 at 01:04:17PM +, Chris Green wrote:
> I have just sent myself an E-Mail which has 50 or so attachments, they
> are a load of VCARD files which I can't concatenate at the sending
> end.
>
> So, how can I save them all quickly without doing each one sep
El día Friday, November 04, 2016 a las 01:04:17PM +, Chris Green escribió:
> I have just sent myself an E-Mail which has 50 or so attachments, they
> are a load of VCARD files which I can't concatenate at the sending
> end.
>
> So, how can I save them all quickly wi
I have just sent myself an E-Mail which has 50 or so attachments, they
are a load of VCARD files which I can't concatenate at the sending
end.
So, how can I save them all quickly without doing each one separately?
--
Chris Green
On 30-09-2016, at 00h 28'03", Konstantin Ovsov wrote about "Re: attachments
name non english symbol"
> On Thu, 29 Sep 2016, 10:44:19, Ionel Mugurel Ciobîcă wrote:
> >
> > Do you forward only the attachments? How do you do that?
>
> Yes, only forwarded a
On Thu, 29 Sep 2016, 10:44:19, Ionel Mugurel Ciobîcă wrote:
> On 28-09-2016, at 10h 09'53", Konstantin Ovsov wrote about "[SPAM?]
> attachments name non english symbol"
> > Hi!
> >
> > I forward attachments with the russian name. The recipient receiv
Hi!
I forward attachments with the russian name. The recipient receives an email
with an attachment with the wrong name. For example, "шрифт.zip" converted into
"__.zip"
It is possible to keep the original name?
If i send a new message, the attachment retains the
On Fri, Sep 16, 2016 at 11:45:44AM -0300, Marcelo Laia wrote:
> On 15/09/16 at 08:10am, Luis Mochan wrote:
> ...
> When I press
>
> Shift+y followed by s in index mode view, current body message is saved inside
> $HOME/attachments/ as textfile0 name.
Yes. The text parts of the
ian repositories. I use it manually through a mutt macro
> > >
> > > macro index Ys "| ~/.mutt/saveattachments\n" "Save attachments"
> > >
> >
> > Hi, I try to use your script, nut, when I hint Y, mutt tell me that "Key Y
>
On Wed, Sep 14, 2016 at 04:12:48PM -0700, Are Troi wrote:
> Hi All,
>
> Last night at a technical talk I lamented the loss around 5 years ago
> from Fedora of command-line tools to extract email attachments from a
> BASH script and a colleague told me Mutt can do this.
Mutt is a r
npak about a year ago to save all attachments from
> a large MBOX and it was everything but a hasslefree experience. Various
> attachments were missed or not processed, some segfaults.
> Those tools are apparently not as robust as mutt is.
I have used ripmime without problems but on indivi
> > macro index Ys "| ~/.mutt/saveattachments\n" "Save attachments"
> >
>
> Hi, I try to use your script, nut, when I hint Y, mutt tell me that "Key Y is
> not mapped"
You should first define the macro! You could do it interactively (
On 14/09/16 at 08:06pm, Luis Mochan wrote:
> Maybe you could use the program 'ripmime' directly from bash. I found
> it in the debian repositories. I use it manually through a mutt macro
>
> macro index Ys "| ~/.mutt/saveattachments\n" "Save attachmen
On Thu, Sep 15, 2016 at 10:53:02AM +1000, Cameron Simpson wrote:
> On 14Sep2016 16:12, Are Troi wrote:
> >Last night at a technical talk I lamented the loss around 5 years ago
> >from Fedora of command-line tools to extract email attachments from a
> >BASH script and a colle
1 - 100 of 987 matches
Mail list logo