similar to: ot: 2.2 ghettoforge install systemctl Q

Displaying 20 results from an estimated 10000 matches similar to: "ot: 2.2 ghettoforge install systemctl Q"

2017 Dec 16
1
ot: 2.2 ghettoforge install systemctl Q
On 16/12/17 20:45, Aki Tuomi wrote: >> I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used >> /etc/dovecot from current Centos 6 Dovecot 2.1 >> >> I can start/stop Dovecot with dovecot / doveadm stop >> >> BUT when I tried 'systemctl' I get >> >> # systemctl status dovecot >> ? dovecot.service - Dovecot IMAP/POP3
2017 Dec 16
0
ot: 2.2 ghettoforge install systemctl Q
> On December 16, 2017 at 1:59 AM voytek at sbt.net.au wrote: > > > I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used > /etc/dovecot from current Centos 6 Dovecot 2.1 > > I can start/stop Dovecot with dovecot / doveadm stop > > BUT when I tried 'systemctl' I get > > # systemctl status dovecot > ? dovecot.service - Dovecot
2017 Dec 16
7
ot: fail2ban dovecot setup
I'm trying to setup and test fail2ban with dovecot I've installed fail2ban, I've copied config from https://wiki2.dovecot.org/HowTo/Fail2Ban, and, trying to test it, attempted multiple mail access with wrong password, but, get this: # fail2ban-client status dovecot-pop3imap Status for the jail: dovecot-pop3imap |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- File
2017 Aug 11
1
new install on Centos 7
On Thu, August 10, 2017 6:35 pm, Peter wrote: > GhettoForge has dovecot22 packages as well which provide the latest > stable version of Dovecot for CentOS 6 and 7. Peter, thanks. I've followed GhettoForge's Postfix page, so far so good but, I'm not that sure of getting dovecot22... do I need to do a 'yum shell --enablerepo=gf-plus', followed by install, run, quit;
2017 Aug 10
2
new install on Centos 7
I currently have Postfix Dovecot MySQL on Centos 6, looking at migrating to new server new server is CentOS 7.3, but, the Centos repo version is dovecot x86_64 1:2.2.10-7.el7 what is the best way to install current release Dovecot on a new server ? tia, V
2017 Aug 17
1
autocreate deprecated q
On Thu, August 17, 2017 5:03 pm, Aki Tuomi wrote: > >> On August 17, 2017 at 8:56 AM voytek at sbt.net.au wrote: > > autocreate and autosubscribe are moved under mailbox settings > > namespace { mailbox FooBox { auto = create } > mailbox Trash { auto = subscribe } > } Aki, thanks I've inserted it, but, maybe not in the correct place ? Aug 17 17:22:43 imap(ve at
2017 Aug 17
2
autocreate deprecated q
I'm getting "autocreate plugin is deprecated" I've removed 1) but still see error am I correct I don't need default IMAP folders in dovecot.conf as they come from 15-mailboxes.conf ? # grep autocreate dovecot.conf lda_mailbox_autocreate = yes mail_plugins = quota sieve autocreate mail_plugins = quota imap_quota autocreate do I just remove BOTH 'mail_plugin ...
2019 Mar 03
2
migrating/cloning 2.2 > 2.3?
I have 2.2 installation on Centos 7, and, I'm trying to setup a new server, and, 'clone' existing setup: Dovecot/Postfix/Mysql on new Centos 7 installed from RPM 2.3.4.1 (3c0b8769e) I then copied/overwrote from old to new /etc/dovecot/*.conf (but not conf.d files), created self certs in place of old server certs and, started Dovecot is that totally dumb, and, how should I do this,
2018 Jul 22
4
ot: LE server conf setup/ iPhone 'expired cert' message
I've installed LE certs on my Dovecot a while back, and, it has been working OK since, but, today, an iPhone user said he can't get emails as iphone says 'cert is expired', searching around, I see some other iPhone similar issues reported, do I have my conf correct, I have; # cat dovecot.conf | grep ssl ssl = required verbose_ssl = no ssl_cert =
2012 Jul 10
6
getting rid of old spam from +spam Maildir ?
I'm trying to setup per user '+spam' delivery from amavis tags, so that each user gets any mails tagged as spam to 'spam' Maildir via +spam Dovecot lmtp delivery. after say 7 days I want to delete all spams older than 7 days, if I simply delete mail files from the file system, is that a 'bad thing' ? what is a proper way to do that, and scripts ? for
2019 May 31
3
sieve setup. no svbin ?
On Fri, May 31, 2019 10:18 am, Ralph Seichter via dovecot wrote: > * Voytek Eymont via dovecot: > Try runing "sievec -u {your_linux_user} /path/to/whatever.sieve" from a > shell and check the resulting error messages. Raplh, thanks so, am I'm missing sql lookup for sieve...? # sievec -u voytek dovecot.sieve sievec(voytek)<9667><>: Error: user voytek: Auth
2019 May 30
2
sieve setup. no svbin ?
since moving/upgrading system I've noticed I no longer get sieve script compiled, there is no dovecot.svbin created in /var/vmail/vmail1/sbt.net.au/voytek at tld.au/sieve what am I missing, how to check ? also, looking at sieve.log, I see a lot of May 31 06:32:50 lda(voytek at sbt.net.au)<1234><c4aVBfI98FzSBAAAyLbbsQ>: Error: sieve: Failed to initialize script execution: Invalid
2011 Apr 08
1
mysql lookup on another host performance q?
Hi, new to dovecot I'm setting a small postfix/dovecot server for virtual domain/users in mysql dovecot is on one host, mysql on another seems to be working, but I'm concerned over performance overhead of this setup; dumb Q, is there any 'proxy mysql' or cacheing option I can use ? any suggestions appreciated also, my mail users as set as 5000/5000 virtual_gid_maps =
2017 Aug 29
2
Syncronize systemctl status with reality?
The particular issue is with puppetmaster (which admittedly takes 4 minutes to actually start, setting TimeoutStartSec=300 in it's unit file stopped the false timeout report) but I have seen it one other time (don't remember the details). systemctl status puppetmaster ? puppetmaster.service - Puppet master Loaded: loaded (/lib/systemd/system/puppetmaster.service; enabled; vendor
2011 Sep 06
1
dumb Q: how to search for email hack attempts ?
one of the users thinks someone hacked his email, I don't have time this morning to analyze mail logs in detail, but does some one has some tips to simply searching mail logs for multiple log in attempts, etc, I'd appreciate some grepping for failed logins show give some clues ?
2017 Aug 20
4
pop 110/995, imap 143/993 ?
just setting a new Dovecot server to migrate from older system, but, I have a general question: 1. I've set the server with self issued cert, and both pop/imap StartTLS/110/143 SSL/993/995 (apologies if I'm using wrong naming terminology) is there a 'preferred way'? should I tell users to use 143 over 993 ? or 993 over 143? or? my current understanding is that some (MS?)
2016 May 25
4
ot: migrating TB user's email to new laptop
On Wed, May 25, 2016 4:31 pm, Philip McGaw wrote: > Did user historically have POP set up? Philip, thanks no, not for a long time, IMAP/143/StartTLS on old laptop > If you still have access to the old laptop set up imap and move the > emails back. yes, I have old laptop here. sorry, not sure how to, is that inside TBird, or how ? (not very familiar with TBird...) >> another OT:
2018 Jan 16
1
MyISAM Too many open files; + index.cache: Cannot allocate memory
installed new Dovecot 2.2 on Centos 7, and, migrated some users from old server # dovecot --version 2.2.33.2 (d6601f4ec) works OK, but, noticed some sql and index.cache errors what am I missing ? only noticed this one so far ------------------ # grep "Too many open files" /var/log/dovecot.log Jan 02 15:22:16 auth-worker(1411): Warning: mysql: Query failed, retrying: Got error 24
2017 Aug 21
4
pop 110/995, imap 143/993 ?
On 21/08/17 10:37, Gedalya wrote: > On 08/21/2017 07:28 AM, voytek at sbt.net.au wrote: >> is there a 'preferred way'? should I tell users to use 143 over 993 ? or >> 993 over 143? or? > There is no concrete answer. There are various opinions and feelings about this. > The opinion againt 993/995 is that these are not standard ports, Out of curiosity, is there a
2020 May 07
4
ot: copy physical mail files ?
> Am 07.05.2020 um 17:15 schrieb Admin dishaw.org <admin at dishaw.org>: > > > >> On May 6, 2020, at 9:45 PM, Voytek Eymont <voytek at sbt.net.au> wrote: >> >> 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 >> >>