Hi Eric, Thanks for your info. Let me try and update here.
On Mon, Nov 16, 2020 at 11:04 PM Eric Broch <[email protected]> wrote: > It is up to you to determine the risks and to TEST! > > For rsync > > dhost=your.ip.address > > rsync --progress -zv -are ssh /home/vpopmail/domains/YOURDOMAIN/ACCOUNT/ > root@$dhost:/home/vpopmail/domains/YOURDOMAIN/ACCOUNT > > Tutorial: > https://www.digitalocean.com/community/tutorials/how-to-use-rsync-to-sync-local-and-remote-directories-on-a-vps > > DO NOT USE THE --delete OPTION. > > > For imapsync > > imapsync --host1 ip.host.one --user1 user1@domain1 --password1 mypasswd > --host2 ip.host.two --user2 user1@domain1 --password2 mypasswd > > Again, DO NOT USE THE --delete OPTION. > > Eric > On 11/16/2020 1:17 AM, ChandranManikandan wrote: > > Hi Eric, > > Please share the commands for imapsync & rsync. > > This is just to copy the standby server one week emails to the production > server which already had existing emails. > Any risk there. > > > > On Sun, Nov 15, 2020 at 1:00 PM Eric Broch <[email protected]> > wrote: > >> you could use imapsync or rsync >> >> Make sure you know what you're doing so as not to delete files on the >> production server. >> >> >> On 11/14/2020 9:42 PM, ChandranManikandan wrote: >> >> Hi Eric, >> >> Thanks for the update. >> I have shutdown standby server and only running production server, now >> everything is working without change or rsync from standby server. >> So as of now no changes and transfer certificate from standby server to >> production server. >> >> If any issue comes then will follow your above steps. >> >> >> Another help required from you. >> One week emails are in standby server, any possible way to transfer >> those emails to live production server while running the production server >> without affect any existing emailboxes. >> Need the commands. >> >> Appreciated your help. >> >> On Fri, Nov 13, 2020, 12:39 AM Eric Broch <[email protected]> >> wrote: >> >>> you could either re-run certificate or rsync the most recent >>> certificates over to the production server from standby >>> >>> Here's how I rsync (assume production server is 192.168.1.2): >>> >>> On standby server (if the most recent keys): >>> >>> # sshpass -p "`cat /root/rsyncpass`" rsync -zv -are ssh >>> /etc/letsencrypt/ [email protected]:/etc/letsencrypt >>> >>> On production server >>> >>> cp -p /var/qmail/control/servercert.pem >>> /var/qmail/control/servercert.pem.bak >>> >>> cat /etc/letsencrypt/live/mydomain.com/privkey.pem >>> /etc/letsencrypt/live/mydomain.com/fullchain.pem > >>> /var/qmail/control/servercert.pem >>> >>> restart dovecot >>> >>> stop/start qmail >>> >>> On 11/12/2020 8:54 AM, ChandranManikandan wrote: >>> >>> Hi Eric, >>> >>> Thanks, mine for Centos 7. >>> I need your help. >>> i have configured my domain ssl letsencrypt server in standby server two >>> days ago which my production was down. >>> Now the production server is up without any changes, >>> my standby server is down now, but still the website and certificate is >>> not working in ssl, >>> do i need to re-run the certificate again >>> >>> >>> On Thu, Nov 12, 2020 at 10:40 PM Eric Broch <[email protected]> >>> wrote: >>> >>>> Mine runs (and should run) w/o spamdyke... >>>> >>>> #!/bin/sh >>>> QMAILDUID=`id -u vpopmail` >>>> NOFILESGID=`id -g vpopmail` >>>> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >>>> SPAMDYKE="/usr/bin/spamdyke" >>>> SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf" >>>> SMTPD="/var/qmail/bin/qmail-smtpd" >>>> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb" >>>> HOSTNAME=`hostname` >>>> VCHKPW="/home/vpopmail/bin/vchkpw" >>>> export SMTPAUTH="-" >>>> >>>> # $SPAMDYKE --config-file $SPAMDYKE_CONF \ >>>> >>>> exec /usr/bin/softlimit -m 64000000 \ >>>> /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c >>>> "$MAXSMTPD" \ >>>> -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \ >>>> $SMTPD $VCHKPW /bin/true 2>&1 >>>> >>>> On 11/12/2020 7:34 AM, Jim McNamara wrote: >>>> > On 11/12/20 7:03 AM, ChandranManikandan wrote: >>>> > >>>> >> Hi Folks, >>>> >> >>>> >> Now it's working, >>>> >> >>>> >> I have done below changes in /var/qmail/supervise/smtp/run >>>> >> Just enabled spamdyke conf lines then working. >>>> >> >>>> >> #!/bin/sh >>>> >> QMAILDUID=`id -u vpopmail` >>>> >> NOFILESGID=`id -g vpopmail` >>>> >> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >>>> >> SPAMDYKE="/usr/bin/spamdyke" >>>> >> SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf" >>>> >> SMTPD="/var/qmail/bin/qmail-smtpd" >>>> >> TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb" >>>> >> HOSTNAME=`hostname` >>>> >> VCHKPW="/home/vpopmail/bin/vchkpw" >>>> >> REQUIRE_AUTH=0 >>>> >> #export FORCETLS=0 >>>> >> export SMTPAUTH="" >>>> >> >>>> >> >>>> >> exec /usr/bin/softlimit -m 64000000 \ >>>> >> /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c >>>> >> "$MAXSMTPD" \ >>>> >> -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \ >>>> >> $SPAMDYKE --config-file $SPAMDYKE_CONF \ >>>> >> $SMTPD $VCHKPW /bin/true 2>&1 >>>> >> >>>> > >>>> > <SNIP> >>>> > >>>> > I noticed this as well on CentOS8, if you remove spamdyke from the >>>> > smtp run file, the service will not run. It gives errors and does not >>>> > run at all. >>>> > >>>> > >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe, e-mail: >>>> [email protected] >>>> > For additional commands, e-mail: >>>> [email protected] >>>> > >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: >>>> [email protected] >>>> >>>> >>> >>> -- >>> >>> >>> *Regards, Manikandan.C * >>> >>> > > -- > > > *Regards, Manikandan.C * > > -- *Regards,Manikandan.C*
