Re: Changing the imaps port #

On Tue, 22 Jan 2019 at 06:17, Patrick Mahan wrote: > Dovecot 2.3.4, FreeBSD 11.2 > > Due to comcast buisness ISP intercepting imaps I need to have my clients > connect to non-standard port (). Previously I had been using stunnel > to receive the imaps connection and forward it to the imap po

Re: Changing the imaps port #

On 21 Jan 2019, at 21:58, Patrick Mahan wrote: > Re needing to say ssl = yes, I thought that was implied for imaps? I would think so, but all the examples I found in a quick search explicitly set it when changing the port. Also, unlike regular comcast, I have found the tech support on their bus

Re: How to connect to a remote server and execute eg a search

> On 21 Jan 2019, at 22.00, Marc Roos wrote: > > > > Thanks Sami, And I should allow access on the remote server via > login_access_sockets? And the authenticated user via this connection is > then testuser I presume? > No. It's the doveadm service that it's contacting: service doveadm

Re: Changing the imaps port #

Yes, I am pretty sure about that. I originally was connected via AT&T DSL but wanted the fast access of cable modem. I need permanent IPs which required me to contract with Comcast buisness. Once I switched over, I was no longer able to access my imap server, which was as I mentioned, stunnel li

Re: Changing the imaps port #

On 21 Jan 2019, at 20:17, Patrick Mahan wrote: > Due to comcast buisness ISP intercepting imaps At you sure about that? I've been using comcast business for 7 years and the do not block 143, 993 587 or 25. they do block 110, but that's fine, I stopped supporting POP around 2001. Other than 110

Changing the imaps port #

Dovecot 2.3.4, FreeBSD 11.2 Due to comcast buisness ISP intercepting imaps I need to have my clients connect to non-standard port (). Previously I had been using stunnel to receive the imaps connection and forward it to the imap port over 127.0.0.1. But I would like to retire stunnel and hav

Moving messages between servers with different configurations

I wanted to move messages from a mbox mailbox on server A to mdbox on server B. I thought I could do this by connecting to the remote server with "doveadm move -S x.x.x.x:x -u testuser Archive/2017 mailbox INBOX/test" but I guess this will only allow and move messages internally on server B?

RE: How to connect to a remote server and execute eg a search

Thanks Sami, And I should allow access on the remote server via login_access_sockets? And the authenticated user via this connection is then testuser I presume? > > > Is there a page that explains how to connect to a remote server? What > is the syntax of socket_path? > > > doveadm s

Re: How to connect to a remote server and execute eg a search

> On 21 Jan 2019, at 21.32, Marc Roos wrote: > > > Is there a page that explains how to connect to a remote server? What is > the syntax of socket_path? > > > doveadm search -S XXX -u testuser mailbox INBOX ALL -S : Sami

How to connect to a remote server and execute eg a search

Is there a page that explains how to connect to a remote server? What is the syntax of socket_path? doveadm search -S XXX -u testuser mailbox INBOX ALL

FOSDEM

Hello all, Several Open-Xchange/Dovecot folks will be attending FOSDEM in Brussels on 2-3 February 2019. For those of you planning to attend: we would love to meet and chat with members of the Dovecot community! Come find us wandering around the talks, or look for us in the evening. Rumor is

Re: Dovecot can't access mailbox that exists (nested)

On 21 January 2019 at 17:16 "@lbutlr" < krem...@kreme.com> wrote: On 21 Jan 2019, at 07:38, Edgaras Lukoševičius < edgaras.lukosevic...@gmail.com> wrote: # doveadm mailbox status -u n...@domain.com -t a

Re: Dovecot can't access mailbox that exists (nested)

On 21 Jan 2019, at 07:38, Edgaras Lukoševičius wrote: > > # doveadm mailbox status -u n...@domain.com -t all INBOX.* You’re doing better than I, whenever I try to use * I get # doveadm mailbox status -u krem...@kreme.com -t all * messages=0 recent=0 unseen=0 vsize=0 # doveadm mailbox list -u

Dovecot can't access mailbox that exists (nested)

Hello, I have this strange situation on nested mailboxes (directories) # dovecot --version 2.2.36 (1f10bfa63) # doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Cor

Re: Unexpected accounts showing up in replication status (doveadm replicator status '*')

Just an update that I think I know what has been going on. I believe I've been tripped up by two things. 1) Not always clearly reading the actual component being referred to when "userid", "user" and "username" are used in official online documentation or other web sources. 2) Setting up dov