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

On 05/18/2017 12:35 PM, Sam Varshavchik wrote: > Fairly unambiguous. This part of the version string is only present in > the courier-specific maildrop build. Cool, thanks. Markus signature.asc Description: OpenPGP digital signature

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

Hi, On 05/19/2017 02:53 AM, Ángel wrote: > On 2017-05-18 at 19:03 +0200, Alessandro Vesely wrote: >> Although the real issue is maildrop, let me note the following about >> courier-base: >> >> * couriertcpd could be just suggested or recommended, not required, as Sam mentioned, the current

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

On 2017-05-18 at 19:03 +0200, Alessandro Vesely wrote: > Although the real issue is maildrop, let me note the following about > courier-base: > > * couriertcpd could be just suggested or recommended, not required, > > * testmxlookup could be moved to courier-mta, > > * I don't see how maildir

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

Alessandro Vesely writes: Although the real issue is maildrop, let me note the following about courier- base: * couriertcpd could be just suggested or recommended, not required, It most certainly is required. The default startup script require it. I suppose you could customize the package

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

Idézem/Quoting Alessandro Vesely : > On Thu 18/May/2017 00:19:07 +0200 Markus Wanner wrote: >> On 17.05.2017 09:48, Alessandro Vesely wrote: >> >>> My suggestion is to avoid disassembling the Courier tarball. That is, have >>> maildrop included by default in courier-mta, and

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

On Thu 18/May/2017 00:19:07 +0200 Markus Wanner wrote: > On 17.05.2017 09:48, Alessandro Vesely wrote: > >> My suggestion is to avoid disassembling the Courier tarball. That is, have >> maildrop included by default in courier-mta, and possibly merge it with >> courier-base as well (why were they

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

Markus Wanner writes: > The > differences are in the configuration. The biggest difference is > maildrop, because it ties in directly into mail delivery, and it has > Courier-specific features, and Courier has maildrop-specific features as > well. Understood. (If you're provided a maildrop

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

Sam, On 05/18/2017 12:29 AM, Sam Varshavchik wrote: > When I refer to source releases, I always refer to > http://www.courier-mta.org/download.html Thanks for clarifying, that's usually referred to as upstream in Debian, whereas "the package" is the result of packaging for Debian. Please excuse

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

Markus Wanner writes: Hi, On 17.05.2017 02:44, Sam Varshavchik wrote: > Only one maildrop package is needed. And one courier package, that's it. Unfortunately, there is not separate courier-mta source release. Only When I refer to source releases, I always refer to http://www.courier-

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

Hi, On 17.05.2017 09:48, Alessandro Vesely wrote: > I'd suggest to avoid that. I'd love not having to reintroduce a second maildrop variant. > I use subjunctive because I install Courier from > tarballs rather than Debian packages, except for off-hand tests. In the > latter > case, I get

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

Hi, On 17.05.2017 02:44, Sam Varshavchik wrote: > Only one maildrop package is needed. And one courier package, that's it. Unfortunately, there is not separate courier-mta source release. Only the bundle. That's problematic for distributions per se. That's not a Debian specific issue, but

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

On Tue 16/May/2017 19:06:55 +0200 Markus Wanner wrote: > > I'll check if it's feasible to re-add the courier-maildrop package in > Debian stretch (i.e. the Courier specific variant) I'd suggest to avoid that. I use subjunctive because I install Courier from tarballs rather than Debian packages,

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:

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

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

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

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

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

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,

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

Hello, I'm still configuring the new server. The 456 error is resolved, thanks, but now I have a new problem. Looking at log files, it seems local delivery is ok. Here is an example of my logs for a test message from GMail to i...@usosalix.com: May 14 01:05:57 maxwell courieresmtpd: