Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Lucio Crusca
Markus Wanner writes: > Is this the Debian stretch installation mentioned? > Yes it is. > I'm successfully running a courier installation on Debian stretch with > maildrop compiled manually, ATM. Thanks for sharing, I'm afraid that's what I need to do too. What does exactly mean to compile

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Markus Wanner
On 14.05.2017 20:16, Lucio Crusca wrote: > However if I try to use maildrop alone, with: > > DEFAULTDELIVERY="| /usr/bin/maildrop" > > it stops working again, so I think I have a problem with maildrop rather > than spamd. Is this the Debian stretch installation mentioned? You might have run

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Sam Varshavchik
Lucio Crusca writes: Sam Varshavchik writes: > From the logs, you've configured spamd to be responsible for delivering > mail > > You have to take smaller steps, and get one thing working, at a time. I've now moved spamd out of the way. My previous DEFAULTDELIVERY was

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Lucio Crusca
Sam Varshavchik writes: > From the logs, you've configured spamd to be responsible for delivering > mail > > You have to take smaller steps, and get one thing working, at a time. I've now moved spamd out of the way. My previous DEFAULTDELIVERY was

Re: [courier-users] Message delivered, but no message in INBOX

2017-05-14 Thread Sam Varshavchik
Lucio Crusca writes: E.g. no files written into the Maildir, despite the "Message delivered" log. I've also tried to access the Maildir with Thunderbird and RoundCube and they both confirm there aren't any messages. I have no clue about what I should check... please help. From the logs,