Discussion about the maildrop mail delivery agent

Fernando Gozalo | 24 Feb 2012 14:44

maildrop doesn't read /etc/maildroprc

Hi,

I think I'm missing something obvious. I want to use for first time 
/etc/maildroprc. It seems that the file is not used at all.

I have created the file an put a single line in it:

# cat /etc/maildroprc
cc "fgozalo <at> csi.uned.es"

# ls -al /etc/maildroprc
-rw------- 1 cartero cartero 25 feb 24 08:10 /etc/maildroprc

No message delivered to "fgozalo <at> csi.uned.es". The message is delivered 
to the original recipient as if no was /etc/maildroprc. Nothing in the 
logs apart of the normal lines for delivery message in the original 
recipient.

More info:
. maildrop version:  2.5.1

Called from postfix:
. main.cf:
mailbox_transport = maildrop

. master.cf
maildrop  unix  -       n       n       -       -       pipe
   flags=ODRhu user=cartero argv=/usr/bin/maildrop -d ${user} -f ${sender}

¿Any hint?

(Continue reading)

headers

Todd Lyons | 24 Feb 2012 15:50

Re: maildrop doesn't read /etc/maildroprc

On Fri, Feb 24, 2012 at 5:44 AM, Fernando Gozalo <fgozalo <at> csi.uned.es> wrote:
>
> Hi,
>
> I think I'm missing something obvious. I want to use for first time
> /etc/maildroprc. It seems that the file is not used at all.

Double check your man page.  Mine is looking in
/etc/courier/maildroprc.  Maybe it's dependent upon which version
you're running.

> No message delivered to "fgozalo <at> csi.uned.es". The message is delivered
> to the original recipient as if no was /etc/maildroprc. Nothing in the
> logs apart of the normal lines for delivery message in the original
> recipient.
> ¿Any hint?

Run a test mail through it manually, call it test.eml (full email,
with headers, but not with a leading Delivered-To header) :

maildrop -d $localuser -f $remoteuser < test.eml

Look for any output that indicates something is happening that is unexpected.

Regards...            Todd
--
SOPA: Any attempt to [use legal means to] reverse technological advances is
doomed.  --Leo Leporte

------------------------------------------------------------------------------

(Continue reading)

headers

Fernando Gozalo | 27 Feb 2012 12:41

Re: maildrop doesn't read /etc/maildroprc

Hi,

>> ¿Any hint?
>
> Run a test mail through it manually, call it test.eml (full email,
> with headers, but not with a leading Delivered-To header) :
>
> maildrop -d $localuser -f $remoteuser<  test.eml

This was a good hint. I tried with verbose mode and...

# maildrop -V20 -d pru00108 -f fgozalo <at> csi.uned.es < test.eml
maildrop: authlib: groupid=512
maildrop: authlib: userid=512
maildrop: authlib: logname=pru00108, 
home=/home/buzones//interno/p/r/pru00108, 
mail=/home/buzones//interno/p/r/pru00108/Maildir
maildrop: Changing to /home/buzones//interno/p/r/pru00108
Message start at 0 bytes, envelope sender=fgozalo <at> csi.uned.es
Tokenized cc
Tokenized string: "fgozalo <at> csi.uned.es"
Tokenized ;
Tokenized eof
maildrop: Delivering to fgozalo <at> csi.uned.es
maildrop: Flock()ing fgozalo <at> csi.uned.es.
maildrop: Appending to fgozalo <at> csi.uned.es.
maildrop: Delivery complete.
maildrop: Attempting .mailfilter
maildrop: Delivery complete.

(Continue reading)

headers

Sam Varshavchik | 25 Feb 2012 00:41

Re: maildrop doesn't read /etc/maildroprc

Fernando Gozalo writes:

> Hi,
>
> I think I'm missing something obvious. I want to use for first time
> /etc/maildroprc. It seems that the file is not used at all.
>
> I have created the file an put a single line in it:
>
> # cat /etc/maildroprc
> cc "fgozalo <at> csi.uned.es"
>
> # ls -al /etc/maildroprc
> -rw------- 1 cartero cartero 25 feb 24 08:10 /etc/maildroprc
>
> No message delivered to "fgozalo <at> csi.uned.es". The message is delivered
> to the original recipient as if no was /etc/maildroprc. Nothing in the
> logs apart of the normal lines for delivery message in the original
> recipient.

Let's try eliminating the low hanging fruit.

Although, by default, the global config file is /etc/maildroprc, this can be  
overridden when maildrop gets built.

Check the build configuration for the maildrop package that you are using.

Then check your mail logs. Its entirely possible that the CC cannot be  
delivered, for some reason.

(Continue reading)