Re: [maildropl] signal 0x06

[Rolan Y. <ro...@om...>]

Maildrop, running as the "dspam user", likely does not have permission 
to write to the maildir. The permissions on your maildir are probably 
writable by the user or a generic "postfix" user. Try either running 
dspam as "postfix" or changing the execute permissions on maildrop suid 
root. If you want to test this out before making any changes, "chmod a+w 
-R" one of your users' maildirs, then try sending them an email. If it 
goes through without error, the permissions are your problem.

~Rolan

Kyle Johnson wrote:
> Hi everyone.
> This problem is pulling my hair out, and I've run out of ideas.
> I run a postfix mail server.  For normal mail, the flow is as follows:
> internet -> postfix -> virtual_transport -> dspam -> maildrop -> maildir
> This is okay, and it works great.
>
> The problem is this:
> When dspam catches a spam, it quarantines it.  You can log into the 
> WebUI and deliver a quarantined message, which delivers via maildrop, 
> with a command similar to:
> /cat file | maildrop -d us...@do...d
> /This fails with the error:/
> maildrop: signal 0x06/
>
> dspam runs as user:group dspam:dspam.  From the webui, I am using 
> suexec, which runs as dspam:dspam.
>
> maildrop seems to run as whatever user is calling it, so in either 
> case, it is dspam which maildrop is running as.
>
> If I:
> /su dspam
> cat file | maildrop -d us...@do...d/
> I still get the same error (maildrop: signal 0x06)
>
> What I do not understand is why things work when in the postfix-flow, 
> but not when being called from the webui or manually from the command 
> line.
>
> Any ideas?
>
> Thank you!
> -- 
>
> Kyle Johnson
> <http://www.fixertec.net/>
>