2015-05-23 21:42 GMT+03:00 Gordon Messmer <gordon.mess...@gmail.com>:
> On 05/23/2015 09:25 AM, Alexey Mishustin wrote:
>> /etc/courier/maildroprc
> ...
>
> You should have an exception block around that in case someone deletes
> their Spam folder. Probably shouldn't have multiple users logging to
> the same file either. DEFAULT should already be $HOME/Maildir, so
> there's no reason to set it.
>
> logfile ".maildrop.log"
> xfilter "/usr/bin/spamc"
> exception {
> if(/^X-Spam-Status: Yes/)
> {
> to ./Maildir/.Spam/.
> }
> }
Fixed...
>> But when maildrop is called from courier, it behaves as if there is no
>> configuration files at all (maildroprc not being read): messages go
>> always to Maildir; no echoes, no new lines in var/log/maildrop.log.
>>
>> What could I have missed?
>
> My guess is that your user has a .courier file, so DEFAULTDELIVERY isn't
> being used. In that case, maildrop probably isn't called from courier
> at all.
Really! I had created a .courier file for forwarding. After deleting
it maildrop is working as intented.
Thank you very much, Gordon!
What is the best way to combine maildrop delivery with forwarding (to
an external e-mail)? cc?
--
Regards,
Alex
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
