On Tue, Jul 25, 2017 at 02:55:51PM +0200, Steffen Nurpmeso wrote: > Hello Paul. > > Paul Vojta <[email protected]> wrote: > |On Mon, Jul 24, 2017 at 02:30:44PM +0200, Steffen Nurpmeso wrote: > |> Paul Vojta <[email protected]> wrote: > |> > |> First of all i am sorry that you were in the queue, your address > |> was (and is still) listed in "List of non-member addresses whose > |> postings should be automatically accepted" as well as "List of > |> addresses (or regexps) whose subscriptions do not require > |> approval", so this i do not understand. (Except that the > |> "moderated" bit for new members is by default on. Well.) > | > |Probably it's because v*@math.b*.edu is an alias for v*@b*.edu, and emails > |go out with both addresses in various parts of the mail header. I've had > |this problem with other mailing lists too, but I forgot about it when > |subscribing to this one. You may have noticed I unsubscribed and subscribed > |again just now using the "real" address. That should fix it. > > So you were in the queue once again. ^.^ > I hope it is fine from now on.
Yes, I'm getting mail from the list now, and my earlier post made it through OK. > |>|I have the following problem with the current s-nail > |>|(commit 670aabb6804d94e0fe386c99e2b9ab382a2bb86c): > |>| > |>|% ~/s-nail-git/s-nail -f %:+texlive > |>|[email protected]@imap.gmail.com requires a password: > |> ... > |>|s-nail: Could not connect: Network is unreachable > .. > |> Would you be so kind and verify that the issue goes away if you > |> apply the diff or update to any of > |> [master,stable/{stable,latest,v14.9}]? > | > |Sorry, the problem remains (on origin/master). > > Ok, i thought you were really talking about the crash that was > caused by this very mysterious (could not have been a) copy+paste > error, but trying once again without an "automatic" password i see > that, whereas folder changes etc. do not require re-entering the > password, performing actions like copying do. I suspect it is > because we get a mismatch when testing for "same mailbox". ... > > Oh yes. That is an IMAP fallout of the new possibility to specify > and fixate a mailbox type by using a proto:// prefix. I see now, > we replaced any (the imaps://) prefix with imap://, so that the > mentioned mismatch occurred. I have tested the reinstantiation > locally with dovecot and only without SSL. I am sorry for that. > > This should now really be fixed, i have used your .rc template and > copied around a bit on my Google test account. On [master] etc. > Thanks for reporting and insisting, Paul. Yes, it works now. Thanks! Paul ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot __________________________________ [email protected]
