This POSIX function is defined in strings.h, so include it explicitly rather than relying on implicit inclusion through default feature-test macros. --- mmime.c | 1 + 1 file changed, 1 insertion(+) diff --git a/mmime.c b/mmime.c index ab5bcf4..6334569 100644 --- a/mmime.c +++ b/mmime.c @@ -12,6 +12,7 @@ #include <stdio.h> #include <stdlib.h> #include <string.h> +#include <strings.h> #include <time.h> #include <unistd.h> -- 2.37.3 -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/20221207213437.14008-1-mforney%40mforney.org.
ino64_t and off64_t are non-standard types and musl will no longer expose them without __LARGEFILE64_SOURCE in the next release. Internally, the kernel uses u64 and s64 for these fields, so replace them with uint64_t and int64_t respectively. --- mlist.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mlist.c b/mlist.c index 5debf99..20061d9 100644 --- a/mlist.c +++ b/mlist.c @@ -111,8 +111,8 @@ list(char *prefix, char *file) #include <sys/syscall.h> struct linux_dirent64 { - ino64_t d_ino; /* 64-bit inode number */ - off64_t d_off; /* 64-bit offset to next structure */ + uint64_t d_ino; /* 64-bit inode number */ + int64_t d_off; /* 64-bit offset to next structure */ unsigned short d_reclen; /* Size of this dirent */ unsigned char d_type; /* File type */ char d_name[]; /* Filename (null-terminated) */ -- 2.37.3 -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/85c82c7c2dd07febc84e0958244c7eb48e1a83de.1670448134.git.mforney%40mforney.org.
Alyssa Ross <hi@alyssa.is> writes: > Use the same check is blaze822() as in blaze822_file() to ensure that > we don't try to open /dev/stdin, which is non-POSIX. Thanks, applied. -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87o7zoc6h3.fsf%40vuxu.org.
Use the same check is blaze822() as in blaze822_file() to ensure that we don't try to open /dev/stdin, which is non-POSIX. --- blaze822.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/blaze822.c b/blaze822.c index 9262f6f..47f03a2 100644 --- a/blaze822.c +++ b/blaze822.c @@ -443,7 +443,10 @@ blaze822(char *file) if (!mesg) return 0; - fd = open(file, O_RDONLY); + if (strcmp(file, "/dev/stdin") == 0) + fd = dup(0); + else + fd = open(file, O_RDONLY); if (fd < 0) { free(mesg); return 0; -- 2.35.1 -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/20220523170921.2623516-1-hi%40alyssa.is.
> We usually use mblaze-profile(5) for that... perhaps something like > > Scan-Lines: 10 Hey. See github.com/leahneukirchen/mblaze/pull/223 Marko -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/962213915.39596.1647973690531%40localhost.
"'Marko Bauhardt' via mblaze" <mblaze@googlegroups.com> writes: >> Currently the length is hardcoded, but I'm willing to accept a patch; >> expressing the logic in shell didn't feel super straight forward however. :) > > Not sure if i have enough skills to apply a proper patch 🤓 > Anyway, how do you imagine the patch? Should be the length of the > messages computed relativ to …i dont know…. Or via env vars or a new > hard coded Value as patch and the User can decide if she/he wants to > have it, similar like other suckless Tools do it. We usually use mblaze-profile(5) for that... perhaps something like Scan-Lines: 10 But computing it relative to the terminal lines could also be an option. -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87r16vaw8a.fsf%40vuxu.org.
Hey leah, > > This has come up before: https://github.com/leahneukirchen/mblaze/issues/194 Ok nice. > > Currently the length is hardcoded, but I'm willing to accept a patch; > expressing the logic in shell didn't feel super straight forward however. :) Not sure if i have enough skills to apply a proper patch 🤓 Anyway, how do you imagine the patch? Should be the length of the messages computed relativ to …i dont know…. Or via env vars or a new hard coded Value as patch and the User can decide if she/he wants to have it, similar like other suckless Tools do it. Marko > -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/1954576594.33292.1647893753851%40localhost.
"'Marko Bauhardt' via mblaze" <mblaze@googlegroups.com> writes: > Hey. > When using mless, there are on top 6 messages visible followed by the > content of the selected message. > > Is there any convenient way to increase the length of the List of > messages?or would be patching the src the way to go? This has come up before: https://github.com/leahneukirchen/mblaze/issues/194 Currently the length is hardcoded, but I'm willing to accept a patch; expressing the logic in shell didn't feel super straight forward however. :) -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87zglobq3b.fsf%40vuxu.org.
Hey. When using mless, there are on top 6 messages visible followed by the content of the selected message. Is there any convenient way to increase the length of the List of messages?or would be patching the src the way to go? Thx Marko -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/1100144372.3767.1647506883156%40localhost.
Hello, I'm happy to announce a new release of "mblaze", a Unix command line mail client system in the spirit of RAND MH, but developed from scratch and focused on Maildir. This 1.2 release mainly adds bugfixes and small improvements. * Caution! The tools mdeliver and mexport were buggy in handling and generation of trailing empty lines in MBOX-RD. Do not import mbox files generated by mexport >=1.2 with mdeliver <1.2 if you require verbatim message delivery. * mshow: add "-A all" to render all attachments * msed: match header names case insensitively * mless: prefer setting LESSKEYIN and using .mlesskey * mcom: take Delivered-To into account for choosing From address * Many bug fixes. You can find mblaze source at https://git.vuxu.org/mblaze https://github.com/leahneukirchen/mblaze and release tarballs on https://github.com/leahneukirchen/mblaze/releases https://leahneukirchen.org/releases/mblaze-1.2.tar.gz Releases are also signed with signify(1) using http://leahneukirchen.org/releases/mblaze.pub namely: RWT/F+mCqnmHzj/+dB32aXOuZ+4Afcr3r6TOVHXGkRNCBExd3kS0tCnL There is a mailing list available at mblaze@googlegroups.com (see https://groups.google.com/forum/#!forum/mblaze or https://inbox.vuxu.org/mblaze/), and an IRC channel #vuxu on irc.libera.chat. Enjoy, -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ 50c164c88cc83b4f52691341ee14060da5a6f1859e86aa73ff595de4b410037f mblaze-1.2.tar.gz 5d8dc60abe88e90ebfddea0fa2049812c9c51b18d5fc5c8327d8aa8b098822cd mblaze-1.2.tar.gz.asc ae08ac91143b0685e7b69d6bdeab8604c683f67dee551e74bd52d19134c27d36 mblaze-1.2.tar.gz.sig -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87ee6h6aft.fsf%40vuxu.org.
[-- Attachment #1.1: Type: text/plain, Size: 2340 bytes --] Dear Leah, Thanks very much for your response. It answered my question and gives me a way forward. This response is much delayed due to "circumstances beyond my control" (narrowly escaping from my country of residence to my home country for leave in the midst of spiking Covid, vaccine shortages, etc.) I am just starting to go through the formail man page and seeing how I can figure out what might be blocking the effectiveness of the editlabel script. I will post again later. Thanks again, John Flood On Saturday, June 19, 2021 at 9:42:14 PM UTC+3 Leah Neukirchen wrote: > John Flood <jflo...@gmail.com> writes: > > > One of the reasons I became interested in mblaze was failure to get the > > editlabel <https://blitiri.com.ar/p/other/mutt-labels/> script to work > with > > mutt. When, e.g., cleaning up my INBOX it was easy with mutt to tag and > > move emails from the same address to a folder, but I also had emails, > say, > > from various students that I would wish to move to a common "student" > > folder by first labeling them and then filtering for the label and > moving > > them at once. > > > > My question here is about msed which I was able to use to add a label > (but > > not edit and existing one used by Gmail like one with "\Important"). > > However, even though I could add a new label which would appear in the > > output of msed, the change did not seem to affect the actual email > itself. > > If I used mhdr, the change would not appear. > > > > So, am I expecting something that msed was not designed to do or is > there a > > way to write the output of msed to the email itself. > > Yes, indeed msed only prints the message to standard output. > > I would not recommend using it to manipulate persisted messages as it > also unfolds the headers. > > You can use formail(1) like the editlabel script for that, it should > only touch affected lines. > > -- > Leah Neukirchen <le...@vuxu.org> https://leahneukirchen.org/ > -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/66089c35-2552-4d4c-82f6-a9bb5d2aba87n%40googlegroups.com. [-- Attachment #1.2: Type: text/html, Size: 3699 bytes --]
John Flood <jfloodcsc@gmail.com> writes: > One of the reasons I became interested in mblaze was failure to get the > editlabel <https://blitiri.com.ar/p/other/mutt-labels/> script to work with > mutt. When, e.g., cleaning up my INBOX it was easy with mutt to tag and > move emails from the same address to a folder, but I also had emails, say, > from various students that I would wish to move to a common "student" > folder by first labeling them and then filtering for the label and moving > them at once. > > My question here is about msed which I was able to use to add a label (but > not edit and existing one used by Gmail like one with "\Important"). > However, even though I could add a new label which would appear in the > output of msed, the change did not seem to affect the actual email itself. > If I used mhdr, the change would not appear. > > So, am I expecting something that msed was not designed to do or is there a > way to write the output of msed to the email itself. Yes, indeed msed only prints the message to standard output. I would not recommend using it to manipulate persisted messages as it also unfolds the headers. You can use formail(1) like the editlabel script for that, it should only touch affected lines. -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87mtrlsnlp.fsf%40vuxu.org.
[-- Attachment #1.1: Type: text/plain, Size: 1288 bytes --] One of the reasons I became interested in mblaze was failure to get the editlabel <https://blitiri.com.ar/p/other/mutt-labels/> script to work with mutt. When, e.g., cleaning up my INBOX it was easy with mutt to tag and move emails from the same address to a folder, but I also had emails, say, from various students that I would wish to move to a common "student" folder by first labeling them and then filtering for the label and moving them at once. My question here is about msed which I was able to use to add a label (but not edit and existing one used by Gmail like one with "\Important"). However, even though I could add a new label which would appear in the output of msed, the change did not seem to affect the actual email itself. If I used mhdr, the change would not appear. So, am I expecting something that msed was not designed to do or is there a way to write the output of msed to the email itself. -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/e48f8edf-a8ba-4690-a458-93f393d87124n%40googlegroups.com. [-- Attachment #1.2: Type: text/html, Size: 1617 bytes --]
[-- Attachment #1.1: Type: text/plain, Size: 4009 bytes --] Thanks very much! Not being a "professional", I had to google a bit in order to be sure of what to do. I think I'd done something similar once or twice. So, after saving your suggestion as a patch and using "git apply" in the local mblaze repository and then recompiling, when I reply with "mrep -nogroup", it works and eliminates "Cc:" completely! So, thanks very much for that option! However, we can still "agree to disagree", in that, although they may exist, I don't know of email programs with "Reply to all" as an automatic default and, if I was knowledgeable enough I would make a patch for a "-group" flag to force the group reply with "nogroup" as the default! Or, otherwise, cause mrep to require one of the two flags and give an error if flagless! My post to the group was prompted by a recent mistake have a somewhat embarrassing email go to someone's relatives when it was meant only for the individual. It was not disastrous, only embarrassing! Hopefully, "Once bitten, twice shy"! Whatever the case, I am grateful for: 1. Your provision of mblaze 2. Your prompt and practical response! Sincerely, John On Monday, May 24, 2021 at 6:46:36 PM UTC+3 Leah Neukirchen wrote: > John Flood <jflo...@gmail.com> writes: > > > I have been using mblaze for a certain number of weeks after using mutt > > (still installed) for several years. I am still getting used to it. > > > > I don't know if there is a better way of raising my issue, but I would > just > > note that from my point of view, the default action of mrep, which is > > "reply to all" has the result that, unless one is vigilant, as we all > know, > > one may end up sending messages to many people that may contain > information > > intended for only one or a few. As a result, one may unintentionally end > > up offending some, causing division in a group or simply spreading > > information that is better kept confidential. > > > > So, I am just expressing the wish that there was a way for one to make a > > more deliberate choice to "reply to all" in order to avoid inadvertent > > mistakes. With vim as an editor, it is, of course, very easy to delete > all > > Cc: addresses, but occasionally we all do things in a hurry or when > > distracted and some people even make the mistake when there is a > deliberate > > choice as in Gmail itself. > > I disagree, in 99% of cases, Reply All is what you want, and as you > say, the adresses are shown and furthermore, it's easier to delete > messages than to look them up and add them manually. > > So mrep will definitely keep Reply All as default, but > this does not mean we can't add "reply directly" command or flag. > I think this just needs to toggle the Cc: generation. > > Try this: > > diff --git a/mcom b/mcom > index 057a998..50b48cb 100755 > --- a/mcom > +++ b/mcom > @@ -110,6 +110,7 @@ defaultc=e > hdrs= > resume= > noquote= > +nogroup= > case "$0" in > *mcom*) > hdr=to > @@ -217,6 +218,9 @@ case "$0" in > -noquote) > noquote=1 > shift;; > + -nogroup) > + nogroup=1 > + shift;; > -??*) > hdr=${1#-} > shift;; > @@ -357,10 +361,12 @@ fi > to=$(mhdr -d -h reply-to "$1") > [ -z "$to" ] && to=$(mhdr -d -h from "$1") > printf 'To: %s\n' "$to" > - printf 'Cc: %s\n' \ > - "$(mhdr -d -A -h to:cc: "$1" | > - notmine |grep -Fv -e "$to" | > - ouniq |commajoin)" > + if [ -z "$nogroup" ]; then > + printf 'Cc: %s\n' \ > + "$(mhdr -d -A -h to:cc: "$1" | > + notmine |grep -Fv -e "$to" | > + ouniq |commajoin)" > + fi > printf 'Bcc: \n' > printf '%s\n' "$hdrs" | awk '{ print }' | > msed "/body/d" - > > > hth, > -- > Leah Neukirchen <le...@vuxu.org> https://leahneukirchen.org/ > -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/d4f0d312-d47d-4d01-af54-dfff59cee0cdn%40googlegroups.com. [-- Attachment #1.2: Type: text/html, Size: 5641 bytes --]
John Flood <jfloodcsc@gmail.com> writes: > I have been using mblaze for a certain number of weeks after using mutt > (still installed) for several years. I am still getting used to it. > > I don't know if there is a better way of raising my issue, but I would just > note that from my point of view, the default action of mrep, which is > "reply to all" has the result that, unless one is vigilant, as we all know, > one may end up sending messages to many people that may contain information > intended for only one or a few. As a result, one may unintentionally end > up offending some, causing division in a group or simply spreading > information that is better kept confidential. > > So, I am just expressing the wish that there was a way for one to make a > more deliberate choice to "reply to all" in order to avoid inadvertent > mistakes. With vim as an editor, it is, of course, very easy to delete all > Cc: addresses, but occasionally we all do things in a hurry or when > distracted and some people even make the mistake when there is a deliberate > choice as in Gmail itself. I disagree, in 99% of cases, Reply All is what you want, and as you say, the adresses are shown and furthermore, it's easier to delete messages than to look them up and add them manually. So mrep will definitely keep Reply All as default, but this does not mean we can't add "reply directly" command or flag. I think this just needs to toggle the Cc: generation. Try this: diff --git a/mcom b/mcom index 057a998..50b48cb 100755 --- a/mcom +++ b/mcom @@ -110,6 +110,7 @@ defaultc=e hdrs= resume= noquote= +nogroup= case "$0" in *mcom*) hdr=to @@ -217,6 +218,9 @@ case "$0" in -noquote) noquote=1 shift;; + -nogroup) + nogroup=1 + shift;; -??*) hdr=${1#-} shift;; @@ -357,10 +361,12 @@ fi to=$(mhdr -d -h reply-to "$1") [ -z "$to" ] && to=$(mhdr -d -h from "$1") printf 'To: %s\n' "$to" - printf 'Cc: %s\n' \ - "$(mhdr -d -A -h to:cc: "$1" | - notmine |grep -Fv -e "$to" | - ouniq |commajoin)" + if [ -z "$nogroup" ]; then + printf 'Cc: %s\n' \ + "$(mhdr -d -A -h to:cc: "$1" | + notmine |grep -Fv -e "$to" | + ouniq |commajoin)" + fi printf 'Bcc: \n' printf '%s\n' "$hdrs" | awk '{ print }' | msed "/body/d" - hth, -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87wnro878n.fsf%40vuxu.org.
[-- Attachment #1.1: Type: text/plain, Size: 1900 bytes --] I have been using mblaze for a certain number of weeks after using mutt (still installed) for several years. I am still getting used to it. I don't know if there is a better way of raising my issue, but I would just note that from my point of view, the default action of mrep, which is "reply to all" has the result that, unless one is vigilant, as we all know, one may end up sending messages to many people that may contain information intended for only one or a few. As a result, one may unintentionally end up offending some, causing division in a group or simply spreading information that is better kept confidential. So, I am just expressing the wish that there was a way for one to make a more deliberate choice to "reply to all" in order to avoid inadvertent mistakes. With vim as an editor, it is, of course, very easy to delete all Cc: addresses, but occasionally we all do things in a hurry or when distracted and some people even make the mistake when there is a deliberate choice as in Gmail itself. I am not a proficient programmer, but when I saw that the mcom script was a bash script, I just hacked it and added an echo command to create a warning which has ended up appearing at the top of the draft when it opens and which I then need to delete before sending, but, at least it's a reminder. So, I'm just wondering whether it would be all that difficult to make an alternate command like "mgrp" that would replace the current "mrep" and a new "mrep" that would not reply to all. Thanks, John Flood -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/e2840d82-89c6-4cc7-8a69-31b158b27e63n%40googlegroups.com. [-- Attachment #1.2: Type: text/html, Size: 2277 bytes --]
Hello, I'm happy to announce a new release of "mblaze", a Unix command line mail client system in the spirit of RAND MH, but developed from scratch and focused on Maildir. This 1.1 release mainly adds bugfixes and small improvements. * mcom: allow tilde prefixed path for profile's outbox setting * mcom: detect and report mmime errors * add contrib/mmailto, a handler for mailto: links * Bug fixes. You can find mblaze source at https://git.vuxu.org/mblaze https://github.com/leahneukirchen/mblaze and release tarballs on https://github.com/leahneukirchen/mblaze/releases http://leahneukirchen.org/releases/mblaze-1.1.tar.gz Releases are also signed with signify(1) using http://leahneukirchen.org/releases/mblaze.pub namely: RWT/F+mCqnmHzj/+dB32aXOuZ+4Afcr3r6TOVHXGkRNCBExd3kS0tCnL There is a mailing list available at mblaze@googlegroups.com (see https://groups.google.com/forum/#!forum/mblaze or https://inbox.vuxu.org/mblaze/), and an IRC channel #vuxu on irc.freenode.net. Enjoy, -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ edd8cb86f667543e703dee58263b81c7e47744339d23ebbb6a43e75059ba93b1 mblaze-1.1.tar.gz bc4d9a51273fe6fb05090f073cb4da162934d39fcc2a2318b396397ab822b12d mblaze-1.1.tar.gz.asc b8eee86b27aeb738d031152328ccfd52509a908de6003f85870c6f4bc54310d2 mblaze-1.1.tar.gz.sig -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/874kjjecx3.fsf%40vuxu.org.
Hi Pierre Long after the fact but here is my reply. > The following works with vim. It requires fzf and fzf.vim. > > Once in a while, you can use > maddr \| sort \| uniq > ~/my.contacts > to dump all contacts found in your emails in that file. > > Then in .vimrc: > inoremap <expr> <c-x><c-k> fzf#vim#complete('cat ~/my.contacts') > will let you complete emails inside vim using fzf when writing an email in > vim. Thank you for this! I have switched to vis[0] as my email editor but it looks like there is a fzf plugin[1] for it as well. I may try this approach in the future! Cheers, Silvan [0] https://git.sr.ht/~martanne/vis [1] https://github.com/guillaumeboudon/vis-fzf > > Best wishes, > Pierre > > On Saturday, July 6, 2019 at 5:02:13 PM UTC-4 Silvan Jegen wrote: > >> Heyho >> >> Ideally I don't want to type out people's whole email addresses when >> composing emails. My first thought was to use an alias file with my >> SMTP client (msmtp). This works fine for sending emails, except that >> the aliases are not replaced in the mail headers. That means if a person >> replies to all people in a mail from me, and the CC header contains an >> alias like 'friend1', the email addressed to 'friend1' one will never >> arrive since it's not a valid email address. >> >> Currently I am using a new approach where I simply run 'sed' over the >> headers of an email at composiition time to replace all my aliases with >> the proper email addresses. >> >> I feel like there should be a more elegant solution to this (involving >> 'msed' being invoked before passing an email to the sendmail program >> perhaps?). Is there an easy way to get simple email address aliases >> working that I am missing? >> >> >> Cheers, >> >> Silvan >> -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/2OG00NPSPEOMF.2C9CX428JY0X7%40homearch.localdomain.
[-- Attachment #1: Type: text/plain, Size: 380 bytes --] -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/SN6PR05MB57752FC8DCFF7E054F23B79BCF0F0%40SN6PR05MB5775.namprd05.prod.outlook.com. [-- Attachment #2: Type: text/html, Size: 2132 bytes --]
Hello, I'm happy to announce a new release of "mblaze", a Unix command line mail client system in the spirit of RAND MH, but developed from scratch and focused on Maildir. This 1.0 release adds three breaking changes(!) and fixes bugs, updating is highly recommended. * Caution! Backwards incompatible changes: * As a message name, `-` now refers to the message on the standard input, and not the the previous message anymore. Use `.-` to refer to the previous message in a short way. The tools will print a warning if you use `-` and the standard input comes from a TTY. * mpick: use the -F flag to read script files. * mpick: remove msglist support, use plain mmsg(7) arguments. * Many mblaze tools now make use of pledge(2) on OpenBSD. * add contrib/mcount, a tool to count mails * mrep: use Reply-From configuration to find From header * Many bug fixes. You can find mblaze source at https://git.vuxu.org/mblaze https://github.com/leahneukirchen/mblaze and release tarballs on https://github.com/leahneukirchen/mblaze/releases http://leahneukirchen.org/releases/mblaze-1.0.tar.gz Releases are also signed with signify(1) using http://leahneukirchen.org/releases/mblaze.pub namely: RWT/F+mCqnmHzj/+dB32aXOuZ+4Afcr3r6TOVHXGkRNCBExd3kS0tCnL There is a mailing list available at mblaze@googlegroups.com (see https://groups.google.com/forum/#!forum/mblaze or https://inbox.vuxu.org/mblaze/), and an IRC channel #vuxu on irc.freenode.net. Enjoy, -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ 316061e8d6cf6455a91105c550669638f6e0288c53c7185fb2429c54e80f2335 mblaze-1.0.tar.gz c8cea1decdc16c5ff4e42b4f5bc262929dcf2b891ad028931d997412818ee44b mblaze-1.0.tar.gz.asc 0a94249cce7872e96ff6621f88fec4081f63b58b307fe580409f6048522c4ae3 mblaze-1.0.tar.gz.sig -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87imcjq82f.fsf%40vuxu.org.
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --] -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/DB8PR03MB61714DBF4B6DD757CB173D4AB45B0%40DB8PR03MB6171.eurprd03.prod.outlook.com. [-- Attachment #1.2: Type: text/html, Size: 1001 bytes --] [-- Attachment #2: LOTTO.tif --] [-- Type: image/tiff, Size: 197896 bytes --]
Hi, the next release of mblaze will be the 1.0, and I've taken the opportunity to do a few breaking changes. I have implemented the first and pushed it to master, so if you use mblaze from master, please read this: * Caution! Backwards incompatible changes: * As a message name, `-` now refers to the message on the standard input, and not the the previous message anymore. Use `.-` to refer to the previous message in a short way. The tools will print a warning if you use `-` and the standard input comes from a TTY. I think daily usage has shown that this use of - is more useful in general, and more consistent with other Unix tools. The other planned breaking change will make mpick use mmsg(7) arguments, too. But it is up to Duncan to implement this. Cheers, -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/878sg0wr8y.fsf%40vuxu.org.
[-- Attachment #1.1: Type: text/plain, Size: 1748 bytes --] Hi Silvan, The following works with vim. It requires fzf and fzf.vim. Once in a while, you can use maddr \| sort \| uniq > ~/my.contacts to dump all contacts found in your emails in that file. Then in .vimrc: inoremap <expr> <c-x><c-k> fzf#vim#complete('cat ~/my.contacts') will let you complete emails inside vim using fzf when writing an email in vim. Best wishes, Pierre On Saturday, July 6, 2019 at 5:02:13 PM UTC-4 Silvan Jegen wrote: > Heyho > > Ideally I don't want to type out people's whole email addresses when > composing emails. My first thought was to use an alias file with my > SMTP client (msmtp). This works fine for sending emails, except that > the aliases are not replaced in the mail headers. That means if a person > replies to all people in a mail from me, and the CC header contains an > alias like 'friend1', the email addressed to 'friend1' one will never > arrive since it's not a valid email address. > > Currently I am using a new approach where I simply run 'sed' over the > headers of an email at composiition time to replace all my aliases with > the proper email addresses. > > I feel like there should be a more elegant solution to this (involving > 'msed' being invoked before passing an email to the sendmail program > perhaps?). Is there an easy way to get simple email address aliases > working that I am missing? > > > Cheers, > > Silvan > -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/37d1f718-192a-4bb3-93ee-a89db62604f1n%40googlegroups.com. [-- Attachment #1.2: Type: text/html, Size: 2548 bytes --]
Here are some of the new features of mpick(1): mpick can now also act as interpreter to for mpick script files instead of only allowing to supply expression through arguments. Another new feature is redirecting mail paths matching expressions to files or processes, similar to redirects work in awk. The following example script moves matching mails into another maildir by piping their path into mrefile(1). By using mrefiles -v flag and using `? skip : print` the output of this mpick script will be either the updated path of matching mails or the original path of mails that did not match the expressions. This would also work with other tools like mflag(1). #!/usr/bin/mpick ("list-id".addr ~~ "*.project1.com" |"mrefile -v ~/mail/project1" || "list-id".addr ~~ "*.project2.com" |"mrefile -v ~/mail/project2") ? skip : print Another new feature is assigning expressions to variables, to make it a bit easier to maintain large filter scripts. #!/usr/bin/mpick let project1 = "list-id".addr == "project1.com" |"mrefile -v ~/mail/project1" let project2 = "list-id".addr == "project2.com" |"mrefile -v ~/mail/project2" in (project1 || project2) ? skip : print Another example (with a second expression for project1) would be: #!/usr/bin/mpick let project1 = "list-id".addr == "project1.com" || "to".addr == "me@project1.com" let project2 = "list-id".addr == "project2.com" let move = project1 |"mrefile -v ~/mail/project1" || project2 |"mrefile -v ~/mail/project2" in move ? skip : print The pipe (|"prog") can be replaced with >"newfile" or >>"append" to write or append matching mails to files. Cheers, Duncan -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/2MOZWQEK1UKMR.3BJG24O93LE6X%40tux.localdomain.
Hello, I'm happy to announce a new release of "mblaze", a Unix command line mail client system in the spirit of RAND MH, but developed from scratch and focused on Maildir. This release adds new features and fixes bugs, updating is highly recommended. * All tools now follow symlinks to mails. * mcom: add preview alias for show command. * mrep/mbnc: allow only one message as argument. * maddr: add -d to only print display name. * mthread: add -r to reverse top-level order. * mlist: print number of matches when message selection is in place. * mpick: many improvements. * Many bug fixes. You can find mblaze source at https://git.vuxu.org/mblaze https://github.com/leahneukirchen/mblaze and release tarballs on https://github.com/leahneukirchen/mblaze/releases http://leahneukirchen.org/releases/mblaze-0.7.tar.gz Releases are also signed with signify(1) using http://leahneukirchen.org/releases/mblaze.pub namely: RWT/F+mCqnmHzj/+dB32aXOuZ+4Afcr3r6TOVHXGkRNCBExd3kS0tCnL There is a mailing list available at mblaze@googlegroups.com (see https://groups.google.com/forum/#!forum/mblaze or https://inbox.vuxu.org/mblaze/), and an IRC channel #vuxu on irc.freenode.net. Enjoy, -- Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/ 804feb62551a64574bbf1b80fadee751abe5657c94205f96ca884f739d3d33fc mblaze-0.7.tar.gz 2713b1a5f8372275b6e4c1cb6c5aa5b2e6935b277fc585559c24405f849008d9 mblaze-0.7.tar.gz.asc befc153579607031bbafbbfa3e17ef0d26ebcfad09f680351896721ea4b0833b mblaze-0.7.tar.gz.sig -- You received this message because you are subscribed to the Google Groups "mblaze" group. To unsubscribe from this group and stop receiving emails from it, send an email to mblaze+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mblaze/87a729gmqq.fsf%40vuxu.org.