Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 21/02/13 08:03PM, Sam Kuper wrote: On Fri, Feb 12, 2021 at 01:30:04PM +0100, Angel M Alganza wrote: I did the same myself for years and also switched to ssmtp. But I belive ssmtp was discontinued, and now I'm using msmtp: https://marlam.de/msmtp/ I couldn't be happier! A queue script is included with msmtp, so you can have the best of both worlds :) https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD I went ahead tonight and compiled msmtp from source to get version 1.8.14. I was previously on 1.8.8. I did the steps suggested in the link you provided. Everything worked well. Then I thought I would test this queuing functionality. I disconnected from my network and sent a test email. It promptly popped up in the queue directory. So far so good. I reconnected to my network and waited expectantly for the queued mails to be sent. They just sat there. I looked through the source of the msmtpq script and AFAICT queued emails will *not* be sent until the next attempt to send a mail. So I tested this and sure enough the queue flushed itself and my earlier queued email was sent. As I do not consider myself competent in shell scripting, am I reading the source correctly? Is there an obvious way forward to check periodically for regaining the network connection and flushing the queue? If there is built-in functionality to do this, I am not finding it. TIA! -- Wishing you only the best, boB Stepp
Re: How to generate html mime message?
On Fri, Feb 12, 2021 at 10:19:07PM -, Grant Edwards wrote: > After a couple years of that, they turned of the SMTP server, so you > can only use Outlook or the OWA web API. No more using mutt for > work... Off-topic, but DavMail might let you resume using Mutt at work. Or switch jobs, since that employer doesn't seem to be a good one. -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: remove restriction on line length in mutt compose
On Saturday, February 13, 2021, 9:58:59 PM CST, Paul Gilmartin wrote: On 2021-02-13, at 18:37:20, Globe Trotter wrote: > > I appear to have hit some key while using compose in mutt, and the result is > that I end on a new line after a certain length of characters in a new line. > What controls this? It is not a vi issue because the editor does no wrap > after even a very long, as used to be the case until earlier today. > Perhaps obeying RFC 821: text line The maximum total length of a text line including the is 1000 characters (but not counting the leading dot duplicated for transparency). -- gil Sorry, no, the linebreak happens at like 80. Can i forcibly set it at 1000, say?
Re: remove restriction on line length in mutt compose
On 2021-02-13, at 18:37:20, Globe Trotter wrote: > > I appear to have hit some key while using compose in mutt, and the result is > that I end on a new line after a certain length of characters in a new line. > What controls this? It is not a vi issue because the editor does no wrap > after even a very long, as used to be the case until earlier today. > Perhaps obeying RFC 821: text line The maximum total length of a text line including the is 1000 characters (but not counting the leading dot duplicated for transparency). -- gil
Re: [unixbhas...@gmail.com: Notify-send pop up for specific mails]
On 14Feb2021 06:48, Bhaskar Chowdhury wrote: >.but depending too much of other software makes it fragile and >prone to >error and least to say it is complex. Aye. But you asked. You can see from the opening comment of the alert script: # Write a possibly-colourised string to the alert log. that it has evolved a bit over time. >Ordinary mortals(i.e me) who has less technical bend of mind, will run >away from this. The core point here is the flow: - getmail => folder - mailfiler to file messages from the folder - some messages run the alert script, which contains whatever platform-specific popup incantation is required All the rest has to do with my environment. If you're using fetchmail+procmail, for example, you just need an "alert" rule at the right points in your rules. >I do understand simplicity can not achieved without by digging and >getting into the rabbit >hole...again but...how many are willing(including me, I am an truest sense lazy >person) ... You can use all my code of course. I'm well aware that even taking what's needed (==> implied, the box of tissues effect) and putting it into your own setup is not necessarily trivial. >Not to deny, I do fall on fetchmail , procmail et al along with >mutt(the love for something do wonder) , but more to it ...nope... > >>The "desktop alert" part of that script is in the $to_desktop >>if-statement at the bottom. Presently I'm on a Mac and use the >>"terminal-notifier" command to issue a normal Mac Notification popup. >>I'd be using whatever Linux desktop notification command line were >>suitable were I on Linux. >> >notify-send is the "lightest" and "efficient" way of doing it on Linux. Thanks. I'll look it up and stick it in. The whole point of the script is to remove platform "how do I alert" from everything else. >Finally, I don't have the ability to create something native(think of >it as >excuse not to put effort,if you like :) ) OR we don't want mutt to be >convoluted >with some "airy-fairy" stuff. > >I am happy with it's limitation(partly because of my lack of understanding and >as mentioned ability to extends it,being using it for long time >though). Incremental change. Start with something basic. Modify it to better fit what you actually desire as its shortcomings become apparent. That's what I do. I've just been doing it a bit longer. For example, your own "alert" script might just directly invoke notify-send and do nothing else. Mine started by writing coloured alerts to a text file, nothing else. Then stick your own "alert" in your rules, and modify alert separately without needing to hack outside the script. Cheers, Cameron Simpson
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On Sun, Feb 14, 2021 at 02:43:32AM +0100, Angel M Alganza wrote: >On Sun, Feb 14, 2021 at 02:35:38AM +0100, Angel M Alganza wrote: >>On Sat, Feb 13, 2021 at 08:03:49PM +, Sam Kuper wrote: >>> On Fri, Feb 12, 2021 at 01:30:04PM +0100, Angel M Alganza wrote: On Mon, Feb 01, 2021 at 04:34:47PM -, Grant Edwards wrote: > I maintained a local queueing MTA for many years, but after > multiple screwups where mail wasn't getting sent (and I didn't > find out in a timely manner) I switched to a non-queueing MTA > (e.g. ssmtp) and later to mutt's SMTP support. I did the same myself for years and also switched to ssmtp. But I belive ssmtp was discontinued, and now I'm using msmtp: https://marlam.de/msmtp/ I couldn't be happier! >>> >>> A queue script is included with msmtp, so you can have the best of >>> both worlds :) >>> >>> https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD >> >> You proved me wrong: I could be happier! >> And I am, since I'm sending this through the msmtp queue. Yay! >> >> Thanks a lot. > > I'm replying to myself to add: send is super-fast now, instant > actually, from Mutt! I love it! Yes, it's great :) I have CC'd Martin Lambers (author of msmtp). Thank you, Martin :) And thank you to Kevin as always, for Mutt :) -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On Sun, Feb 14, 2021 at 02:35:38AM +0100, myself wrote: And I am, since I'm sending this through the msmtp queue. Yay! I'm replying to myself to add: send is super-fast now, instant actually, from Mutt! I love it! Cheers, Ángel
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 21/02/14 10:52AM, Cameron Simpson wrote: On 12Feb2021 23:20, boB Stepp wrote: something I like working with notmuch. I wish I could use notmuch's tagging capabilities from within Mutt in the sense of adding multiple tags to a single email or a set of tagged emails. But the only example of an approach is to try to adapt the macro I cited earlier in this thread which deletes the inbox tag. I see how to modify this to do *one* tag, but that would be hard-coded and not very flexible or useful. I'm sure there must be a way to write a macro to allow for me to enter multiple tags for notmuch, but I don't know enough about Mutt macros to see a way forwards yet. "notmuch tag" itself accepts multiple tags. Write a small shell script to prompt for the tags to change (in the same form as notmuch expects i.e. +tag and -tag) which then invokes notmuch. If you mean this macro: macro index \ "set my_old_pipe_decode=\$pipe_decode my_old_wait_key=\$wait_key nopipe_decode nowait_key\ notmuch-mutt tag -- -inbox\ set pipe_decode=\$my_old_pipe_decode wait_key=\$my_old_wait_key" \ "notmuch: remove message from inbox" it: - saves the pipe_decode and wait_key settings, and turns them off - pipes the current message through notmuch-mutt to remove the "inbox" tag - restores the old pipe_decode and wait_key settings The $my_blah= is a standard mutt hack because there's no "push temporary setting or value", and there are no settings called my_*. So people use $my_blah for "user variables". Piping the whole message through notmuch lets notmuch-mutt get the message-id in order to know which item to tag or untag. The it passes "id:$mid" to notmuch, where $mid is the message id. That's the mechanism. This is all starting to make sense. With the suggestions below I think I might be able to attack this. Many thanks, Cameron! To tag things interactively you have 2 issues: - specifying the messages to tag - specifying the tag changes For the latter I'd have a shell script which prompted for that, then ran notmuch. For the former, from inside mutt, I'd think there are 2 ways forward. With a single message you can just pipe it straight into the script, like the above macro does. With multiple messages I think I would tag them, and pipe all of them _separately_ through the script. Now, there are some ways to make that more convenient, particularly these settings: set auto_tag=yes set pipe_split=yes auto_tag=yes causes mutt to apply commands to all tagged messages (if any) or just the current message (if nothing tagged). pipe_split=yes causes mutt to run separate pipes per message when it pipes multiple messages, instead of concatenating them and running one pipe. You want that for notmuch-mutt. The notmuch-mutt script in the example above expects exactly one message on its input, _entirely_ to grab its message-id. So we want pipe_split-yes to invoke the script once for each message. Regarding prompting, I'd write a script like this (untested): #!/bin/sh set -ue echo -n "Enter tags to change (-tag, +tag): " >/dev/tty read tags -- Wishing you only the best, boB Stepp
remove restriction on line length in mutt compose
Hi, I appear to have hit some key while using compose in mutt, and the result is that I end on a new line after a certain length of characters in a new line. What controls this? It is not a vi issue because the editor does no wrap after even a very long, as used to be the case until earlier today. Thanks in advance!
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On Sat, Feb 13, 2021 at 08:03:49PM +, Sam Kuper wrote: On Fri, Feb 12, 2021 at 01:30:04PM +0100, Angel M Alganza wrote: I couldn't be happier! A queue script is included with msmtp, so you can have the best of both worlds :) You proved me wrong: I could be happier! And I am, since I'm sending this through the msmtp queue. Yay! Thanks a lot. Cheers, Ángel
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 21/02/13 08:03PM, Sam Kuper wrote: A queue script is included with msmtp, so you can have the best of both worlds :) https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD Thanks for this link! -- Wishing you only the best, boB Stepp
Re: [unixbhas...@gmail.com: Notify-send pop up for specific mails]
On 11:24 Sun 14 Feb 2021, Cameron Simpson wrote: On 13Feb2021 19:29, Bhaskar Chowdhury wrote: On 07:40 Sat 13 Feb 2021, Cameron Simpson wrote: On 12Feb2021 09:36, Kevin J. McCarthy wrote: On Fri, Feb 12, 2021 at 09:59:38AM +0530, Bhaskar Chowdhury wrote: The problem it pops up for every new mail arrive. [...] For more sophisticated notification, you'll need to use another tool. For xample, my own new mail desktop notifications happen from my mail filer, not from mutt. This has the advantage that they still happen when mutt is closed (if you can call that an advantage). How?? Show us...share with the people .. Ok I collect my email with getmail, deliver to my local "+spool" mail folder, a Maildir (~/mail/spool). I filter my messages using mailfer: https://pypi.org/project/cs.app.mailfiler/ which monitors multiple Maildirs for new messages, and files them according to per-folder rules. So it watches spool, spool-in, spool-out, spool-to-phone etc. "spool" winnows some spam and lets the rest through to spool-in. spool-in files to my inbox, various mailing list folders etc. Anything not matched lands in +UNKNOWN. It is mostly spam. spool-out is what mutt's $record is set to - mutt saves sent mail there and mailfiler refiles it. spool-to-phone just has a rule to forward to my phone's email account. So, alerts. Mailfiler rules are usually quite simple, like this: !me Work from:(ALERT) which says to match messages from addresses in the group "alert" and do 2 things: - "me" save a copy in my +me folder, my "priority inbox" - "!" run the $ALERT command with the message and save a copy to the targets named in $ALERT_TARGETS They're set like this: ALERT=alert ALERT_TARGETS="F,spool-to-phone" So $ALERT runs my "alert" command, a script. Details below. $ALERT_TARGETS says: - "F" (F)lag the message (same as mutt's (F)lag command) so that it is highlighted in mutt's index - "spool-to-phone" save a copy in my +spool-to-phone folder, which mailfiler also monitors (its rules say forward a copy to my phone's email account) The desktop popup comes from my "alert"r script: https://hg.sr.ht/~cameron-simpson/css/browse/bin/alert?rev=tip That will issue alerts to a variety of places depending on envvars and options particularly my dlog (a timestamped text log I use for reviewing things, since my invoicing system is a ghastly hack held together with string) and to the desktop. Thanks! .but depending too much of other software makes it fragile and prone to error and least to say it is complex. Ordinary mortals(i.e me) who has less technical bend of mind, will run away from this. I do understand simplicity can not achieved without by digging and getting into the rabbit hole...again but...how many are willing(including me, I am an truest sense lazy person) ... Anyway, your manipulation to get the simple task done very commanding ,alas! If I could follow. Not to deny, I do fall on fetchmail , procmail et al along with mutt(the love for something do wonder) , but more to it ...nope... The "desktop alert" part of that script is in the $to_desktop if-statement at the bottom. Presently I'm on a Mac and use the "terminal-notifier" command to issue a normal Mac Notification popup. I'd be using whatever Linux desktop notification command line were suitable were I on Linux. notify-send is the "lightest" and "efficient" way of doing it on Linux. I presume there _is_ a standard way to issue a popup alert on Linux systems these days? I used to just always run a permanent very short full-width terminal across the top of the screen tailing a log file myself, crude but effective. The same terminal also accepted commands if you typed them. Anyway, that is how this is hooked into my email. Suggestions for current Linux or other UNIX desktop popup command line tools welcomed. As mentioned use notify-send. Finally, I don't have the ability to create something native(think of it as excuse not to put effort,if you like :) ) OR we don't want mutt to be convoluted with some "airy-fairy" stuff. I am happy with it's limitation(partly because of my lack of understanding and as mentioned ability to extends it,being using it for long time though). Cheers, Cameron Simpson signature.asc Description: PGP signature
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On Sun, Feb 14, 2021 at 11:00:45AM +1100, Cameron Simpson wrote: > On 13Feb2021 20:03, Sam Kuper wrote: >> A queue script is included with msmtp, so you can have the best of >> both worlds :) >> >> https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD > > Ah, I missed that. Nice. > > Though I still like a local system MTA so that scripts and cron etc > etc can also send email natively. The two approaches can coexist happily on the same machine: - a local MTA for cron, etc.; and - msmtpq for use by Mutt for outbound mail. -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: [unixbhas...@gmail.com: Notify-send pop up for specific mails]
On 13Feb2021 19:29, Bhaskar Chowdhury wrote: >On 07:40 Sat 13 Feb 2021, Cameron Simpson wrote: >>On 12Feb2021 09:36, Kevin J. McCarthy wrote: >>>On Fri, Feb 12, 2021 at 09:59:38AM +0530, Bhaskar Chowdhury wrote: The problem it pops up for every new mail arrive. [...] >>>For more sophisticated notification, you'll need to use another tool. >> >>For xample, my own new mail desktop notifications happen from my mail >>filer, not from mutt. This has the advantage that they still happen when >>mutt is closed (if you can call that an advantage). >> >How?? Show us...share with the people .. Ok I collect my email with getmail, deliver to my local "+spool" mail folder, a Maildir (~/mail/spool). I filter my messages using mailfer: https://pypi.org/project/cs.app.mailfiler/ which monitors multiple Maildirs for new messages, and files them according to per-folder rules. So it watches spool, spool-in, spool-out, spool-to-phone etc. "spool" winnows some spam and lets the rest through to spool-in. spool-in files to my inbox, various mailing list folders etc. Anything not matched lands in +UNKNOWN. It is mostly spam. spool-out is what mutt's $record is set to - mutt saves sent mail there and mailfiler refiles it. spool-to-phone just has a rule to forward to my phone's email account. So, alerts. Mailfiler rules are usually quite simple, like this: !me Work from:(ALERT) which says to match messages from addresses in the group "alert" and do 2 things: - "me" save a copy in my +me folder, my "priority inbox" - "!" run the $ALERT command with the message and save a copy to the targets named in $ALERT_TARGETS They're set like this: ALERT=alert ALERT_TARGETS="F,spool-to-phone" So $ALERT runs my "alert" command, a script. Details below. $ALERT_TARGETS says: - "F" (F)lag the message (same as mutt's (F)lag command) so that it is highlighted in mutt's index - "spool-to-phone" save a copy in my +spool-to-phone folder, which mailfiler also monitors (its rules say forward a copy to my phone's email account) The desktop popup comes from my "alert"r script: https://hg.sr.ht/~cameron-simpson/css/browse/bin/alert?rev=tip That will issue alerts to a variety of places depending on envvars and options particularly my dlog (a timestamped text log I use for reviewing things, since my invoicing system is a ghastly hack held together with string) and to the desktop. The "desktop alert" part of that script is in the $to_desktop if-statement at the bottom. Presently I'm on a Mac and use the "terminal-notifier" command to issue a normal Mac Notification popup. I'd be using whatever Linux desktop notification command line were suitable were I on Linux. I presume there _is_ a standard way to issue a popup alert on Linux systems these days? I used to just always run a permanent very short full-width terminal across the top of the screen tailing a log file myself, crude but effective. The same terminal also accepted commands if you typed them. Anyway, that is how this is hooked into my email. Suggestions for current Linux or other UNIX desktop popup command line tools welcomed. Cheers, Cameron Simpson
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 13Feb2021 20:03, Sam Kuper wrote: >On Fri, Feb 12, 2021 at 01:30:04PM +0100, Angel M Alganza wrote: >> On Mon, Feb 01, 2021 at 04:34:47PM -, Grant Edwards wrote: >>> I maintained a local queueing MTA for many years, but after multiple >>> screwups where mail wasn't getting sent (and I didn't find out in a >>> timely manner) I switched to a non-queueing MTA (e.g. ssmtp) and >>> later to mutt's SMTP support. >> >> I did the same myself for years and also switched to ssmtp. But I >> belive ssmtp was discontinued, and now I'm using msmtp: >> >> https://marlam.de/msmtp/ >> >> I couldn't be happier! > >A queue script is included with msmtp, so you can have the best of both >worlds :) > >https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD Ah, I missed that. Nice. Though I still like a local system MTA so that scripts and cron etc etc can also send email natively. Cheers, Cameron Simpson
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 12Feb2021 23:25, boB Stepp wrote: >On 21/02/13 08:01AM, Cameron Simpson wrote: >>I pull everything from my c...@cskk.id.au inbox, deleting it. But my >>mail >>filing forwards a suite of messages to a separate account which is for >>my phone. So anything important sends a copy back out to the cloud. >>Well, a personal external server. Um, in the cloud :-( >> >>Likewise, any email I reply to sends the source message and the reply to >>that account. >> >>In this way my phone has access to a copy of the critical stuff and also >>any ongoing email discussions. > >So it seems you only concern yourself in keeping relatively current emails >accessible to your phone? Well I pretty much never purge it, so old stuff too. >You haven't had occasion to need something from a >while back to fetch on your phone that suddenly becomes needed? Well, the phone account is meant to have "relevant" stuff rather than the dross comprising most email. So my filer forwards: - everything it flags on arrival - everything I send/reply - the source message of anything I reply to Cheers, Cameron Simpson
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 12Feb2021 23:20, boB Stepp wrote: >>Then tag messages in you inbox and ";s+folder" to move them in >>batches. >>Here I mean mutt's (t)ag keystroke, an in memory flag. Emphemeral, used >>entirely to do mutt things to an ad hoc batch of messages. > >Yeah, I just was playing around with this some earlier in the week. I'm now >doing this to tag and move emails into my Archive folder, which I have bound >"S" for this purpose. Which leads me to a question I have been meaning to >ask. This is what I am using right now: > >macro index,pager S "=Archive" "Send to >Archive" > >If I don't add then the email(s) sit there marked deleted >(Funny that the same 'D' label is used here as for a real deletion.) until I >manually >sync or it happens automatically. I just want the mail to be _immediately_ >moved to my >local Archive folder. Is there a better, more direct way to do this without >doing a sync operation? The message will be copied to Archive immediately (you can check that by opening it in another window). It is just the current folder where they're not yet removed until you sync; that lets you under the "delete" part of the "move" if you want. If you wanted the sync immediate, include "" in the macro? It is a whole mail folder sync of course. Personally, my (d)elete macro just archives :-) Cheers, Cameron Simpson
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 12Feb2021 23:20, boB Stepp wrote: >Yeah, I think you have. I have kept those earlier emails from you >nicely >flagged in my inbox for reference. Currently I am trying to see if I can get >something I like working with notmuch. I wish I could use notmuch's tagging >capabilities from within Mutt in the sense of adding multiple tags to a single >email or a set of tagged emails. But the only example of an approach is to >try to adapt the macro I cited earlier in this thread which deletes the inbox >tag. I see how to modify this to do *one* tag, but that would be hard-coded >and not very flexible or useful. I'm sure there must be a way to write a >macro to allow for me to enter multiple tags for notmuch, but I don't know >enough about Mutt macros to see a way forwards yet. "notmuch tag" itself accepts multiple tags. Write a small shell script to prompt for the tags to change (in the same form as notmuch expects i.e. +tag and -tag) which then invokes notmuch. If you mean this macro: macro index \ "set my_old_pipe_decode=\$pipe_decode my_old_wait_key=\$wait_key nopipe_decode nowait_key\ notmuch-mutt tag -- -inbox\ set pipe_decode=\$my_old_pipe_decode wait_key=\$my_old_wait_key" \ "notmuch: remove message from inbox" it: - saves the pipe_decode and wait_key settings, and turns them off - pipes the current message through notmuch-mutt to remove the "inbox" tag - restores the old pipe_decode and wait_key settings The $my_blah= is a standard mutt hack because there's no "push temporary setting or value", and there are no settings called my_*. So people use $my_blah for "user variables". Piping the whole message through notmuch lets notmuch-mutt get the message-id in order to know which item to tag or untag. The it passes "id:$mid" to notmuch, where $mid is the message id. That's the mechanism. To tag things interactively you have 2 issues: - specifying the messages to tag - specifying the tag changes For the latter I'd have a shell script which prompted for that, then ran notmuch. For the former, from inside mutt, I'd think there are 2 ways forward. With a single message you can just pipe it straight into the script, like the above macro does. With multiple messages I think I would tag them, and pipe all of them _separately_ through the script. Now, there are some ways to make that more convenient, particularly these settings: set auto_tag=yes set pipe_split=yes auto_tag=yes causes mutt to apply commands to all tagged messages (if any) or just the current message (if nothing tagged). pipe_split=yes causes mutt to run separate pipes per message when it pipes multiple messages, instead of concatenating them and running one pipe. You want that for notmuch-mutt. The notmuch-mutt script in the example above expects exactly one message on its input, _entirely_ to grab its message-id. So we want pipe_split-yes to invoke the script once for each message. Regarding prompting, I'd write a script like this (untested): #!/bin/sh set -ue echo -n "Enter tags to change (-tag, +tag): " >/dev/tty read tags
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On 12Feb2021 22:53, boB Stepp wrote: >On 21/02/13 08:11AM, Cameron Simpson wrote: >>I would guess your PC does not have a mail system installed. So cron >>cannot deliver the cron job output by email. > >I was aware that a cron job could email its output, but I thought I would have >to explicitly set that up. Is this not the case? In any event I do not know >enough at this time to do this, so I haven't done so. But if your hypothesis >is correct and it is trying to email me, but finding no MTA to enable it to do >so, why don't I *always* get this message? Cron only sends email when the job's output is not empty. Silent jobs do not try to send email. Is that plausible? >>One of the benefits of have a local email system is getting stuff from >>cron et al. Also, you can use it for spooling - if mutt sends via the >>local email system you can send when offline - it will just queue. >> >>>One concern based on earlier discussion in this thread. I am now using >>>msmtp as my MTA client. What will happen if I send an email when, for >>>whatever reason, Gmail connectivity is broken? Will it get resent? >> >>I don't know. What does its manual say? [...] >reading the past few days! My head is spinning chock full of half-understood >information about multiple email software and topics!! [...] >As far as I have been able to tell from the man pages msmtp will attempt to >send me a notification email in the event of delivery failure. AFAICT, there >is no explicit mention of msmtp trying to resend the email. Also it is not >clear to me if delivery failure includes not being able to connect to the >Internet. It did say it uses standard exit codes, but I did not see how it >would act in this instance. Looks to me like it does not queue: % (echo To: c...@cskk.id.au; echo From: cs; echo Subject: msmtp test;echo;echo 1) | msmtp --host=bogushost.example.com --from=c...@cskk.id.au -t c...@cskk.id.au msmtp: cannot locate host bogushost.example.com: nodename nor servname provided, or not known msmtp: could not send mail Caveat: I have no msmtp config - that's a bare command line test. There's a package called "nullmailer" which can be used as your system MTA - it is intended for systems with a smarthost - upstream SMTP server, exactly what you msmtp setup will be using. But it has a queue. You could install it without changing your mutt/msmtp setup at all. If it works for you, you could then switch to having mutt use the local sendmail command (the default) instead of msmtp. Looks like its config lives in /usr/local/etc/nullmailer. Source: https://github.com/bruceg/nullmailer Install: https://github.com/bruceg/nullmailer/blob/master/INSTALL Man page for nullmailer-send, which describes the config settings: https://github.com/bruceg/nullmailer/blob/master/doc/nullmailer-send.8 Disclaimer: I've not used it. Cheers, Cameron Simpson
Re: Dead url, returning 404 in wiki under configlist/Configs
On Fri, Feb 12, 2021 at 09:45:41AM -0800, Kevin J. McCarthy wrote: > On Fri, Feb 12, 2021 at 02:25:44PM +0530, Bhaskar Chowdhury wrote: >> Please take out the dead url from the Configlist page under Configs > > Thanks, I've removed the dead link. > > Note, to anyone else: although the wiki is not directly publicly > editable, you can clone the https://gitlab.com/muttmua/wiki repos and > submit a merge request too. Thanks. That link's target is still visible in the Wayback Machine, though. Merge request submitted: https://gitlab.com/muttmua/wiki/-/merge_requests/8 -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: UserPages dead url ..the first one the page
On Sat, Feb 13, 2021 at 06:59:04AM +0530, Bhaskar Chowdhury wrote: > On this page : https://gitlab.com/muttmua/mutt/-/wikis/UserPages > > The url: http://mutt.justpickone.org/ -- David T-G > > While clicking on the url Showing: > > "Error resolving “mutt.justpickone.org”: Name or service not known" > > I think it is not maintained anymore. Thanks. Fortunately, the link target is available in the Wayback Machine. Merge request submitted: https://gitlab.com/muttmua/wiki/-/merge_requests/8 -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: My experiences with Mutt to date: Suggestions for overcoming some issues
On Fri, Feb 12, 2021 at 01:30:04PM +0100, Angel M Alganza wrote: > On Mon, Feb 01, 2021 at 04:34:47PM -, Grant Edwards wrote: >> I maintained a local queueing MTA for many years, but after multiple >> screwups where mail wasn't getting sent (and I didn't find out in a >> timely manner) I switched to a non-queueing MTA (e.g. ssmtp) and >> later to mutt's SMTP support. > > I did the same myself for years and also switched to ssmtp. But I > belive ssmtp was discontinued, and now I'm using msmtp: > > https://marlam.de/msmtp/ > > I couldn't be happier! A queue script is included with msmtp, so you can have the best of both worlds :) https://git.marlam.de/gitweb/?p=msmtp.git;a=blob_plain;f=scripts/msmtpq/README.msmtpq;hb=HEAD Sam -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
Re: [unixbhas...@gmail.com: Notify-send pop up for specific mails]
On 07:40 Sat 13 Feb 2021, Cameron Simpson wrote: On 12Feb2021 09:36, Kevin J. McCarthy wrote: On Fri, Feb 12, 2021 at 09:59:38AM +0530, Bhaskar Chowdhury wrote: The problem it pops up for every new mail arrive. [...] For more sophisticated notification, you'll need to use another tool. For xample, my own new mail desktop notifications happen from my mail filer, not from mutt. This has the advantage that they still happen when mutt is closed (if you can call that an advantage). How?? Show us...share with the people .. Cheers, Cameron Simpson signature.asc Description: PGP signature
