Displaying 20 results from an estimated 9309 matches for "inboxe".
Did you mean:
inbox
2016 Jan 06
3
Mapping of INBOX.INBOX breaks imapc_list_prefix=INBOX?
We're running a huge imapc-Migration from an old Courier-IMAP to Dovecot.
Courier always uses "INBOX."-prefix for his folders, so we set
namespace inbox {
[...]
separator = .
prefix = INBOX.
[...]
}
on our new Dovecot 2.2.20 system.
And also we added:
imapc_list_prefix=INBOX
to avoid the dublication of the INBOX prefix.
At the end, doveadm/dsync/imapc see
2006 Jul 18
2
Masking INBOX.INBOX
I am using dovecot and trying to make it compatible with my a BincIMAP
installation. BincIMAP uses a scheme similar to Courier-IMAP, so I set
up this default_mail_env:
default_mail_env = maildir:~/Maildir
And this namespace:
namespace private {
separator = .
prefix = INBOX.
inbox = yes
}
Which mostly works as expected, but I now see an "INBOX" subfolder of
"INBOX" in
2010 Jun 21
1
doveadm search: Error: Syncing mailbox foo failed: Mailbox doesn't exist: foo
Hi Timo,
doveadm reports errors for \Noselect mailboxes.
What I have:
1 LIST "" *
* LIST (\HasNoChildren) "/" "Templates"
* LIST (\HasChildren) "/" "INBOX"
* LIST (\Noselect \HasChildren) "/" "INBOX/Lists"
* LIST (\Noselect \HasChildren) "/" "INBOX/Lists/vmm"
* LIST (\HasNoChildren) "/"
2019 Jul 16
2
Unexpected result from LIST EXTENDED command
I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server
Notice that some status responses are missing (For folders INBOX.Archive, INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as expected
In rfc5819 there is this:
If the server runs into unexpected problems while trying to look up
the STATUS information, it MAY drop the corresponding STATUS reply.
In
2018 Aug 14
5
doveadm mailbox delete not working
I have a user who has several folders in his mailbox, which we can not
delete, neither via IMAP nor via doveadm:
root at ka-nfs-mail:~# doveadm mailbox list -u <username> | grep hbereiche
| cat -v
INBOX/[Fachbereiche ^M
INBOX/Fachbereiche ^M
INBOX/hbereiche^M
INBOX/hbereiche/LAGen]^M
INBOX/hbereiche/LAG^M
INBOX/[Fachbereiche^M
INBOX/[Fachbereiche/LAGen]^M
INBOX/[Fachbereiche]^M
2019 Oct 18
3
Dovecot v2.3.8 released
On 2019-10-18 13:25, Tom Sommer via dovecot wrote:
> I am seeing a lot of errors since the upgrade, on multiple client
> accounts:
>
> Info: Connection closed: read(size=7902) failed: Connection reset by
> peer (UID FETCH running for 0.242 + waiting input/output for 108.816
> secs, 60 B in + 24780576+8192 B out, state=wait-output)
>
> Using NFS storage (not running with
2019 Oct 08
4
Dovecot v2.3.8 released
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Changes
+ Added mail_delivery_started and mail_delivery_finished events, see
https://doc.dovecot.org/admin_manual/list_of_events/ for details.
+ dsync-replication: Don't replicate users who have "noreplicate" extra
field in
2019 Oct 08
4
Dovecot v2.3.8 released
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.8.tar.gz.sig
Binary packages in https://repo.dovecot.org/
Changes
+ Added mail_delivery_started and mail_delivery_finished events, see
https://doc.dovecot.org/admin_manual/list_of_events/ for details.
+ dsync-replication: Don't replicate users who have "noreplicate" extra
field in
2012 Aug 09
1
dsync \noselect on INBOX.INBOX skips sync of INBOX
Hi Timo,
We have encountered an issue today with a number of migrations. Some customers have mailboxes on the source IMAP server that look like this:
3 LIST "" *
* LIST () "." "INBOX"
* LIST () "." "INBOX.Statements"
* LIST () "." "INBOX.Draft"
* LIST () "." "INBOX.Drafts"
* LIST () "."
2018 Aug 15
1
doveadm mailbox delete not working
One more update, I tried renaming that "[Test " folder to just "Test",
which creates an also not deletable folder "Test".
Good news is, if I delete these folders on both replication nodes from
mdbox/mailboxes and mdbox/subscriptions they seem to be really gone.
I can event create the folder "Test" again and it behaves normal aka. I
can delete it afterwards
2014 Mar 22
3
Case-sensitive INBOX or client issue?
I am using dovecot as an IMAP server for a Cisco product (Cisco Agent
Desktop by Calabrio) and noticed some odd behavior when trying to access
emails. The mail is delivered to the main INBOX, then a Cisco server moves
it to a directory within the INBOX based on the queue it is meant for.
Here is the directory structure of the Maildir:
Maildir/INBOX
Maildir/INBOX/tmp
Maildir/INBOX/63
2019 Mar 20
2
[BUG?] Double quota calulation when special folder is present
Just hoping to get some dev eyes on this. I'm incredibly reluctant to throw
the word 'bug' around
(since 99 times out of 100, it's not -- it's almost always the config), but
I can't think of any way
that this could be a config issue, esp when the pre-2.2.34 version works as
expected.
I noticed during troubleshooting that dovecot errors out if I try to create
a subfolder
2018 Oct 09
3
immediate delete of mails
On Tue, 9 Oct 2018 11:09:53 +0300
Reio Remma <reio at mrstuudio.ee> wrote:
> Do you see anything in Dovecot logs? It should definitely log if there
> were permission issues.
With 'mail_debug=yes' I see nothing relevant. Just something like this when I want to expunge deleted mails:
Oct 09 10:40:01 imap(tselmeci)<15816><ZwHSosd3NL/AqAFm>: Debug: Mailbox INBOX:
2019 Apr 21
3
FTS delays
On 3 Apr 2019, at 20.30, Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
> doveadm search -u jom at grosjo.net mailbox inbox text milan
> output
>
> doveadm(jom at grosjo.net): Info: Query : ( bcc:inbox OR body:inbox OR cc:inbox OR from:inbox OR message-id:inbox OR subject:inbox OR to:inbox OR uid:inbox ) AND ( bcc:milan OR body:milan OR cc:milan OR from:milan OR
2020 Jul 17
2
Namespace issues & duplicate maiboxes
Hello,
I am seeing duplicate mailboxes when I perform the ?doveadm mailbox list? command?the output is as follows:
=================
INBOX
INBOX.Drafts
INBOX.Trash
INBOX.Sent
INBOX.INBOX
INBOX.INBOX.Sent Messages
INBOX.INBOX.Drafts
INBOX.INBOX.Trash
INBOX.INBOX.Deleted Messages
=================
Here is namespace config that seems to have caused the above duplicates. Please help me
2012 Mar 05
2
\NoSelect on missing folders in LIST
Hi,
I noticed a difference between courier and dovecot, and I'm not sure
which of them is wrong wrt. RFC3501 - if any.
I have a Maildir which has been accessed by an Apple Mail client, so it
got folders like:
INBOX
INBOX.Trash
INBOX.INBOX.folder
INBOX.INBOX.folder.a
INBOX.INBOX.folder.b
The INBOX.INBOX folder does not exist on disk and is not subscribed.
Courier responds to:
. list
2013 Nov 05
1
Problem migration from cyrus with imapc
Hi all,
i have problem with namespace when i try to migrate from cyrus to
dovecot with imapc.
If i login to the old cyrus i get:
telnet 192.168.8.164 143
Trying 192.168.8.164...
Connected to 192.168.8.164.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5]
Dovecot ready.
a
2011 Dec 23
2
2.1.rc1 (056934abd2ef): virtual plugin mailbox search pattern
Hello Timo,
With dovecot 2.1.rc1 (056934abd2ef) there seems to be something wrong
with virtual plugin mailbox search patterns.
I'm using a virtual mailbox 'unread' with the following dovecot-virtual file
$ cat dovecot-virtual
*
unseen
For testing propose I created the following folders with each containing
one unread message
INBOX, INBOX/level1 and INBOX/level1/level2
2019 Apr 21
2
FTS delays
Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue.
> On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote:
>
> For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh
2019 Apr 10
2
[BUG?] Double quota calulation when special folder is present
On Wed, Apr 3, 2019 at 9:37 PM Mark Moseley <moseleymark at gmail.com> wrote:
>
> On Wed, Mar 20, 2019 at 2:13 PM Mark Moseley <moseleymark at gmail.com>
> wrote:
>
>> Just hoping to get some dev eyes on this. I'm incredibly reluctant to
>> throw the word 'bug' around
>> (since 99 times out of 100, it's not -- it's almost always the