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

Idézem/Quoting Sam Varshavchik : > Markus Wanner writes: > >> I don't quite see how that matters. It's the same set of source files, >> which would need the same set of security fixes, for example. What does >> the duplication of efforts buy us? >> >> I'd rather state that

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

Markus Wanner writes: I don't quite see how that matters. It's the same set of source files, which would need the same set of security fixes, for example. What does the duplication of efforts buy us? I'd rather state that duplication of code is never a good idea, but a sign for bad

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

On 05/16/2017 05:10 PM, Sam Varshavchik wrote: > They should not be. maildrop is a separate source package. It's a > tarball in of itself, that's built independently. > > Now, the fact that this tarball contains code that's also found in > another, larger, package, that's a different subject. I

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

Markus Wanner writes: I'd quickly like to elaborate on why the former Debian maintainer decided to do that and hope for your understanding: Before, there was a courier-maildrop as well as a (stand-alone) maildrop package. Meaning those two are built from the very same source, but They should

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

Hi, On 05/16/2017 02:27 PM, Sam Varshavchik wrote: > This has been discussed already – that package replaces the maildrop > component with the standalone version of maildrop. This doesn't work > correctly, or rather it won't work without some additional > configuration. I'd quickly like to

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

Idézem/Quoting Sam Varshavchik : > Lucio Crusca writes: > >> but the maildrop manpage reports: >> >> "-V is ignored when maildrop runs in delivery mode." >> >> and maildropfilter manpage reports the same about the VERBOSE variable. > > Then run maildrop manually, yourself.

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

It now works: Markus kindly sent me his patch and his custom maildrop 2.8.4 deb package, because he's currently short of time to keep up with the conversation here. I tried to apply his patch to maildrop 2.8.5 sources. The patch gets applied, but configuration fails afterwards for some reason

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

Lucio Crusca writes: but the maildrop manpage reports: "-V is ignored when maildrop runs in delivery mode." and maildropfilter manpage reports the same about the VERBOSE variable. Then run maildrop manually, yourself. Run maildrop with -V from the shell, pipe a test message on standard

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

I wrote: > Is it enough to edit that line, make it look like > #ifndef HAVE_COURIER >#define HAVE_COURIER > #endif > > and configure/make/install? I answer myself: no it isn't, because I've tried and that leads to a compile error. Then I've also tried just commenting out the #undef,

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

I wrote: > What does exactly mean to compile maildrop with HAVE_COURIER? I coulnd't find > any > such option in ./configure and the generated Makefile does not include > it either. I've had a look at the current maildrop stable sources (2.8.5). In the file libs/maildrop/config.h.in I see: