similar to: Logging in to a virtual users Maildir

Package: dovecot Version: 0.99.10.4-2 I am accessing my IMAP folder on my ~/Maildir using mutt via Dovecot and I have this problem whereby mutt incorrectly reports I have new mail in a "mailboxes" polled mailbox. This happens all the time when I press the key bound to change mailbox. I use courier IMAP at school, and I have not experienced this problem. A bug with dovecot or mutt?

On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote: > >> And yet it is. > > in muttrc you miss ~ or $(HOME)/something No. >> Root has been aliased for decades. This has no impact on where and how >> mutt stores the mail it sends as root out of root?s crontab. > > root user can read mail files for all unix users, thats your fail, maybe

I am having some trouble with dovecot 1.2.12 and some namespace issues, or at least that's what I think is the issue. I setup a virtual mailhosting using mysql and postfix. I can receive email and send email without a problem, but when I use mutt to sign in to dovecot, I can't list any Folders, it see's INBOX but it doesn't see any mail. I generally try to not post my problems

What happens if you put the following in /root/.muttrc: Set record='/file/to/put/mail/in' ? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 ?On 5/5/18, 12:15 PM, "dovecot on behalf of @lbutlr" <dovecot-bounces at dovecot.org on behalf of

I have a user w/o a shell that runs an app as a daemon that needs to use mutt to email an attachment from a script. During testing when the app was ran as root everything worked:) Now that we obviously are running as a user w/o a shell this little bit broke. I used mutt as I needed to send the attachment as mime, and the ability to specify a muttrc from the cli when executed was useful so we

Debug log output please! I think you still miss the gssapi module for dovecot. Am 03.07.2016 um 19:42 schrieb Mark Foley: > Achim, > > This is my most recent effort. If I cannot make progress from here I'm going to give this idea a rest. > > I used easy-rsa to create a cert. Files are: > > /etc/ssl/certs/OHPRS/easyrsa/ca.crt > /etc/ssl/certs/OHPRS/easyrsa/reqs/MAIL.req

On 21 March, 2018 - Aki Tuomi wrote: > Thank you for your thorough report, we'll look into it. Has anyone managed to reproduce this (using my transcript for example)? With mutt, I get this problem.. If I set 'imap_pipeline_depth=0' in .muttrc, I can't seem to reproduce it anymore. /Tomas -- Tomas Forsman, stric at cs.umu.se, http://people.cs.umu.se/stric/ `- SysAdmin at

On Fri, Oct 18, 2019 at 10:36:25AM -0500, Valeri Galtsev wrote: > > > > On Fri, Oct 18, 2019 at 09:23:38AM -0500, Valeri Galtsev wrote: > > > And last but not least: I got used to some way of interaction with computer, > > > and that way is most productive for me after very long use. I don't want to > > > blend in iPad generation, I want to stay

Hi! My plea to readers: =================== Pls., people who only want strictly technical issues to read, and frown at any broader context regardless how intrinsically related, but not strictly technically related, it might be, skip all the way, all the way to, search for exact words: "strictly technical" or visually, find two lines of sole "===" characters. Thank you!

> And yet it is. in muttrc you miss ~ or $(HOME)/something >> root: some-other-unix-login > Root has been aliased for decades. This has no impact on where and how > mutt stores the mail it sends as root out of root?s crontab. root user can read mail files for all unix users, thats your fail, maybe crontab miss $(HOME) where it matters, but if it have and you start mutt as root

Heylas, I just switched my primary mail server from courier imap to dovecot (I've been waiting to do this; dovecot showed up in debian testing for alpha, at last). So, using the same set of maildirs, there are slightly different behaviors. First, of course, dovecot displays the hierarchy as I thought it ought to be, such that INBOX is a sibling of all other top-level boxes, not the parent

Achim, This is my most recent effort. If I cannot make progress from here I'm going to give this idea a rest. I used easy-rsa to create a cert. Files are: /etc/ssl/certs/OHPRS/easyrsa/ca.crt /etc/ssl/certs/OHPRS/easyrsa/reqs/MAIL.req /etc/ssl/certs/OHPRS/easyrsa/reqs/dovecot.req /etc/ssl/certs/OHPRS/easyrsa/private/ca.key /etc/ssl/certs/OHPRS/easyrsa/private/MAIL.key

Larry Rosenman wrote: > I have my dovecot running with TLS, so the passwords are NOT transmitted in > the clear (starttls). The problem is not transmitting them in the clear but keeping them in the clear in a local file like muttrc, or entering the password each time you launch mutt. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49 at fidonet http://vas.tomsk.ru/

Hi Mark, I'll keep replying to the list. You must create an signed server certificate for your FQDN. ~# ./build-key-server mail.hprs.local Then point to public and privat part in your dovecot config. ssl_cert = </etc/easy-rsa/keys/reqs/mail.hprs.local.req ssl_key = </etc/easy-rsa/keys/private/mail.hprs.local.key But all that should not interfere with kerberos because you can accept

hi i have a strange problem with my dovecot installtion: i configured it to accept digest-md5 authentication only but for some reason mailclients (i tried mutt and thunderbird so far) want to log with PLAIN (which fails of course). authentication basically works, e.g. if i explicitly set set imap_authenticators="digest-md5 in .muttrc everything works... any idea what is going wrong? config

What I do is keep my passwords in a file encrypted by GPG and have mutt do: source "gpg -q --textmode -d ~/.neomutt/passwords.gpg |" that way they're not readable except by use of a passworded GPG key. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX

> On 05 May 2018 at 20:14 "@lbutlr" <kremels at kreme.com> wrote: > > > On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote: > > > >> And yet it is. > > > > in muttrc you miss ~ or $(HOME)/something > > No. > > >> Root has been aliased for decades. This has no impact on where and how > >> mutt

> On Oct 18, 2019, at 11:34 AM, Scott Robbins <scottro11 at gmail.com> wrote: > > On Fri, Oct 18, 2019 at 10:36:25AM -0500, Valeri Galtsev wrote: >> >> >>> On Fri, Oct 18, 2019 at 09:23:38AM -0500, Valeri Galtsev wrote: >>>> And last but not least: I got used to some way of interaction with computer, >>>> and that way is most

Hi, I have a little problem with characters/lines getting mixed up and I don't know where to look or how to google for a clue. I've a CentOS 4 system on which I use gnome-terminals. When I use mutt (mutt-1.4.1-10) in such a terminal, in some situations it mixes-up the lines in the terminal. It seems in some way it fails to 'refresh' all lines. For example, if I have a line bind

OK, let me go through exactly what you did: you: > Here's the test (I must run mutt not telnet like i mentioned earlier to > get the imap tickets). > > root at server:~# kinit achim > Password for achim at DOMAIN.LOCAL: > [I enter my password] As root on AD/DC mail.hprs.local: me: $ kinit mark Password for mark at HPRS.LOCAL: [I enter my password] you: >