Re: Mailing list status

[nunojsilva]

On 2018-03-12, Kevin J. McCarthy wrote:

> On Mon, Mar 12, 2018 at 10:01:08PM +, Nuno Silva wrote:
>> It looks like the "nomail" subscription setting was lost in this
>> transition.
>> 
>> I have been subscribed that way for some time and today, for the first
>> time ever, I received a few emails from this mailing list.
>
> Sorry about that.  Yes, the 'nomail' and 'digest' options were lost, and
> I have no way to retrieve them.  I'll have to ask for your forgiveness
> and request you manually re-enable those settings for your account.
>
> Subscription settings can be edited at:
> https://lists.osuosl.org/mailman/listinfo/mutt-users
>
> Note, however, that the website and mailman are not integrated yet.
> Some of the mailman links in emails point to
>  prefixes which currently don't work.
> Please use the above osuosl.org URL for now.

To do this by e-mail:

1. The mailing list software now requires the password to be provided
   with some requests and it appears that passwords were reset with this
   migration. So, first send an email containing just "password" to
   mutt-users-requ...@mutt.org

2. After receiving the password, send a second e-mail to the same
   address with

   set authenticate your-password
   set delivery off

-- 
Nuno Silva

Re: Piping to a script and receiving commands/variables back

[Cameron Simpson]

On 12Mar2018 23:32, David Woodfall  wrote:

I've made a shell script that I pipe via a key bind. It parses for
email address and writes a new procmail rule based on that and the
name of a folder that I enter on the CLI.

It works OK, but I'd like to send the name of the folder back to mutt
and have it save the message there afterwards.

I've kind of got it working by echoing commands to a tmp file and then
have mutt source it:

echo "push =$folder" \
> /tmp/newfolder

I'd much rather know if there's a better way of doing it.


The other alternative is to source its output directly. So the raw command is:

 `your-shell-script`

But you want the script to parse a mail message and emit mutt commands for 
sourcing. Possibly you need to (a) save the message to a file (b) run:


 `your-shell-script  (formerly c...@zip.com.au)

Piping to a script and receiving commands/variables back

[David Woodfall]

Hello,

I've made a shell script that I pipe via a key bind. It parses for
email address and writes a new procmail rule based on that and the
name of a folder that I enter on the CLI.

It works OK, but I'd like to send the name of the folder back to mutt
and have it save the message there afterwards.

I've kind of got it working by echoing commands to a tmp file and then
have mutt source it:

echo "push =$folder" \
 > /tmp/newfolder

I'd much rather know if there's a better way of doing it.

Thanks

Re: Mailing list status

[Kevin J. McCarthy]

On Mon, Mar 12, 2018 at 10:01:08PM +, Nuno Silva wrote:
> It looks like the "nomail" subscription setting was lost in this
> transition.
> 
> I have been subscribed that way for some time and today, for the first
> time ever, I received a few emails from this mailing list.

Sorry about that.  Yes, the 'nomail' and 'digest' options were lost, and
I have no way to retrieve them.  I'll have to ask for your forgiveness
and request you manually re-enable those settings for your account.

Subscription settings can be edited at:
https://lists.osuosl.org/mailman/listinfo/mutt-users

Note, however, that the website and mailman are not integrated yet.
Some of the mailman links in emails point to
 prefixes which currently don't work.
Please use the above osuosl.org URL for now.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

Re: Mailing list status

[nunojsilva]

On 2018-03-12, Kevin J. McCarthy wrote:

> Last Friday night, our mailing list and website server suffered a
> catastrophic failure.
>
> Fortunately, for the past couple months I have already been working on
> moving our mailing lists to OSUOSL.  I had planned a couple more steps
> to transition smoothly, but given the failure have accelerated things.
>
> The new mailing list server uses GNU mailman.  There are likely a few
> things that need to be tweeked.  Please let me know about any issues.
[...]

Hello,

It looks like the "nomail" subscription setting was lost in this
transition.

I have been subscribed that way for some time and today, for the first
time ever, I received a few emails from this mailing list.

-- 
Nuno Silva

Re: Mailing list status

[Cameron Simpson]

On 12Mar2018 12:31, Kevin J. McCarthy  wrote:

Last Friday night, our mailing list and website server suffered a
catastrophic failure.

Fortunately, for the past couple months I have already been working on
moving our mailing lists to OSUOSL.  I had planned a couple more steps
to transition smoothly, but given the failure have accelerated things.


Many thanks!


The new mailing list server uses GNU mailman.  There are likely a few
things that need to be tweeked.  Please let me know about any issues.


I notice that the Sender: header now says {listname}-boun...@mutt.org whereas 
before it said owner-{listname}@mutt.org. (Because my mail filing rule no 
longer matched.)


In my mind the original value is better, with a Return-Path: header for 
{listname}-boun...@mutt.org. (Assuming of course that owner-{listname} is still 
a valid address.)


But this is very minor.

Cheers,
Cameron Simpson  (formerly c...@zip.com.au)

Re: mutt manual: i have bad startings into learning mutt

[kalle]

hello,
thanks to you all for the lots of help, which came. I always work on
different free software topics in parallel, so it is usual that my
responses can take a lot of time. But they eventually come...

Am 07.02.2018 um 22:37 schrieb kalle:
> hello,
>
> In the manual v.1.9.2, chapter "2.1 Index" it says
>
> "The index is the screen that you usually see first when you start
> Mutt. It gives an overview over your emails in the currently opened
> mailbox."
>
> The problem is: there are no mails to see, because there is no mailbox
> of mine open and I don't know how to do this.
>
>
> It is the third time already that I try to learn mutt but having no
> mails to start with, not knowing what is meant by a 'mailbox' and how
> to administrate it, even when reading in the newbie manual not getting
> to a point.
>
> I usually use thunderbird and thus already have some experience with
> e-mail, but what I got from trying to learn mutt is just depressing
> for me.
>
>
> greetings,
>
> kalle
>

Am 08.02.2018 um 19:27 schrieb Wim:
> the manual is an excellent resource but difficult for new users. The
> Arch wiki might be a better place to start.
>
> https://wiki/archlinux.org/index.php/Mutt
>
> Or
> https://wiki.ubuntuusers.de/Mutt/

your 2 hints helped me (the second one is in german). But I think, that
they don't make me really understand things, they only help me fix the
configuration problem somehow.
But it disturbs me, that every distribution community make their own
documentation. It would be much more efficient, if there would be one
reference manual and then at most some different tutorials or alike,
which are specialized in their didactical way. Doing the same work
several times is a waste of resources for the user community.

Therefore I will look thoroughly, what went wrong when I tried or what
could be done better.

@yubin, erik: this is my muttrc NOW. and now it works.

set imap_user=ka...@projektwerkstatt.de
set spoolfile=imaps://mail.netzguerilla.net:993/
set folder=imaps://mail.netzguerilla.net:993/
set editor=ed

I didn't have a .muttrc-file before. That's why it didn't work. It was
only that when I started mutt, the program told me that I didn't have
any mailbox and if didn't want any, if I remember right. But I didn't
know what to answer.

As you see, I have a spoolfile now.My mutt-version is 1.5.21.



Am 08.02.2018 um 03:19 schrieb Erik Christiansen:
> As you are using linux on your host, try:
>
> $ ls /var/spool/mail/
>
> to see what is there. (And go from there.)

The directory was empty. How should it, since I didn't have any
MailRetrievalAgent to put it there and didn't configure mutt to use it's
imap-feature. And now, while I started using fetchmail I also got some
mails in /var/mail.

@Cameron:

Am 08.02.2018 um 05:39 schrieb Cameron Simpson:
>
> Ok, it sounds like mutt is presenting the local default UNIX mailbox on
> your system.
>
> If you are using Thunderbird then it is likely that either your mailbox
> is an IMAP service hosted at your ISP or at some place like Google Mail.
>
> Is this the case?
>
> Without some configuration, mutt looks in your local machine's mail
> system. It is likely that nothing is using that if it is a personal
> machine such as a laptop, so you have no local mail.

You were exactly right.


my conclusion at this state of reflection, at which I am:
i suppose that if in the manual.txt it would've been clearly
referenced/explained the different functions of Mail exchange and that
Mutt is generally only the MUA-part while it can also have some
MRA-features, which are in chapter 6 - Optional Features (e.g. 6.4 IMAP
Support)  I would've found the IMAP-configuration there.
But as I started from the beginning of the document, where the it is not
talked about the necessary configuration, I could not follow, and
continued the chapters, passing the "Configuration"-chapter until
reaching the "Advanced Features"-chapter and there at latest abandoning,
without having found a good hint about it.

kalle

Re: Gmail undelete configuration

[Keith Smiley]

Sorry I meant what's the difference from the mutt / offlineimap perspective on 
these?

-- 
Keith Smiley

On Sun, Mar 11, 2018, at 13:01, Yubin Ruan wrote:
> On Sun, Mar 11, 2018 at 12:10:46PM -0700, Keith Smiley wrote:
> > > That is the same for archiving.
> > 
> > What is the differentiation for archiving vs deleting?
> 
> For archiving, messages get moved into [Gmail]/Archive, whereas for deleting
> messages get moved into [Gmail]/Trash, which get cleared every 30 days by
> Gmail by default.
> 
> Yubin

Re: Mailing list status

[Francesco Ariis]

Hello Kevin,
thanks for the hard work.

On Mon, Mar 12, 2018 at 12:31:34PM -0700, Kevin J. McCarthy wrote:
> The new mailing list server uses GNU mailman.  There are likely a few
> things that need to be tweeked.  Please let me know about any issues.

1. The listinfo URL

> http://mutt.org/mailman/listinfo/mutt-users

returns a 404.

2. (minor) I would change:

> Mutt-users mailing list
> Mutt-users@mutt.org

to this:

> mutt-users mailing list - mutt-users@mutt.org

(i.e. one line, email address not capitalised)
-F

Mailing list status

[Kevin J. McCarthy]

Hi Everyone,

Last Friday night, our mailing list and website server suffered a
catastrophic failure.

Fortunately, for the past couple months I have already been working on
moving our mailing lists to OSUOSL.  I had planned a couple more steps
to transition smoothly, but given the failure have accelerated things.

The new mailing list server uses GNU mailman.  There are likely a few
things that need to be tweeked.  Please let me know about any issues.

It is likely that emails sent to the list since Friday night will not
make it through, and will need to be resent.  Sorry for the
inconvenience.

Please let me offer a huge thank you to GBNet for donating their time
and servers to Mutt for many, many years, and also express my
appreciation to OSUOSL for working with me to transition to their
hosting services.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature
-- 
Mutt-users mailing list
Mutt-users@mutt.org
http://mutt.org/mailman/listinfo/mutt-users