Hi Eric,

OK. That seems to have worked everything out. All the pieces and parts seem to 
be running. Now I just have to port in all of my details from my backups.

‘just’. :)

Thank you, Eric,
Roxanne


On Jul 26, 2016, at 12:30 AM, Eric <[email protected]> wrote:

Hi Roxanne,

It looks like I should make some changes to the install script. Thanks for the 
heads up.

ClamAV starts differently now (99.2) I'll get that updated in the install 
script.

ClamAV starts using the following:

systemctl start clamav-daemon.service
systemctl enable clamav-daemon.service
systemctl start clamav-daemon.socket
systemctl enable clamav-daemon.socket

I'd uninstall and reinstall vpopmail and qmail with fresh download.

uninstall:
rpm -e --nodeps vpopmail qmail

download vpopmail and qmail

install:
rpm -ivh vpopmail
rpm -ivh qmail

Then run 'toaststat' and the command line.


Eric


On 7/25/2016 9:21 PM, Roxanne Sandesara wrote:
> I am in the process of building a new CentOS 7 toaster and trying to port in 
> backup materials from an old CentOS 5 toaster. Through a bit of back and 
> forth, I’ve managed to get most things installed. I have two niggling 
> problems remaining that I need to tackle, and I am suspecting that they are 
> related.
> 
> Going through the script recorded files of my installations, I noticed that I 
> get the errors:
> 
> warning: user vpopmail does not exist - using root
> warning: group vchkpw does not exist - using root
> warning: user vpopmail does not exist - using root
> warning: group vchkpw does not exist - using root
> 
> I had to go back a couple of times to get some of the packages to install, 
> and I suspect that’s where this crept in. As near as I can tell, everything 
> is now installed. But obviously I think I need to create the vpopmail user 
> and the vchkpw group.
> 
> When the script finishes up, I get the following:
> 
> Starting qmail-toaster: svscan.
> send: unable to open supervise/ok: file does not exist
> smtp: unable to open supervise/ok: file does not exist
> submission: unable to open supervise/ok: file does not exist
> send/log: unable to open supervise/ok: file does not exist
> smtp/log: unable to open supervise/ok: file does not exist
> submission/log: unable to open supervise/ok: file does not exist
> id: vpopmail: no such user
> id: vpopmail: no such user
> id: vpopmail: no such user
> id: vpopmail: no such user
> SysV service         clamd:    [  FAILED  ]
> SysV service         spamd:    [  OK  ]
> SysV service       network:    [  OK  ]
> Systemd service    dovecot:    [  OK  ]
> Systemd service      httpd:    [  OK  ]
> Systemd service      acpid:    [  OK  ]
> Systemd service        atd:    [  OK  ]
> Systemd service     autofs:    [  OK  ]
> Systemd service      crond:    [  OK  ]
> Systemd service       ntpd:    [  OK  ]
> Systemd service     smartd:    [  OK  ]
> Systemd service       sshd:    [  OK  ]
> Systemd service irqbalance:    [  OK  ]
> Systemd service      named:    [  OK  ]
> Systemd service     vsftpd:    [  OK  ]
> 
> 
> My questions:
> 1) I know I can just issue useradd vpopmail; but what other details do I need 
> there? Should I set a password? Or not? What groups should it be a member of? 
> I suspect I should force it to take GID 89, but if I’m wrong, let me know 
> that too.
> 2) I assume I can groupadd vchkpw. What user(s) should go in that group? 
> Should I force it to a particular ID?
> 3) Would the vpopmail user/vchkpw group errors cause the failures for the 
> qmail services? Will fixing them fix that?
> 
> Obviously I want to get this right. Any help or advice would be appreciated.
> 
> 
> ---------------------------------------------------------------------
> 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]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to