similar to: dovecot-pigeonhole problems after upgrade to v2.3.0

December 28, 2017 2:52 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >>> >>> December 28, 2017 12:14 PM, "Aki

December 28, 2017 12:43 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: > >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >>> >>> Hello, >>> >>> After

December 28, 2017 12:14 PM, "Aki Tuomi" <aki.tuomi at dovecot.fi> wrote: >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: >> >> Hello, >> >> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's > > managesieve plugin. my emails are not

Which part? Hosting the email server at home or the relay in the cloud? On Dec 10, 2017 14:53, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > On December 10, 2017 3:39:05 PM EST, Stephan H <herker at gmail.com> wrote: > >I have dovecot postfix setup on my home server as well. I use a > >virtual > >server in the cloud as my mx record

Question; So after updating to 2.3.0 and following the recommended warnings / changes from running doveconf -n and then doing that same command > "a new conf file", and then renaming the conf files and restarting dovecot, I should be good to go with my old config updated to the new config spec? Just confirming. Thanks. What I mean is doing the -n to a new file hasn't changed or

I have dovecot postfix setup on my home server as well. I use a virtual server in the cloud as my mx record and mail relay and have my home record on dynamic dns. It's really effective. On Dec 10, 2017 2:37 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > On December 10, 2017 2:49:35 PM EST, "Andr? Rodier" <andre at rodier.me> >

> On December 27, 2017 at 6:05 PM "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > > > December 27, 2017 10:53 AM, aki.tuomi at dovecot.fi wrote: > > > Small amendment... > > > > if you ran > > > > gpg --export > /etc/apt/trusted.gpg.d/dovecot.gpg > > > > please run > > > > gpg --export

Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy

Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy

hello dovecot community, question; if my user database and dovecot installation is currently setup to use plain login passwords, and i want to convert to cram-md5, after i configure dovecot accordingly and reset passwords into cram-md5, if anyone uses plain login method again in the future, will it still work? or must they always from this point on use encrypted passwords? Thanks. -- Thanks,

Hello Mike, Yes, I am using a static IP address, but in theory, you could use a dynamic one. Nothing technically would prevent email exchanges between two boxes, as long as the SPF records are up to date and the DKIM is properly setup. Unfortunately, some ISPs are simply blacklisting full range of private IP addresses just because they are not officials / commercials. Kind regards, Andr? On

Hello, I have a forum system which can potentially have users send email to it for posting purposes that arrives addressed to a particular user account with a recipient delimiter: user+1a2b3c4d5e6f at domain.com The forum server is supposed to check the "user" account mailbox's inbox for the messages and post them to the site automatically. This doesn't work right now

dumb question warning: I have two email accounts, me at tld1 and me at tld2 often, get emails intended (by me) for me at tld2 sent to me at tld1 this is purely for my own preferred record keeping preference, as I run the server, is it 'a really bad things' if I simply copy relevant mail files from /var/vmail/vmail1/tld1..../cur to /var/vmail/vmail1/tld2.../cur ? rather than forward

I am running two servers with Dovecot v2.2.12 on CentOS x86_64 (5.10 and 6.5 respectively) and users are virtual over ldap. I have setup our main internal server (vmail.example.com) with dsync replication according to the first part of http://wiki2.dovecot.org/Replication. The second one (vmail1.example.com) will be the failover server which we want to be a real-time mirror (but can be

I have Centos 7 with dovecot/postfix/mysql Maildir I want to bring in a new server, new server will have same hostname as current, but, different IP I was intending to rsync -avzhe ssh vmail at oldserver:/var/vmail/vmail1 /var/vmail/vmail1 and, then, re run as necessary when/if mail still arrives on old server is that "a good plan" ...? TIA, V

On December 10, 2017 5:25:46 PM EST, Stephan H <herker at gmail.com> wrote: >Which part? Hosting the email server at home or the relay in the >cloud? > >On Dec 10, 2017 14:53, "Fabian A. Santiago" ><fsantiago at garbage-juice.com> >wrote: > >> On December 10, 2017 3:39:05 PM EST, Stephan H <herker at gmail.com> >wrote: >> >I have

On 30.07.2019 20:07, Tom Diehl via dovecot wrote: > > Does anyone have an Idea how to fix this? > > Regards, > Perhaps see if there are any denials in SELinux audit log: sudo grep denied /var/log/audit/audit.log | grep dovecot | audit2allow -a Good luck, Reio

I have a small Postfix/Dovecot/MariaDB on Centos 7 with a dozen virtual domains, I'm running out of space in /var but got space can I simply move the entire /var/vmail/vmail1 tree elsewhere ? like say /vmail/vmail1 is it as simple as shutting Dovecot/Postfix, move tree, edit conf and re start ? or am I missing something ..? or is the a better way of doing this ? # grep 'var/vmail'

Hello, I have setup v2.2.12 to mirror mailboxes between our main mail server (vmail.example.com) and a failover server (vmail1.example.com). The problem I have is the behavior of mailboxes used on the main server (*vmail*) over POP3. I have setup an IMAP account on the failover server (*vmail1*) on such a mailbox: the mailbox is used on vmail using POP3 and the same is monitored on vmail1

Dovecot version: 2.0.19 ------------------------------------------------------- grep -v '^ *\(#.*\)\?$' /etc/dovecot/dovecot-ldap.conf hosts = server.domain.tld:389 ldap_version = 3 auth_bind = yes dn = vmail at domain.tld dnpass = somepassword base = ou=testou,dc=domain,dc=tld scope = subtree deref = never