Re: textwidth/linewrap

[tech-lists]

Hi,

Lots of ways to do the same thing! Thanks for the suggestions
--
J.


signature.asc
Description: PGP signature

textwidth/linewrap

[tech-lists]

Hi,

I guess lots of people would use mutt with vim-console.

Can anyone tell me please what setting they use for line 
wrapping? I thought in .vimrc it'd be


set textwidth=72

but that doesn't seem to work. Is it a setting in .muttrc
or in .vimrc? Or an additional setting?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: [SOLVED] Re: mutt seems laggy to resume on v.2.x

[tech-lists]

On Thu, Nov 26, 2020 at 04:03:53PM -0800, Kevin J. McCarthy wrote:

I'd normally say to double check $imap_check_subscribed is unset, but
that option is quite old.  Perhaps something has changed in the code
there, but I'm not recalling anything right now.


Well, you were right, it was enabled! I've disabled it now, and adjusted the
spool folder location.

thanks,
--
J.


signature.asc
Description: PGP signature

[SOLVED] Re: mutt seems laggy to resume on v.2.x

[tech-lists]

Hi,

I *think* i've found the reason for the lagginess. Hopefully what's here will
be of use to others.

With mutt, for this address I make a config file, launch mutt in a screen with 
-F.
On the remote system, I have a lot of different folders which I'll use 
with different email addresses. These email addresses are aliases to the main

account.

What was happening before (mutt v.1.x) was mutt would log in, scan the
imap folders i'd configured for it in .muttrc-lists (and *only* those 
folders, no others) then return and this was quick on an average dsl line.


What is happening now (mutt v.2.x) is it's scanning everything under the
main account. There's a lot of mail there. It's this which is taking the time. 
This was found using -d 2 with mutt. If more than say 30s elapses between
moving pages or moving the highlight bar, when it's moved again it scans 
the entire mailspool again. This is laggy on a 100MBit connection.


Right now I don't know if the old mutt to new mutt is the cause or if there's
been a change that they at the mail hosting have done which has occurred
at the same time as mutt v1 -> mutt v2. It might not be an issue with
mutt at all.

Maybe this isn't the ideal way to have mutt and imap? Some setups have 
an imap cache running locally. Is this better than running imaps access

from .muttrc ?

--
J.


signature.asc
Description: PGP signature

Re: mutt seems laggy to resume on v.2.x

[tech-lists]

Hi,

ktrace shows (as best I can interpret it) when mutt is "woken up" 
it re-uses the connection to the imap server somehow. It's 
exchanging information, not sure what. But it's a big

segment like a half page full in kdump. So maybe the answer is in
idle parameters. I'll re-do the muttrc with the newly installed
one from 2.0.2 as a template.

Doing stuff like setting fmcache to tmpfs, experimenting with 
different db backends and making sure the hd doesn't sleep seem 
to have no effect so I'm guessing the direct cause isn't local.

--
J.


signature.asc
Description: PGP signature

Re: mutt seems laggy to resume on v.2.x

[tech-lists]

On Thu, Nov 26, 2020 at 10:34:30AM +1100, Cameron Simpson wrote:


Probably. I don't have a FreeBSD box to hand. Is yours a Raspberry?


yup, rpi4 with 8GB


Have you got ktrace and kdump? Less interactive, but IIRC the process is
to ktrace your mutt command and kdump the resulting log file.


I don't have it right this moment because when building the kernel
it was one of the things I took out to streamline it. I'll recompile
and get back with results.

With my other tests, recompiling mutt with different header 
backends made no difference. I think you're right with the 
auto-sleep thing. Hopefully it can be turned off.


Thanks all for your help.
--
J.


signature.asc
Description: PGP signature

Re: mutt seems laggy to resume on v.2.x

[tech-lists]

Hi,

On Wed, Nov 25, 2020 at 05:43:21PM -0500, Patrick Shanahan wrote:


possibly reinstall strace.  for my openSUSE Tumbleweed system I show:
 strace-5.9-1.1.x86_64

your version is quite old and version number appear to reflect the kernel
version.  what kernel are you running, 4.5.x ??


I'm using freebsd-current 
--

J.


signature.asc
Description: PGP signature

Re: mutt seems laggy to resume on v.2.x

[tech-lists]

Hi,

On Thu, Nov 26, 2020 at 09:01:03AM +1100, Cameron Simpson wrote:

A way to check this would be to have another window open running:

   strace -p pid-of-idle-mutt-process

Get that ready. Wait for idleness. Resume. See where it stalls.

If that is hard to observe interactively, strace has options for
including timestamps in the trace output, you could do the resume and
then scroll back looking for the stall in the timestamps.


Unfortunately strace (do you mean devel/strace) appears to be broken:

root@rpi4:/usr/ports/devel/strace# make
===>  strace-4.5.18_1 is marked as broken: Uses procfs-based process debugging.
*** Error code 1

Is there an equivalent tool?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: mutt seems laggy to resume on v.2.x

[tech-lists]

Hello,

On Wed, Nov 25, 2020 at 09:59:30AM -0600, Hokan wrote:


I am running a month-old FreeBSD-CURRENT on an RPI-4 (8GB) and could not 
replicate the problem.


thanks for posting yr config.

Your mutt is compiled just slightly differently:


hcache backend: Berkeley DB 5.3.28: (September  9, 2013)


Is there a reason why you're using this hcache backend?

different configure options: '--disable-autocrypt' '--without-sqlite3' 
'--with-bdb=/usr/local' '--without-tokyocabinet' 


Compile options:

ISPELL="/usr/local/bin/ispell"


I'm going to try recompiling with options as you've set them.
Might try kyotocabinet too
--
J.


signature.asc
Description: PGP signature

mutt seems laggy to resume on v.2.x

[tech-lists]

Hi,

I'm finding mutt significantly more laggy to resume on later
versions (=>2.x) than say 1.5.21.

Let's say there's the list of emails in a folder already 
selected. If I use up or down arrow for example, it'll sit for 
3-4 seconds doing nothing and then move. But once moving, it's

as responsive as it's always been before.

Then, say 5 minutes happen where nothing happens. Slow to move
around again. I'm using imaps. It's not having to re-authenticate, 
so the connection isn't dropping. Ping times to the imap server 
are 77ms, no packet loss.


Is it my config? Maybe should revise it as it's not changed
significantly for more than a decade. What should I be looking for?

For context:
freebsd-current (all debugging has been turned off)
TMP is ~/tmp and is tmpfs (memory) mounted.
$HOME is usb3-mounted spinning rust.

% mutt -v
Mutt 2.0.2 (2020-11-20)
Copyright (C) 1996-2020 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: FreeBSD 13.0-CURRENT (arm64)
ncurses: ncurses 6.2.20200215 (compiled with 6.2)
libiconv: 1.16
libidn2: 2.3.0 (compiled with 2.3.0)
hcache backend: tokyocabinet 1.4.48

Compiler:
FreeBSD clang version 11.0.0 (g...@github.com:llvm/llvm-project.git 
llvmorg-11.0.0-0-g176249bd673)
Target: aarch64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin

Configure options: '--disable-fcntl' '--with-ssl=/usr' 
'--with-docdir=/usr/local/share/doc/mutt' '--sysconfdir=/usr/local/etc' 
'--enable-external-dotlock' '--enable-pop' '--enable-imap' 
'--enable-compressed' '--enable-sidebar' '--enable-autocrypt' 
'--with-sqlite3=/usr/local' '--enable-debug' '--disable-flock' '--enable-gpgme' 
'--without-gss' '--without-bdb' '--without-kyotocabinet' '--enable-hcache' 
'--without-qdbm' '--without-gdbm' '--with-tokyocabinet=/usr/local' 
'--with-libiconv-prefix=/usr/local' '--with-idn2=/usr/local' 
'--enable-locales-fix' '--enable-nls' '--with-sasl=/usr/local' '--enable-smtp' 
'--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man' 
'--disable-silent-rules' '--infodir=/usr/local/share/info/' 
'--build=aarch64-portbld-freebsd13.0' 'build_alias=aarch64-portbld-freebsd13.0' 
'CC=cc' 'CFLAGS=-O2 -pipe  -fstack-protector-strong -fno-strict-aliasing ' 
'LDFLAGS=  -fstack-protector-strong ' 'LIBS=' 'CPPFLAGS=' 'CPP=cpp'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -O2 -pipe  
-fstack-protector-strong -fno-strict-aliasing

Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  -USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  
+USE_SSL_OPENSSL  -USE_SSL_GNUTLS  +USE_SASL  -USE_GSS  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  +HAVE_FUTIMENS  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  +CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  +LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  +HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_LIBIDN2  +HAVE_GETSID  +USE_HCACHE  
+USE_SIDEBAR  +USE_COMPRESSED  -USE_INOTIFY  
-ISPELL

SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/local/share/mutt"
SYSCONFDIR="/usr/local/etc"
EXECSHELL="/bin/sh"
-MIXMASTER

To contact the developers, please mail to .
To report a bug, please contact the Mutt maintainers via gitlab:
https://gitlab.com/muttmua/mutt/issues

patch-1.5.0.ats.date_conditional.1
patch-1.5.6.cb.reverse_reply.2
patch-1.5.7.ust.maildir-mtime.2
patch-1.5.4.cd.ifdef.1
vvv.quote
vvv.initials

thanks,
--
J.


signature.asc
Description: PGP signature

Re: hcache and display options

[tech-lists]

On Wed, Oct 02, 2019 at 03:07:16PM +0100, tech-lists wrote:
[...]

thanks for the pointers. Does slang have any advantages over ncurses though? I
have both, and use slang in slrn. There is ncurses in the OS and a later
version is in ports (FreeBSD) 
--

J.


signature.asc
Description: PGP signature

hcache and display options

[tech-lists]

Hi,

When compiling mutt, I have several options for the header cache:

1. HCACHE_TOKYOCABINET
2. HCACHE_KYOTOCABINET
3. HCACHE_NONE
4. HCACHE_BDB

Which is "best"? I use mutt with imap directly. The machine it's on has an old
sse2/sse3 cpu, but 8GB RAM. The drive is SSD (230GB)

I also have these options:

5. NCURSES
6. SLANG

Which is best for use of mutt within screen(8) ?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Getting color on FreeBSD

[tech-lists]

On Thu, Aug 22, 2019 at 07:14:28PM -0500, Tim Chase wrote:

I'm a bit stuck trying to figure out why colors aren't working for me
on FreeBSD (where I understand that termcap is used rather than
terminfo).


How are you invoking mutt?

The only way I can get a mono mutt display is by invoking mutt with an empty
config file (as I have a .muttrc with color statements already):

touch .argaerg
mutt -F .argaerg

Have you tried copying the supplied sample.muttrc to $HOME/.muttrc and then
running mutt? It'll at least show you colour if $TERM is xterm-256color

If you installed mutt with pkg, colour will be enabled. Here's my mutt -v :

Mutt 1.12.1 (2019-06-15)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: FreeBSD 12.0-RELEASE-p10 (amd64)
ncurses: ncurses 5.9.20140222 (compiled with 5.9)
libiconv: 1.14
libidn2: 2.2.0 (compiled with 2.2.0)
hcache backend: Berkeley DB 5.3.28: (September  9, 2013)

Compiler:
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM
6.0.1)
Target: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin

[...]

Compile options:
-DOMAIN
-DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  -USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  
+USE_SSL_OPENSSL  -USE_SSL_GNUTLS  +USE_SASL  -USE_GSS  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  +HAVE_FUTIMENS  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  +CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  +LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_LIBIDN2  +HAVE_GETSID
+USE_HCACHE  
+USE_SIDEBAR  +USE_COMPRESSED  -USE_INOTIFY  
-ISPELL


--
J.


signature.asc
Description: PGP signature

Re: imap4s timeouts and closed connections

[tech-lists]

Hi,

On Sun, Jul 28, 2019 at 01:17:33PM -0400, José María Mateos wrote:


I also have Fastmail and also have these problem -- mailboxes are closed
and a malformed TLS package warning is shown. I haven't found a way to
solve this with any combination of timeouts, keepalive, etc. In the end,
this brought me back to solve whatever issues I had with offlineimap and
do everything locally now.


Please can you tell me what OS you were using and whether you were using
openssl or gnutls for ssl, when you were experiencing the problem?

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Composing ask From: address and arbitrary keys in PGP

[tech-lists]

On Thu, Aug 01, 2019 at 05:50:59AM +, Ryan Smith wrote:

The identity macro does work, but it will not work for setting custom
header in composing new emails as hdr is set before about sending
emails.
I tried gpgme which does not seems to give me any option to select
self encrypt key based on From: , but always use default key
Can you illustrate more on how to select signing key based on From:
in gpgme? gpgme seems also only uses default key as sign as if you
have multiple accounts and different for keys for each account.
Ryan


Sorry I wasn't clear. Re-reading what I wrote, seems to suggest I select
the From: and then the appropiate key gets auto-selected. That doesn't
happen. The default key remains the default key. If I select a different
From: and want a signing key for that identity, I select the appropriate
key from the gpg sign-as multi-selection.

The other way of doing it is to have two mutt sessions each running in
screen or tmux, each with different muttrc files with different
identities and different signing defaults. This is how I keep work 
emails amd mailing list emails separate.

--
J.


signature.asc
Description: PGP signature

Re: imap4s timeouts and closed connections

[tech-lists]

On Sun, Jul 28, 2019 at 07:59:58AM -0700, Kevin J. McCarthy wrote:


Actually, if you don't mind compiling out of git, perhaps you could try
the branch 'kevin/stable-poll-fix'.  I have a theory about what might be
the problem and would appreciate if you would give that branch a try.


Hi Kevin,

Yes I can do that. Not right this minute but hopefully later. Many
thanks for looking at this. I'll get back to you when done.

--
J.


signature.asc
Description: PGP signature

imap4s timeouts and closed connections

[tech-lists]

Hi,

context: Mutt 1.12.1 / freebsd12-stable

I'm using fastmail for all my mail and I access it with imap4s. Lately
I've been seeing timeouts, or a mailbox will just close [1], and yet my
connection (fibre) is stable. I've been using imap with mutt ever since 
direct imap support became available, and this is the first time I've

really had any problem with mutt in an imap context.

I have the following in my .muttrc:

set mail_check=90
set imap_keepalive=30
set timeout=15

I can be just reading mail in the mailbox then "connection closed"

How can I fix? I've done some searching about this but can't find much
for my version of mutt and what I did find was inconclusive. But it's an
issue that seems to come up repeatedly.

[1] doubly annoying because my lastread isn't recorded ie the mailbox
closes without synching.

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Composing ask From: address and arbitrary keys in PGP

[tech-lists]

On Fri, Jul 26, 2019 at 05:12:08AM +, g...@riseup.net wrote:

1. When composing messages, mutt ask To: or recipient adress and 
Subject: and then go to editor. How to make mutt ask for 
From: or sender address only and then go to editor?


I use this, in muttrc:

# my identities
macro compose v "^Uidentity_" "Select from"

alias identity_a0 tech-lists 
alias identity_a1 someotheraddress 

[...etc...]

and use v then hit tab to get a selectable list. This selected when
about to send the email. I'm unsure what the proper name for that part
of mutt is.

I use gpgme which selects the signing key based on From:

--
J.


signature.asc
Description: PGP signature

Re: mutt and clear-signing

[tech-lists]

On Wed, Jul 03, 2019 at 09:20:53AM +1000, m...@raf.org wrote:


be warned though that the SKS network (where you might get keys from)
has recently been attacked by the poisoning of some high profile keys
that, if fetched and imported, will break your gnupg installation.

see the following for more information and advice:

 https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f


thanks very much for this. what a nightmare!
--
J.


signature.asc
Description: PGP signature

mutt and clear-signing

[tech-lists]

Hi,

I'm using mutt v.1.12.0 on freebsd-current with gpgme. In my config, mutt will
verify clearsigned gpg sigs if the public key is on the gpg keyring.

But if the key is unknown, mutt will say the key is unknown, and this is
normal and expected.

What I want to happen is, if the key is unknown i'd like mutt to prompt
something like "get key y/n" or even automatically fetch the key and add
it to the keyring if the public key is valid. What's the best way to
accomplish this?

At the moment I have to open another term and gpg --recv-keys keyid

thanks,
--
J.


signature.asc
Description: PGP signature

Re: Bottom posting v top posting

[tech-lists]

On 13/05/2018 18:15, Martin Trautmann wrote:

IBTD. Major e-mail tools, such as outlook, failed to support proper threading. 
Writing on a smartphone here, I'm not even aware of an app with threading.


You're using K-9 mail which has apparently supported threading since 
4.390-beta, see 
http://grokbase.com/t/gg/k-9-mail/135pt36a12/conversation-threaded-view/oldest


I must admit that I don't know of an MUA that does not have threading 
capability in 2018. But I know nothing about outlook.



But are we still discussing bottom vs. top quoting? The here recommended style 
to me is known as INLINE QUOTING, where you do trim the quoting to the few 
lines which will help to understand the context of a discussion.


Oh I do that as well. I said:

Personally, if I need to quote someone back to themselves, I'll do it inline. 


But inline quoting has its own issues. Multiple inline quotes from 
multiple messages can get messy. IMOHO messier than just bottom posting, 
which is at least logically chronological.


--
J.

Re: Bottom posting v top posting

[tech-lists]

On 13/05/2018 00:52, Brian Salter-Duke wrote:

The use of phones for email
alters the game. It is time we gave up bottom posting!


No!! ;) and you're missing the point (IMOHO) :( basically, people 
quote back way too much. This is the issue. Most email apps allow 
threaded mail, so very little need to quote whole screeds. Personally, 
if I need to quote someone back to themselves, I'll do it inline.


just my 0.02 euros, generically because this client is thunderbird.
--
J.

Re: moving messages on imap4 server based on date received

[tech-lists]

On Sun, Oct 08, 2017 at 04:35:47PM -0500, Larry Rosenman wrote:

Whether you can run on YOUR server, I do not know, but I've been running 
this script for ~1 year.


Hi, thanks for the script, I've saved it as it may come in useful
one day. Unfortunately I'm not running my own mail server at this
time; I'm using FastMail so need to work around that.

archivemail *nearly* does what's needed, except that it saves to local
disk, whereas what I want is to save it in an archive folder on the
server, without compression or other encoding.

There's an add-on for Thunderbird that does exactly what's needed. It's
called awesome auto-archiver or something like that. Of course the
problem for me there is that it's thunderbird, and I want to run mutt
because it's elegant and lightweight and copes happily with thousands
of emails even on a low-powered netbook.

--
J.

Re: moving messages on imap4 server based on date received

[tech-lists]

On Thu, Sep 28, 2017 at 03:56:35PM -0400, Dan Ritter wrote:

On Thu, Sep 28, 2017 at 02:10:22PM +0100, tech-lists wrote:

Hello mutt-users@

I'm running mutt 1.9.1 (2017-09-22) on freebsd-11-stable.

What I'd like to have is, when mutt loads, it scans its subscribed
folders and moves the mail based on date received into preconfigured
mail folders. Either that, or maybe run another standalone program in a
screen or cron that does the same. I don't want to "download" the mail
at this stage - it needs to be moved around on the remote server.

Can mutt do this, or is there another program that does this with imap4?


If your IMAP server supports SIEVE, that is the easiest way to
get this done. Sorting will happen at delivery time.


Hi, sorry for the late reply

The reason I can't use SIEVE is because SIEVE rules act at delivery time
only. By delivery time, I mean the time they arrive on the imap server.

What I want to happen is, for emails already in folders on the imap
server, if they're over say 30 days old, for an automatic process to
move them into an archive folder on the same server.

thanks,
--
J.

Re: moving messages on imap4 server based on date received

[tech-lists]

On Thu, Sep 28, 2017 at 03:56:35PM -0400, Dan Ritter wrote:


If your IMAP server supports SIEVE, that is the easiest way to
get this done. Sorting will happen at delivery time.


yep it supports seive, but not every option, hopefully it will support
mive from folder by arrive date, for multiple folders.

thanks,
--
J.

moving messages on imap4 server based on date received

[tech-lists]

Hello mutt-users@

I'm running mutt 1.9.1 (2017-09-22) on freebsd-11-stable.

What I'd like to have is, when mutt loads, it scans its subscribed
folders and moves the mail based on date received into preconfigured
mail folders. Either that, or maybe run another standalone program in a
screen or cron that does the same. I don't want to "download" the mail
at this stage - it needs to be moved around on the remote server.

Can mutt do this, or is there another program that does this with imap4? 


thanks,
--
J.

Re: associating sig and other properties with "From:" drop-down in mutt

[tech-lists]

On Tue, Apr 12, 2016 at 10:56:29PM +0200, Wim wrote:

Hi,
what you could try is to associate various identitys with send-hooks
in this way:
send-hook . "source identity_a0"   # default config
send-hook "~f identity_a1" "source a1" # the a1 identity
send-hook "~f identity_a2" "source a2" # the a2 identity
and so on...
where "~f identity_a1" is one of your email identities and a1, a2 set the
various identity parameters, signatures, headers and stuff in seperate
files. Don't forget some parameters you'll have to set to zero, for example:
ignore * for the headers.
Don't know if this will work but if successfull post the results.


Thanks, I'll try that. My overriding concern is that it'll still give
the nifty drop-down-to-select.

--
J.

associating sig and other properties with "From:" drop-down in mutt

[tech-lists]

Hello list,

In my .muttrc I have a section that begins like this:
###
macro compose v "^Uidentity_" "Select from"
###

after this I have various addresses:

alias identity_a0 my-preferred-email-address 
alias identity_a1 my-work-email-address 

This setup works well, allowing me to set the From: from a drop-down
before I send.

What I'd like is, for each From: also associate a sig and other
characteristics, like whether by default the email should be
gpg-signed, what other headers it wants. Is there an elegant way to do
this? I don't want "being able to select the other address" to change,
hopefully that can remain as-is. What I want is the *consequences of
that selection* to change, so that on selection it's not just the
"From:" that changes, but the other stuff as well.

Many thanks,
--
J.