On 25.06.15 11:48, David Champion wrote:
There are use cases for allowing specific roles/service accounts
access to your unvetted email attachment files. (I would expect these
generally have to do with file sharing/export.) Conventionally the only
way around this is to proactively degrade
It seems when multiple hooks exist for the same context (in particular,
multiple folder-hooks matching on .*), they're executed in reverse
order of appearance in .muttrc.
From the 1st day I started using mutt seriously I had this in .muttrc:
folder-hook .* exec collapse-all
But, this resulted
On Fri, Jun 26, 2015 at 06:06:50PM +1000, Erik Christiansen wrote:
On 25.06.15 11:48, David Champion wrote:
There are use cases for allowing specific roles/service accounts
access to your unvetted email attachment files. (I would expect these
generally have to do with file sharing/export.)
* Ian Zimmerman i...@buug.org [06-26-15 12:05]:
It seems when multiple hooks exist for the same context (in particular,
multiple folder-hooks matching on .*), they're executed in reverse
order of appearance in .muttrc.
From the 1st day I started using mutt seriously I had this in .muttrc:
On Fri, Jun 26, 2015 at 10:28:45PM +0200, Andrzej Popielewicz wrote:
* Mick michaelkintz...@gmail.com [2015-06-25 17:07:37]:
I have just tested. It works.
In order to begin the game You have to switch on two-stage verification,
being in Your Gmail account. After verification using code snet
* Mick michaelkintz...@gmail.com [2015-06-25 17:07:37]:
On Thursday 25 Jun 2015 16:13:35 Grant Edwards wrote:
On 2015-06-25, Ben Fitzgerald benfi...@gmail.com wrote:
I recently updated my google preferences and limited set allow
unsecure apps to off.
Later I tried to login to
On 26.06.15 18:06, Erik Christiansen wrote:
# chmod g+s,o+w /tmp/test
Allowing other to publish to the group was done for the purpose of a
quick confirmation that sgid does what we expect. In practice, it would
be more secure for the publisher to own the directory, and only set the
sgid bit.
Ian Zimmerman wrote:
From this behavior it is clear that the second hook in fact runs
first, and vice versa.
Actually, the folder-hooks are run in the order listed in your .muttrc.
However, each invocation of exec or push adds to the *front* of the
input buffer. Hence the contents of the
