Re: base64 encoding of full message body?
On Sun, Mar 20, 2016 at 11:48 AM, Gabriel Philippe
wrote:
> Hi,
>
> I'm sick and tired of seing the PGP signatures of my messages to Yahoo
> groups invalidated. Yahoo groups thinks it is a good idea to split
> "long" lines, but that changes the message body. I tried to limit the
> maximum size of the lines in my messages, and that works most of the
> time. But quoted lines needs to be rewrapped (because they get longer
> due to the addition of "> "), and as I write in French, non ASCII
> characters are encoded in quoted-printable, which can greatly increase
> the length of the lines.
>
> It seams that (all?) messages from the Yahoo groups interface
> ("X-Mailer: Yahoo Groups Message Poster") are fully base 64 encoded.
> "Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: base64"
>
> Is it possible to force this behaviour in mutt? I would limit it to
> messages sent to Yahoo groups.
I've found an ugly hack.
macro compose y "^Ubase64"
If someone founds a better way...
--
Gabriel
Three newbie questions
I have spent much of the last week (when I should have been doing other things) getting to grips with mutt. My setup consists of three mail accounts: two gmail, and one MS Exchange which I access using davmail (I'm using Linux) so that localhost is my server. Since I was having problems downloading headers and bodies - mutt would freeze - I'm using mbsync to sync my mails locally, and msmtp as a sender. All this has required a great deal of configuring, and copying bits and pieces of other people's config files. Anyway, it mostly works, but I still have a few things I can't (easily) do: 1. When I send an email, no matter from what account, a copy always ends up in the Inbox of my default account. How can I ensure such a mail ends up in the Sent folder of its account? 2. Can I open up a mailbox so that the current highlighted message is the first one received since my last visit to this account? 3. How can I trawl through a Maildir folder and extract all the addresses into an alias file? There is a Perl script to do that, but I can't get it to work on my system - the libraries are incompatible. 4. When I run mbsync, it seems very very slow, and takes a long time to do its stuff, and invariably it finishes with an error message: "Socket error from imap.gmail.com (64.233.188.108:993): Connection timed out" What I don't understand is that this happens when syncing messages from my work account, which simply uses localhost as the server. As well, I get an error message saying that "slave Trash cannot be opened." which is mystifying, as the Trash directory is there. -- Whew! So many queries... If I have flouted protocol in asking too many questions in one email, do let me know, and I'll restrict my questioning. But I still have even more questions! Thanks very much, Alasdair
mbox problem on new system
Hi, I'm an inveterate mbox user (that goes back to the days when ext2/3 were reputed to not like vast numbers of files in a directory). I'm now building a new machine to replace the current antiquated box I use as my home server. The current server (x86_64 linux) was last rebuilt in September last year with coreutils-8.24, gcc-5.2 and for a few weeks it has been running mutt-1.6.1. The new base system is from a few months ago, with coreutils-8.25 and gcc-5.3 (the base is linuxfromscratch - old is 7.8, new is 7.9, and everything after is from development BLFS - 'beyond linuxfromscratch'). In ~/.muttrc I have set folder="~/Mail" and ~/Mail is a symlink to ~/mailboxes/Jul/ for this month's mails (and also symlinks to some other mboxes). As part of bringing up the new machine I have copied /home from the old one (will need to repeat that when I'm ready for the real changeover), to sort out the many problems which I expect to encounter. But I did not expect that mutt would now cause me pain. When I open mutt on the old machine, I get a list of all the mailboxes for the current month. But on the new machine I get /home/ken/Mail is not a mailbox. I had built 1.6.2 because it got announced just before I got to that point, but reverting to 1.6.1 is no different. I mentioned the changed version of coreutils because on the old machine 'ls -l ~/Mail' shows it is a symlink whereas on the new one it shows the contents of the directory to which it points : that confused me for a while, but 'file' confirmed it was a symlink as expected. I *can* use it, by keying 'c ?' for a list of the mailboxes, but that is awkward when things used to just work. Any ideas what I can do to open the directory of mailboxes directly, the way I used to, please ? ĸen -- Brave Sir Nigel ran away! When reality reared its ugly head, Sir Nigel turned his tail and fled. Brave brave brave Sir Nigel.
Re: mbox problem on new system
* Ken Moffat [07-07-16 17:26]: > Hi, > > I'm an inveterate mbox user (that goes back to the days when ext2/3 > were reputed to not like vast numbers of files in a directory). > > I'm now building a new machine to replace the current antiquated > box I use as my home server. The current server (x86_64 linux) was > last rebuilt in September last year with coreutils-8.24, gcc-5.2 and > for a few weeks it has been running mutt-1.6.1. The new base system > is from a few months ago, with coreutils-8.25 and gcc-5.3 (the base > is linuxfromscratch - old is 7.8, new is 7.9, and everything after > is from development BLFS - 'beyond linuxfromscratch'). > > In ~/.muttrc I have > > set folder="~/Mail" > > and ~/Mail is a symlink to ~/mailboxes/Jul/ for this month's mails > (and also symlinks to some other mboxes). > > As part of bringing up the new machine I have copied /home from the > old one (will need to repeat that when I'm ready for the real > changeover), to sort out the many problems which I expect to > encounter. But I did not expect that mutt would now cause me > pain. > > When I open mutt on the old machine, I get a list of all the > mailboxes for the current month. But on the new machine I get > > /home/ken/Mail is not a mailbox. > > I had built 1.6.2 because it got announced just before I got to that > point, but reverting to 1.6.1 is no different. > > I mentioned the changed version of coreutils because on the old > machine 'ls -l ~/Mail' shows it is a symlink whereas on the new one > it shows the contents of the directory to which it points : that > confused me for a while, but 'file' confirmed it was a symlink as > expected. > > I *can* use it, by keying 'c ?' for a list of the mailboxes, but that > is awkward when things used to just work. > > Any ideas what I can do to open the directory of mailboxes directly, > the way I used to, please ? consider alias alias mutt='mutt -f ' besure to revise ~/.muttrc (and/or /etc/muttrc) to reflect proper mail box locations. from one stil using mbox :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Re: mbox problem on new system
On Thu, Jul 07, 2016 at 05:31:18PM -0400, Patrick Shanahan wrote: > * Ken Moffat [07-07-16 17:26]: > > > > In ~/.muttrc I have > > > > set folder="~/Mail" > > > > and ~/Mail is a symlink to ~/mailboxes/Jul/ for this month's mails > > (and also symlinks to some other mboxes). > > > > When I open mutt on the old machine, I get a list of all the > > mailboxes for the current month. But on the new machine I get > > > > /home/ken/Mail is not a mailbox. > > > > consider alias > > alias mutt='mutt -f ' > > besure to revise ~/.muttrc (and/or /etc/muttrc) to reflect proper mail box > locations. > > from one stil using mbox :) The problem is that they are NOT proper mailbox locations! With 1.6.1 on the old system I can point to a directory containing mailboxes and symlinks, but on the new system that gives me the error message. Until now, I have looked at the times on the mailboxes to see which had soemthing new. For the symlinks, they are either old stuff or the catch-all mymail - people who mail me directly can expect a delay of some hours before I look at that mailbox, because almost everything I am interested in is public and on lists (private stuff from people who tend to use html gets sent to a gmail account which I read in a browser or on my phone). I can use mutt -f Mail/mymail (which is the only current mailbox guaranteed to exist at the start of a month), but most of the time that will not be an improvement. I filter most incoming mails via procmail, what I would like to continue to do is just get a list of the currnet mailboxes and symlinks. What is really perplexing me is that mutt-1.6.1 on a slightly older system works the way I have been used to (probably for more than 10 years), but the same version on a current system works differently. Hmm, I suppose this might be a change in the linux kernel (the old system runs 4.1, the new one is 4.4). Thanks anyway. ĸen -- Brave Sir Nigel ran away! When reality reared its ugly head, Sir Nigel turned his tail and fled. Brave brave brave Sir Nigel.
Re: Three newbie questions
On 08.07.16 00:46, Alasdair McAndrew wrote: > 1. When I send an email, no matter from what account, a copy always > ends up in the Inbox of my default account. How can I ensure such a > mail ends up in the Sent folder of its account? I'd look for a "set record" statement in .muttrc, and replace it with: set record="~/mail/Sent" or whatever the path to yours is. Several questions in one mail is fine, so long as readers are curious enough to delve past the non-specific subject line, which admittedly does tempt with the prospect of low-hanging fruit, and so may work well. Heck, some respondents may even have time/experience to answer more than one of them. ;-) Erik
