Re: Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost

> Hi. > > On 17.01.2017 19:09, Andy Dorman via Info-cyrus wrote: >> >> I am not an expert by any means and I hope someone corrects me if I >> make a bad suggestion...but I have two questions: >> >> 1. It sounds like you have a heavily used server, so why do you have >> Cyrus listening on both "loca

Re: Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost

Sounds like you could consider partitioning (if you aren’t already) - then you can scale-out the disk iops without needing fancy hardware/software: https://www.cyrusimap.org/docs/cyrus-imapd/2.4.7/overview.php#partitions

Re: Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost

Hi. On 17.01.2017 19:09, Andy Dorman via Info-cyrus wrote: I am not an expert by any means and I hope someone corrects me if I make a bad suggestion...but I have two questions: 1. It sounds like you have a heavily used server, so why do you have Cyrus listening on both "localhost:lmtp" AND

Re: Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost

n 17 12:35:26 gw0 sm-mta[7]: v0H7ZML4078586: SYSERR(root): Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost This usually means that message bounced to MTA queue, where it can be hold for several minutes, sometimes dozens of minutes. I have the following direct

Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost

Could not connect to socket /var/imap/socket/lmtp: Connection refused by localhost This usually means that message bounced to MTA queue, where it can be hold for several minutes, sometimes dozens of minutes. I have the following directive in the cyrus.conf: SERVICES { ... lmtp cmd=&quo