I run through the document and have some suggestion/fix to give: In the step : chown -R spamtrap:mailusers /home/spamtrap/.maildir the group mailusers has not been yet created, and even if you create it, when you access spamtrap with squirrelmail, it expect the maildir directory to have the couurect uid/gid. I think, and locally did, that is better to add spamtrap to the group mailusers instead In the Installing revised smtpclient we can use the mail-client/smtpclient-1.0.1 that already seems to have an option to process the headers. The option seems to be -w instead of -F so even the deliver.pl should be changed. Reproducible: Always
(In reply to comment #0) > I run through the document and have some suggestion/fix to give: > > In the step : > chown -R spamtrap:mailusers /home/spamtrap/.maildir > > the group mailusers has not been yet created, and even if you create it, when > you access spamtrap with squirrelmail, it expect the maildir directory to have > the couurect uid/gid. > I think, and locally did, that is better to add spamtrap to the group mailusers > instead What are the steps?
(In reply to comment #1) > What are the steps? 6. Autolearning and sidelining emails -> Creating the spamtrap user
(In reply to comment #2) > (In reply to comment #1) > > What are the steps? > 6. Autolearning and sidelining emails -> Creating the spamtrap user I meant, can you please write down the instructions and where they should go. I'm not familiar with spamtrap, so none of what you said makes any sense, sorry.
(In reply to comment #3) chown -R spamtrap:mailusers /home/spamtrap/.maildir must become chown -R spamtrap:spamtrap /home/spamtrap/.maildir That should work to fix my first point The other point, I think you already fix it
(In reply to comment #4) > (In reply to comment #3) > chown -R spamtrap:mailusers /home/spamtrap/.maildir > > must become > > chown -R spamtrap:spamtrap /home/spamtrap/.maildir > > > That should work to fix my first point Thanks for clarifying. Fixed in CVS.
