similar to: Advice on once a day message delivery setup

Hi all. We've just migrated our back-end NFS mailstore from FC1 systems to CentOS4 and are experiencing problems/delays with vpopmail and user Maildirs. IMAP is fine, it's just POP access that causes us problems. Now, NFS mounts successfully, the clients can see /home/vpopmail and serve content as we would expect. IMAP works perfectly and sees new messages as soon as they're

Having > 10 TByte mailstore filesystem-checks takes too much time. At the moment we have four different partitions, but I don't like to set symlinks or LDAP-flags to sort customers and their domains to there individual mount-point. I'd like to work with mdbox:/mail/%d/%n to calculate the path automatically. How do you handle >> 10 TB mailstore? I'm very interested in the

> On Feb 22, 2017, at 2:44 PM, Timo Sirainen <tss at iki.fi> wrote: > > I guess mainly the message sequence numbers in IMAP protocol makes this more difficult, but it's not an impossible problem to solve. Any thoughts on the wisdom of supporting an external database for session state or even mailbox state (like using Redis or even MySQL)? Also, would it help reliability or

HI All, We have a couple of dovecot director proxies and six backed mailstores each accessing mailboxes stored on five NFSv4 filsystems with about 1TB of mail on each in maildir format.? We have about 800 max users on each mailstore at peak times and performance appears to starting to degrade at these times.? The mailstores are pretty recent hardware with 64GB of RAM and 24 cores.?? The NFS

Greetings, I'm working with a new CentOS 7 installation, moving a system up from CentOS 5 due to OpenSSL version 0.9.8e not meeting PCI Compliance requirements. However, while setting up the CentOS 7 environment one of the closed source applications is requiring 0.9.8. The software vendor has advised installing package openssl098e from yum; but I'm hesitant to do so from a

Greetings, I'm running Dovecot 2.0.9 on my CentOS 6 server, for several thousand mailboxes. Recently, I've had several reports of "my mailbox is suddenly empty, where'd my mail go?" I've enabled debug logging, but I'd like to make sure I have the best level of debug to see things like "delete message" commands? I've configured in logging:

I'm using roundcube webmail managesieve plugin. Webmail can login managesieve to a specific mailstore successfully without proxying. Because I have mutiple mailstores, I have to use proxying to redirect the correct mailstores just as imap/pop3. ???? Stephan Bosch ????? 2016-04-03 22:50 ???? Hawk Chen; dovecot ??? Re: ??: Re: managesieve proxying not working Op 3-4-2016 om 16:32 schreef

On 10/21/2015 2:34 PM, Eero Volotinen wrote: > Remember that rhel/centos backports fixes, so just looking version > number is not reliable way to detect security issues. > > Eero Indeed, though I can say on CentOS 5 the required configuration to be PCI compliand is not valid in apache, and httpd will not start. -- ----------------------------------------------- - Nick Bright

I'm still learning firewalld obviously, and I am having trouble groking the documentation to understand how to do this. I know I could do an iptables direct, but that doesn't seem like the "right" way to do it. What I'm trying to do is allow a specific service, only for a specific ip. Effectively, SNMP should be allowed form a specific IP address (the systems monitor).

Dear list, One of my users is reading e-mail from his phone. When he logs in, this is what I see in my logs : Apr 10 16:17:58 auth-worker(17101): Debug: sql(xxx at mydomain.tld,52.184.164.73): query: SELECT email as user, password FROM users WHERE email = LOWER('xxx at mydomain.tld') [...] Apr 10 16:17:58 imap-login: Info: Login: user=<xxx at mydomain.tld>, method=LOGIN,

On 17 Nov 2015 17:30, "Nick Bright" <nick.bright at valnet.net> wrote: > > On 11/17/2015 11:12 AM, Nick Bright wrote: >> >> firewall-cmd --zone=monitoring --add-source=1.2.3.4/32 >> firewall-cmd --zone=monitoring --add-service=snmp >> firewall-cmd --zone=monitoring --add-interface=ens192 >> firewall-cmd --runtime-to-permanent > > I went

Hi All, I need to import mailboxes into my Director NFS setup via one of my director proxy's as doing a direct dsync to the backend mailstores appears to giving me NFS locking issues. It looks like it may be possible to do this using doveadm listeners. I have setup doveadm listeners on a test proxy and backend mailstore. I am not sure how to make the dsync proxy through to the backend

Hi All, I am using dovecot in the Director setup with multiple proxy and backend mailstores and user information stored in LDAP.? I am aware users can be directed to a single backend server.? It would be useful to be able to direct groups of users to pairs of backend servers to give some fault tolerance against NFS issues and make the whole thing more scalable.??? Otherwise each backend mailstore

On 10/21/2015 1:55 PM, Andrew Holway wrote: > Personally I would go round to that particular vendors office with a pipe > wrench and encourage them to do better however, unless this software is > transmitting credit card information then it seems that you could be > safe(ish) from the regulation standpoint. It really depends on the location > of the machine. Is it deep in the bowels

In CentOS 6.7 I ran setup command and I could configure network settings from that "gui" utility at command line. In CentOS 7 I don't know where this goes or how to enabled. I have installed a few packages: yum install setuptool -y \ && yum install system-config-network-tui -y \ && yum install system-config-firewall* -y \ && yum install

On 6 November 2015 at 21:49, Pete Travis <lists at petetravis.com> wrote: > On Nov 6, 2015 3:31 PM, "Nick Bright" <nick.bright at valnet.net> wrote: >> >> Greetings, >> >> One of my biggest frustrations with CentOS 7 has been firewalld. >> >> Essentially all of the documentation just flat doesn't work. >> >> One common

On 11/16/2015 01:39 PM, Nick Bright wrote: > This is very frustrating, and not obvious. If --permanent doesn't work > for a command, then it should give an error - not silently fail > without doing anything! But --permanent *did* work. What you're seeing is the documented behavior: --permanent The permanent option --permanent can be used to set options

Hello, I'm currently experimenting with the 2.1.x series and am facing a behavior I can't explain; I must be doing something wrong and probably miss the obvious... ;-) This is a very basic build on Mac OS X 10.8.2: ./configure --prefix=/_COD/dovecot-2.1.14 --sysconfdir=/_ETC --localstatedir=/_VAR --with-sqlite --with-ldap=yes (Yes, I know, a strange layout, yet very convenient for

Hello, With the same basic configs as in my previous messages, I tried with the maildir format instead of the mbox format. That is, in both cases ("virtual" uids/gids vs a single "real" uid/gid), doveconf -n shows: mail_location = maildir:~/maildir instead of: mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox Here too, with "virtual" uids/gids, connections thru

Hi All, I have dsync mirror command working between a standalone dovecot server and a backend mailstore in a Dovecot Director setup.?? Is it safe to do the dsync directly to the backend mailstore in this setup? It doesn't seem to work via the director proxy. Thanks Murray