Re: [qmailtoaster] Re: EZMLM list management issues

[Boheme]

But I can’t unsubscribe using the CLI tools, and there is no error output. 

-Sent from my Pip-Boy 3000

> On 3/03/2022, at 1:40 AM, qmailtoas...@dukat.dk wrote:
> 
> Hi Chris
> 
> Have you looked carefully for relevant information in web servers log files?
> 
> - Allan
> 
>> On 2022-03-02 10:01, Chris Knight wrote:
>> I’m still having ezmlm issues.  I can’t delete users from the command
>> line, from qmailadmin, or via email commands.  Permissions on all
>> files in the list directory are vpopmail:vchkpw
>> Has anyone else encountered this?
>> -Chris
 On Feb 6, 2022, at 7:45 AM, Chris Knight  wrote:
>>> I’ve got a toaster that has been running fine for a long while.  One of my 
>>> friends who I host email for reported that they are unable to unsubscribe 
>>> someone from a mailing list they run.  I logged in, and tried to manually 
>>> use the ezmlm-unsub command, and yet the email address refuses to be 
>>> removed from the mailing list.  I’ve checked permission in the 
>>> [list]/subscribers/ directory, and all files are owned by vpopmail:vchkpw
>>> Has anyone else had problems with list management?
>>> My package version is ezmlm-0.53.324-0.qt.el7.x86_64
>>> -Chris
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Let's Encrypt "DST Root CA X3" expires today

[Boheme]

I was about to suggest that. :)

https://access.redhat.com/errata/RHBA-2021:3649

-Sent from my Pip-Boy 3000

> On 1/10/2021, at 9:25 AM, Quinn Comendant  wrote:
> 
> On 30 Sep 2021 13:02:51, Quinn Comendant wrote:
>> I have a RoundCube server that is now unable to connect to an IMAP 
>> server (older qmailtoaster running couriertls). The error in the 
>> imap4-ssl log is "sslv3 alert certificate expired".
> 
> I was able to solve this by updating the `ca-certificates` package on the 
> server running RoundCube. `ca-certificates` version 2021.2.50–72 removes DST 
> Root CA X3. https://access.redhat.com/errata/RHBA-2021:3649
> 
> Quinn

Re: [qmailtoaster] Future of qmailtoaster on CentOS?

[Boheme]

I’ve been meaning to learn to compile all the source for Ubuntu for a while. 
This may be the kick in the pants I needed. 

-Sent from my Pip-Boy 3000

> On 10/12/2020, at 12:50 AM, Angus McIntyre  wrote:
> 
> Does anyone have any thoughts on the likely future of qmailtoaster given the 
> new plans for CentOS?
> 
> (See https://centos.org/distro-faq/ for more details)
> 
> I'd never actually heard of CentOS Stream before today, but having just 
> painfully built a working toaster on top of CentOS 8, I'm a little 
> apprehensive about the impact of the proposed changes.
> 
> Comments?
> 
> Angus
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Email backup to external storage

[Boheme]

I use a Restic. The website can explain it better, but it does encrypted 
incremental snapshot backups to remote storage systems, in my case I use B2 
from Backblaze. B2 costs around $5/month/TB, and with the way the snapshot 
backups work I have easily accessible backups going back several years. 

Check it out:  https://restic.net/

-Chris



-Sent from my Pip-Boy 3000

> On 30/10/2020, at 7:57 PM, ChandranManikandan  wrote:
> 
> 
> Hi Folks,
> 
> Could anyone use Email backup into external storage like NAS or cloud storage?
> 
> Am running COS7 with qmail in two machines
> One machine is 1 TB email size and Hard disk size is 4 TB
> Another machine is 600 GB email size and hard disk size is 1 TB.
> 
> How do I take automatic email backup to an external device, in case of any 
> problem like Virus,malware,ransom ware etc.. then we can recover from that.
> 
> Please suggest me 
> Advance thanks.
> 
> -- 
> Regards,
> Manikandan.C

Re: [qmailtoaster] Distressing strange behavior

[Boheme]

It doesn’t sound like you are being repeatedly hacked. It sounds like your 
reputation dropped with google, and certain emails trigger their anti-spam 
filtering now. Not all of them, just some. I have problems with Google 
accepting email regularly sometimes, and dropping other emails into people’s 
spam folders, as a result of too many of my users forwarding email to google 
and those forwards passing along a lot of spam to their addresses on my server. 

-Sent from my Pip-Boy 3000

> On 17/08/2020, at 8:46 AM, Charles Hockenbarger  wrote:
> 
> 
> As I understand the forwards setup in qmailadmin those are in the database, 
> right?
> 
> The address that was compromised hasn't sent any email since the password 
> change. 
> 
> I hadn't thought about looking at qmail-inject. I'll dig into watching that 
> part of the process. 
> 
> Get TypeApp for Android
>> On Aug 16, 2020, at 3:14 PM, Eric Broch  wrote:
>> How do you have your forwards set up?
>> 
>> Is there any mail in your queue?
>> 
>> If someone hacked an account on your server with forwards to gmail accounts 
>> they aren't limited to just these forwards, they also have the option in the 
>> email client to add gmail accounts in the "To:" field of the email they're 
>> sending, thus bounces from gmail accounts that aren't in your forwards file.
>> 
>> Also, qmail-inject puts mail in the queue and you'll see it in the send log.
>> 
>> 
>> 
>>> On 8/16/2020 10:05 AM, Chas Hockenbarger wrote: 
>>> I'm hoping someone has encountered this weird behavior or something like it 
>>> before and can point me down a path, because all my research has turned up 
>>> nothing so far.
>>>  
>>> 
>>> I had an email account recently get breached due to a re-used password, and 
>>> that account was used to send a bunch of spam out from a server I help 
>>> manage.  We changed the password on the account as soon as we found it 
>>> happening and the outbound flood stopped.
>>>  
>>> 
>>> Shortly after that, however, I started seeing a very, very strange 
>>> behavior.  Sometimes, and I haven’t yet been able to identify the trigger 
>>> or pattern, when users on this server send email to a forward that contains 
>>> around 50 or so email addresses (they use it like a private distribution 
>>> list) they will get anywhere from 1-10 bounces from Gmail.  Not every email 
>>> sent to the forward has this happen, and not even every email from a 
>>> particular user.
>>>  
>>> 
>>> The outbound spamming caused the server’s reputation to go in the tank with 
>>> Google, and if it weren’t for that, I wouldn’t know this was happening, 
>>> because they get the bounces from Gmail accounts that absolutely ARE NOT in 
>>> the forward or part of the email chain AT ALL.
>>>  
>>> 
>>> I’m kind of freaking out here because while I haven’t found a breach of the 
>>> actual server / OS, this feels like someone has been able to inject 
>>> something somewhere into my server that I simply can’t find.  It is 
>>> especially troubling because a user who is not on this domain, but is part 
>>> of the group and therefore uses the forward from time to time, sent 
>>> something to the forward today and got Gmail bounces.   
>>>  
>>> 
>>> I don’t see anything in the send log that shows the server even trying to 
>>> send to Gmail, which only adds to the ghost story.
>>>  
>>> 
>>> Any ideas, paths to go down, anything would be greatly appreciated here.  
>>> I’m about to just rebuild the whole thing from scratch on a new VM, but if 
>>> I’m overlooking something simple don’t want to put the users through that.
>>>  
>>> 
>>> Thanks in advance.
>>>  
>>> 
>>> Chas

Re: [qmailtoaster] IMAP problems after recent update?

[Boheme]

Yes, the user is IMAP

-Sent from my Pip-Boy 3000

> On 11/08/2020, at 11:09 AM, Eric Broch  wrote:
> 
> Is this IMAP?
> 
>> On 8/10/2020 1:10 PM, Chris wrote:
>> Over the weekend I updated a few packages on my system. Full list below.  
>> This morning one of my users who is using Thunderbird on an ancient Windows 
>> box reported to me that they can't check email anymore. They can get to the 
>> web page for my mail server, so it isn't network connectivity.  Nobody else 
>> has reported a problem.  My first thought was that the update changed the 
>> available TLS versions and his old box can't connect anymore, but the 
>> dovecot configs haven't changed.  Has anyone else experienced anything 
>> similar?
>> 
>> While fail2ban is installed, it isn't configured or running.  I also checked 
>> that.  :)
>> 
>> -Chris
>> 
>> 
>> 
>> 
>> 
>> ---> Package autorespond.x86_64 0:2.0.5-0.qt.el7 will be updated
>> ---> Package autorespond.x86_64 0:2.0.5-1.qt.el7 will be an update
>> ---> Package certbot.noarch 0:1.5.0-1.el7 will be updated
>> ---> Package certbot.noarch 0:1.6.0-1.el7 will be an update
>> ---> Package dbus.x86_64 1:1.10.24-13.el7_6 will be updated
>> ---> Package dbus.x86_64 1:1.10.24-14.el7_8 will be an update
>> ---> Package dbus-libs.x86_64 1:1.10.24-13.el7_6 will be updated
>> ---> Package dbus-libs.x86_64 1:1.10.24-14.el7_8 will be an update
>> ---> Package fail2ban.noarch 0:0.10.5-2.el7 will be updated
>> ---> Package fail2ban.noarch 0:0.11.1-9.el7.2 will be an update
>> ---> Package fail2ban-firewalld.noarch 0:0.10.5-2.el7 will be updated
>> ---> Package fail2ban-firewalld.noarch 0:0.11.1-9.el7.2 will be an update
>> ---> Package fail2ban-sendmail.noarch 0:0.10.5-2.el7 will be updated
>> ---> Package fail2ban-sendmail.noarch 0:0.11.1-9.el7.2 will be an update
>> ---> Package fail2ban-server.noarch 0:0.10.5-2.el7 will be updated
>> ---> Package fail2ban-server.noarch 0:0.11.1-9.el7.2 will be an update
>> ---> Package kernel.x86_64 0:3.10.0-1127.18.2.el7 will be installed
>> ---> Package kernel-headers.x86_64 0:3.10.0-1127.13.1.el7 will be updated
>> ---> Package kernel-headers.x86_64 0:3.10.0-1127.18.2.el7 will be an update
>> ---> Package kernel-tools.x86_64 0:3.10.0-1127.13.1.el7 will be updated
>> ---> Package kernel-tools.x86_64 0:3.10.0-1127.18.2.el7 will be an update
>> ---> Package kernel-tools-libs.x86_64 0:3.10.0-1127.13.1.el7 will be updated
>> ---> Package kernel-tools-libs.x86_64 0:3.10.0-1127.18.2.el7 will be an 
>> update
>> ---> Package python-perf.x86_64 0:3.10.0-1127.13.1.el7 will be updated
>> ---> Package python-perf.x86_64 0:3.10.0-1127.18.2.el7 will be an update
>> ---> Package python2-acme.noarch 0:1.5.0-1.el7 will be updated
>> ---> Package python2-acme.noarch 0:1.6.0-1.el7 will be an update
>> ---> Package python2-certbot.noarch 0:1.5.0-1.el7 will be updated
>> ---> Package python2-certbot.noarch 0:1.6.0-1.el7 will be an update
>> ---> Package qmail.x86_64 0:1.03-3.qt.el7 will be updated
>> ---> Package qmail.x86_64 0:1.03-3.2.qt.el7 will be an update
>> ---> Package qmailadmin.x86_64 0:1.2.16-2.qt.el7 will be updated
>> ---> Package qmailadmin.x86_64 0:1.2.16-3.2.qt.el7 will be an update
>> ---> Package spamassassin.x86_64 0:3.4.1-1.qt.el7 will be updated
>> ---> Package spamassassin.x86_64 0:3.4.2-2.qt.el7 will be an update
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] local queue increasing /slow delivery / multiple copies of same email

[Boheme]

What do you need to do in that cron job for cleanup?

-Sent from my Pip-Boy 3000

> On 11/08/2020, at 6:33 AM, Remo Mattei  wrote:
> 
> 
> 
>>> On Aug 10, 2020, at 11:29 AM, Diego Piñon Conde  
>>> wrote:
>>> 
>>> Thank you to all the guys who help me to reestablish my toaster, especially 
>>> to Eric, Remo and Philip.
>>> 
>> No problems
>> 
>> Do you think the real culprit off this mess was dspam?
>> 
>> 
> I use DSPAM on my side for years never had any issues
>> if yes, do you think it is recommended to make a purge/clean of this db time 
>> to time? Or this was just a strange case?
>> 
> I run a cron job on my side to clean/purge 
>> 
>> At this stage spamdike was the only who use dspam isn't? Disabling spamdike 
>> could have allowed local queued emails to flow normally while the error was 
>> resolved? 
>> 
>> Again, thank you Eric for your invaluable and selfless help and your great 
>> work with qmailtoaster.
>> 
> Hopefully that helps answer your questions. 
> 
> Ciao 
>> El 08/08/2020 a las 06:45 p. m., Eric Broch escribió:
>>> I'm not sure what to say at this point, maybe run the attached script.
>>> 
>>> All it does is reinstall the relevant packages and change the permissions 
>>> appropriately
>>> 
>>> If that doesn't work, I saw Remo's offer for a Zoom session and their's 
>>> always the ClamAV users' list.
>>> 
>>> I'd be interested to know the problem.
>>> 
>>> Eric
>>> 
>>> On 8/8/2020 12:01 PM, Diego Piñon Conde wrote:
 sure!
 
 root  6126  1.0  0.0 112812   964 pts/1S+   14:59   0:00 
 grep --color=auto clam
 clamupd+ 30315  0.0  0.2 130376  4028 ?Ss   12:00   0:00 
 /usr/bin/freshclam -d --foreground=true
 
 
 El 08/08/2020 a las 02:38 p. m., Eric Broch escribió:
> can you do this
> 
> # ps aux |grep clam
> 
> and post output
> 
> On 8/8/2020 11:28 AM, Diego Piñon Conde wrote:
>> sorry for the delay Eric!, I was travelling to home...
>> 
>> Job for clamd@scan.service failed because the control process exited 
>> with error code. See "systemctl status clamd@scan.service" and 
>> "journalctl -xe" for details.
>> 
>> Did not start...
>> 
>> systemctl status clamd@scan.servic
>> 
>> ● clamd@scan.service - clamd scanner (scan) daemon
>>Loaded: loaded (/usr/lib/systemd/system/clamd@.service; enabled; 
>> vendor preset: disabled)
>>Active: failed (Result: start-limit) since Sat 2020-08-08 14:15:23 
>> -03; 3min 28s ago
>>  Docs: man:clamd(8)
>>man:clamd.conf(5)
>>https://www.clamav.net/documents/
>>   Process: 4316 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf 
>> (code=exited, status=1/FAILURE)
>> 
>> Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner (scan) 
>> daemon.
>> Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered 
>> failed state.
>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff time 
>> over, scheduling restart.
>> Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan) daemon.
>> Aug 08 14:15:23 pegasus systemd[1]: start request repeated too quickly 
>> for clamd@scan.service
>> Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner (scan) 
>> daemon.
>> Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered 
>> failed state.
>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
>> Hint: Some lines were ellipsized, use -l to show in full.
>> 
>> journalctl -xe
>> 
>> -- The result is failed.
>> Aug 08 14:15:23 pegasus systemd[1]: Unit clamd@scan.service entered 
>> failed state.
>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service failed.
>> Aug 08 14:15:23 pegasus systemd[1]: clamd@scan.service holdoff time 
>> over, scheduling restart.
>> Aug 08 14:15:23 pegasus systemd[1]: Stopped clamd scanner (scan) daemon.
>> -- Subject: Unit clamd@scan.service has finished shutting down
>> -- Defined-By: systemd
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>> --
>> -- Unit clamd@scan.service has finished shutting down.
>> Aug 08 14:15:23 pegasus systemd[1]: start request repeated too quickly 
>> for clamd@scan.service
>> Aug 08 14:15:23 pegasus systemd[1]: Failed to start clamd scanner (scan) 
>> daemon.
>> -- Subject: Unit clamd@scan.service has failed
>> -- Defined-By: systemd
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>> --
>> -- Unit clamd@scan.service has failed.
>> --
>> 
>> 
>> El 08/08/2020 a las 12:26 p. m., Eric Broch escribió:
>>> Diego
>>> 
>>> Please try this new configuration file...
>>> 
>>> Attached is a new scan.conf (scan.conf.test).
>>> 

[qmailtoaster] Upgraded email to testing version, now only plain passwords accepted for authed smtp?

[Boheme]

In an attempt to resolve my duplicate email issues, I upgraded to the version 
of email in the testing repo. Now email can only be sent on 587 with plain 
passwords. Since I have everyone using TLS that’s still secure, but it’s 
causing a headache for existing non-technical users who’s settings suddenly 
don’t work. 

Was this an expected change?
Is it reversible, or has the md5 challenge response been completely removed?

-Sent from my Pip-Boy 3000
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Re: Email delivery repeats

[Boheme]

Nope. It’s insanely random. 

-Sent from my Pip-Boy 3000

> On 16/07/2020, at 5:27 AM, Eric Broch  wrote:
> 
> 
> Can you repeat this error at will?
> 
>> On 7/10/2020 2:15 AM, Chris wrote:
>> I've disabled spamdyke, the source of the 421 timeout error; but I'm still 
>> getting re-delivery of emails.  Not as frequently, but I've received the 
>> same two emails a dozen times today.
>> 
>> Has anyone else experienced this before?
>> 
>> -Chris
>> 
>> On Tue, Jun 30, 2020 at 7:30 AM Chris  wrote:
>>> A few nights ago I shut down the VM that my qmailtoaster runs on, bumped 
>>> the memory up to 4g, and restarted it.  First reboot in a long while, so I 
>>> was nervous.  Everything seemed fine.  
>>> 
>>> The next day I noticed that there were a couple of emails I had deleted 
>>> that had re-appeared.  I'd delete them again, and they'd come back again.  
>>> My mail client shows date sent and date received, and they were definitely 
>>> all the same sender time.  Checking the logs, I see the same set of email 
>>> being re-accepted in /var/log/qmail/smtp/current over and over.
>>> 
>>> Finally I have a clue.  Gmail sent me a delivery warning about one of the 
>>> emails, as it was a test message from myself, and it says my server is 
>>> responding with error:
>>> 
>>> 421 Timeout. Talk faster next time.
>>> 
>>> So it seems the email is getting accepted, but then the sending server is 
>>> given an error 421, so it queues it up for re-delivery.
>>> 
>>> Any suggestions on what I should be looking at to figure this out?
>>> 
>>> -Chris

Re: [qmailtoaster] qmailtoaster and clamav version: 0.102.2

[Boheme]

What does the ‘many domain option for vpopmail’ provide?  Is that the component 
that gives us virtual domain hosting?

-Sent from my Pip-Boy 3000

> On 20/02/2020, at 5:04 AM, Eric Broch  wrote:
> 
> I'll get the new version out in the next couple of days.
> 
> Ultimately with CentOS 8, and maybe 7 at a later date, I'm moving to the 
> standard repos (EPEL or CentOS) for clamav and spamassassin.
> 
> I'm considering the same with Dovecot (moving away from the many domain 
> option for vpopmail) and its necessity of being compiled with vpopmail-devel.
> 
> These things will make QMT less time consuming to maintain.
> 
> As far as Dovecot I'll float this with the QMT community before doing 
> anything.
> 
> Eric
> 
>> On 2/19/2020 8:04 AM, あいざわひろし wrote:
>> hello qmailtoaster-list
>> 
>> yesterday I found freshclam saying
>> |WARNING: Your ClamAV installation is OUTDATED!
>> |WARNING: Local version: 0.101.4 Recommended version: 0.102.2
>> 
>> but at
>> ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/7/testing/x86_64/
>> clamav-0.101.4-10.qt.el7.x86_64.rpm
>> looks latest.
>> 
>> How can I update clamav ?
>> 
>> --
>> AIZAWA Hiroshi
>> 
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] letsencrypt cert renewal commands

[Boheme]

Depending on the commands you used for your initial cert generation, you might 
not need the standalone option. If you did DND or webroot validation you’re may 
need to tweak the command line. 

-Sent from my Pip-Boy 3000

> On 13/12/2019, at 4:47 PM, ChandranManikandan  wrote:
> 
> 
> Thanks Chris,
> 
> Let me try out above all of your options and update you.
> 
>> On Wed, Dec 11, 2019 at 1:54 AM Chris  wrote:
>> Running certbot nightly is excessive.  You can't renew until you get near 
>> the end if the current expiration period.  Also, there are other things you 
>> may need to do as part of the cert replacement on a qmailtoaster box.  I 
>> have this cronjob:
>> 
>> 1 1 1 * * /root/migration/certbot.sh
>> 
>> That runs this script: (/root/migration/certbot.sh)
>> 
>> #!/bin/sh
>> 
>> qmailctl stop
>> systemctl stop dovecot
>> systemctl stop httpd
>> 
>> TIMESTAMP=`date +"%Y%m%d-%H%M%S"`
>> cp -a /var/qmail/control/servercert.pem 
>> /var/qmail/control/servercert.pem-$TIMESTAMP
>> certbot renew --agree-tos  --standalone
>> cat 
>> /etc/letsencrypt/live/[SERVERNAME-REDACTED]/{cert,chain,fullchain,privkey}.pem
>>  > /var/qmail/control/servercert.pem
>> chmod 640 /var/qmail/control/servercert.pem
>> chown vpopmail.vchkpw /var/qmail/control/servercert.pem
>> 
>> 
>> qmailctl start
>> systemctl start dovecot
>> systemctl start httpd
>> 
>>> On Tue, Dec 3, 2019 at 9:03 PM ChandranManikandan  wrote:
>>> Hi Friends,
>>> 
>>> I have installed letsencrypt on COS7 and i try to make cron job as per the 
>>> below steps, but the cert renew and certbot folder are not there in /opt.
>>> 
>>> 0 0 * * * /root /opt/certbot renew
>>> 
>>> Is any other way is there or did i made any mistake?
>>> Anyone had the same problem?
>>> 
>>> -- 
>>> Regards,
>>> Manikandan.C
> 
> 
> -- 
> Regards,
> Manikandan.C

Re: [qmailtoaster] Re: Running QMT7 at Amazon AWS

[Boheme]

EFS is network file storage where you pay for what you are using, and you can 
mount it simultaneously on multiple machines. I don’t recall whether it’s NFS 
or SMB under the covers. 

https://aws.amazon.com/efs/

-Sent from my Pip-Boy 3000

> On 9/06/2019, at 1:34 PM, Jeff Koch  wrote:
> 
> Hi Chris:
> 
> We'll create an instance with a 500GB root disk of standard SSD storage - I 
> believe that is Elastic Block Storage. Not sure what you mean by EFS.
> 
> Jeff
> 
>> On 6/8/2019 7:01 PM, Chris wrote:
>> Out of curiosity, are you planning on keeping your message store on EBS or 
>> EFS?
>> 
>>> On Sun, Jun 9, 2019 at 9:21 AM Jeff Koch  wrote:
>>> Hi Eric - thanks - based on the great responses from the list I'm going 
>>> with the CentOS 7 AMI.  Jeff
>>> 
 On 6/8/2019 2:16 PM, Eric Broch wrote:
 Hi Jeff,
 
 Be mindful of the openssl version on this AWS Linux. QMT/COS7 use 
 openssl-1.0.2k. Openssl-1.1.1 will require a patched QMT.
 
 Eric
 
> On 6/7/2019 5:21 PM, Jeff Koch wrote:
> 
> Has anyone tried running QMT7 on Amazon AWS? We have a new instance with 
> Linux kernel 4.14, x86_64, systemd 219, GCC 7.3, Glibc 2.26, Binutils 
> 2.29.1,. I'm wondering whether we can just load the rpms and qmail will 
> run.
> 
> Jeff
>>> 
> 

Re: [qmailtoaster] test

[Boheme]

This received message got to me two hours before the test message. :)

-Sent from my Pip-Boy 3000

> On 27/11/2018, at 5:44 AM, Sean Murphy  wrote:
> 
> Received.
> 
> 
>> On 11/26/2018 11:43 AM, Eric Broch wrote:
>> 
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] COS 6.10 qmt build error.

[Boheme]

Do you need volunteers for mirrors?  

-Sent from my Pip-Boy 3000

> On Sep 12, 2018, at 9:32 AM, Eric Broch  wrote:
> 
> Tony,
> 
> And replace
> 
> http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm
>  
> 
> http://mirror2.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm
>  
> 
> 
> I'm not sure how many qmailtoaster mirrors are left...probably mine (mirror2) 
> and that's it.
> 
> 
>> On 9/11/2018 3:26 PM, Eric Broch wrote:
>> Have a look here: https://www.qmailtoaster.org/ under CentOS 6
>> 
>> -Eric
>> 
>> 
>>> On 9/11/2018 9:59 AM, Tony White wrote:
>>> Hi folks,
>>>   Trying to create a new COS6 server.
>>> 
>>> All ok up to qt-bootstrap-2
>>> where i get this error
>>> 
>>> qt-bootstrap-2 - installing qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm 
>>> (repo) ...
>>> Retrieving 
>>> http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm
>>> 
>>> 
>>> curl: (51) SSL: certificate subject name 'monk13.stakehouse.io' does not 
>>> match target host name 'mirrors.qmailtoaster.com'
>>> error: skipping 
>>> http://mirrors.qmailtoaster.com/current/nodist/qmailtoaster-release-2.0-1.qt.nodist.noarch.rpm
>>>  - transfer failed
>>> qt-bootstrap-2 - installing qmailtoaster-util (scripts) ...
>>> 
>>> Any help appreciated please...
>>> 
>> 
> 
> -- 
> Eric Broch
> White Horse Technical Consulting (WHTC)
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Odd error in dovecot.log

[Boheme]

Well, I get why it was establishing a connection, as I had just restarted 
dovecot. Just seemed odd that it was trying to access a table that doesn’t 
exist. But if legacy code from before the table-per-domain refactoring if the 
vpopmail DB layout?

-Sent from my Pip-Boy 3000

> On Nov 7, 2017, at 5:08 AM, Eric Broch  wrote:
> 
> Here's the explanation in the code as a result of the 'mysql_query' and 
> 'mysql_error' call:
> 
> if (mysql_query(_read,SqlBufRead)) {
> fprintf(stderr, "vmysql: sql error[3]: %s\n", 
> mysql_error(_read));
> /*  - May 29, 2006 - With newer versions of MySQL, there is such a 
> thing
> as a connection timeout regardless of activity.  By default under 
> MySQL 5, this
> timeout is 28800 seconds (8 hours).  If your vpopmail system runs 
> fine for the
> first 8 hours, then stops authenticating, this timeout is your 
> problem (especially
> under authdaemond).
> 
> What this code does is when an error is encountered, it first tries 
> to drop and
> rebuild a connection to the SQL server and tries again.  If this 
> second attempt
> fails, then something other than the connection timeout is the 
> problem.  This fix
> need to be implemented in other places but in my setup (Slackware 
> 10.2, netqmail,
> vpopmail, courier-authdaemond, courier-imapd and a few others), this 
> is always where
> the auth attempt died with a "SQL server has gone away" error.
> */
> 
> fprintf(stderr, "Attempting to rebuild connection to SQL server\n");
> vclose();
> verrori = 0;
> if ( (err=vauth_open_read()) != 0 ) {
>   verrori = err;
>   return(NULL);
> }
> if (mysql_query(_read, SqlBufRead)) {
>   fprintf (stderr, "vmysql: connection rebuild failed: %s\n", 
> mysql_error(_read));
>   return(NULL);
> }
> }
> 
> Not sure why mysql (mariadb) would return this error.
> 
> Eric
> 
> 
>> On 11/7/2017 5:47 AM, Eric Broch wrote:
>> That's a good question, Chris. I'll have to delve into the code.
>> 
>> 
>>> On 11/6/2017 9:57 PM, Chris wrote:
>>> Given that the new DB structure for vpopmail involves having a separate 
>>> table for each domain, I thought seeing this in my dovecot.log was a little 
>>> weird:
>>> 
>>> Nov 06 20:53:43 auth-worker: Error: vmysql: sql error[3]: Table 
>>> 'vpopmail.users' doesn't exist
>>> Nov 06 20:53:43 auth-worker: Error: Attempting to rebuild connection to SQL 
>>> server
>>> Nov 06 20:53:43 auth-worker: Error: vmysql: connection rebuild failed: 
>>> Table 'vpopmail.users' doesn't exist
>>> 
>>> Any idea why vmysql is trying to access the users table in the vpopmail db, 
>>> given that it doesn't exist?
>>> 
>>> -Chris
>> 
> 
> -- 
> Eric Broch
> White Horse Technical Consulting (WHTC)
> 
> 
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] qmail - couldn't find any host named grupodecor.com

[Boheme]

I replied with two solutions to this problem on 6/12.

You never replied, so I have no idea whether you tried my suggestions. 

-Sent from my Pip-Boy 3000

> On Jun 20, 2017, at 8:10 PM, Jeff Koch  wrote:
> 
> 
> I'm having trouble sending email to anyone at grupodecor.com. All of my qmail 
> mailservers say:
> 
> Sorry, I couldn't find any host named grupodecor.com. (#5.1.2)
> 
> And yet I can send from my hotmail account and the MX host - 
> grupodecor-com.mail.protection.outlook.com - responds to smtp connections. 
> Try sending an email to anyone at that domain ( like ab...@grupodecor.com ) 
> 
> Anyone know why thisis happening?
> 
> Jeff

Re: [qmailtoaster] Qmail - Can't find host

[Boheme]

Oh, the dreaded outlook.com hosted mail...  I went through this a few days ago. 
 Qmail has an issue with the results bind gives for personal domains hosted at 
outlook.com. I found two solutions that worked:

1) I routed mail for the outlook hosted domain through an instance of 
mailcleaner that I had on my network. 

2) switch local DNA resolution to djbdns using the script at 
https://raw.githubusercontent.com/qmtoaster/scripts/master/chg_dns.sh

Both solutions resulted in successful delivery. I would use option 2 if you 
can, so you don't have to fiddle your delivery rules every time someone sends 
email to a new domain hosted at outlook.com



-Sent from my Pip-Boy 3000

> On Jun 12, 2017, at 4:44 PM, Jeff Koch  wrote:
> 
> This is interesting and maybe I'm overthinking this but on all of my qmail 
> toaster servers (three old Bill's Toaster and one new QMT server) when I try 
> to send an email to this address or any address at the domain grupodecor.com 
> I get:
> 
> :
> Sorry, I couldn't find any host named grupodecor.com. (#5.1.2)
> 
> I can do an nslookup on the mailservers and get the MX record
> 
> nslookup -q=mx grupodecor.com
> 
> Non-authoritative answer:
> grupodecor.com  mail exchanger = 0 grupodecor-com.mail.protection.outlook.com.
> 
> and,
> 
> nslookup grupodecor.com
> 
> Non-authoritative answer:
> Name:   grupodecor.com
> Address: 34.194.244.120
> 
> Can anyone help explain this?
> 
> Thanks, Jeff