On Fri, November 19, 2021 3:08 am, Jay Hart wrote:
> Fixed the attachment directory write issue by setting setenforce to '0'.
Not a good long-term solution. You can watch the audit log and use ls -Z
to view file/directory contexts. Use tools like audit2allow to help you
figure out what polici
Fixed the attachment directory write issue by setting setenforce to '0'.
Then I got held up on the IMAP server (dovecot) and had to set 'Secure IMAP
(TLS)' setting to 'disabled'.
Does these sound ok? Or, do I have another issue??
Great news is I just logged into my new Squirrelmail setup!!!
J
On Fri, November 19, 2021 2:21 am, Jay Hart wrote:
> I am past this point now. Solved a bit more items. But now stuck on
> writing permissions to the attachment directory
> (/var/spool/squirrelmail/attach/)
Just watch your log file, walk the directory structure to your
data/attachments director
I am past this point now. Solved a bit more items. But now stuck on writing
permissions to the attachment directory
(/var/spool/squirrelmail/attach/)
- main thing I fixed was the squirrelmail conf file in the /etc/httpd
directories.
Jay
> Good Evening,
>
> Problem: Squirrelmail will not run du
Good Evening,
Problem: Squirrelmail will not run due to likely permissions issue on the
server.
I am trying to get Squirrelmail running on a Centos 8 server. I have Centos 8
fully patched and running on stream. Using Apache, dovecot,
SA, and clamav for email. I have all those pieces installed
