It has been killing me too! The basic issue I have is that as soon as I
change my .qmail-default to use maildrop it returns the following error:

@4000000042bdac521ae5d764 new msg 1109815
@4000000042bdac521ae5e704 info msg 1109815: bytes 1568 from
<[EMAIL PROTECTED]>
qp 2638 uid 210
@4000000042bdac521d5d0954 starting delivery 4890: msg 1109815 to local
hippotje.
[EMAIL PROTECTED]
@4000000042bdac521d5dfb84 status: local 1/10 remote 0/20
@4000000042bdac522a5dbdc4 delivery 4890: deferral:
maildrop:_error_writing_to_ma
ilbox.//usr/bin/maildrop:_Unable_to_deliver_to_mailbox./

All I can think of is permissions. But i have checked them all.

xen2 root # maildrop -vp
maildrop 1.8.0 Copyright 1998-2004 Double Precision, Inc.
GDBM extensions enabled.
Courier Authentication Library extension enabled.
Maildir quota extension enabled.
This program is distributed under the terms of the GNU General Public
License. See COPYING for additional information.
xen2 root #



> Man, I don't know, maildrop is pretty cut and dry. The compile options are
> proper, what is the specific issue that you're having, basically give me a
> scenario error messages, logs. Also paste the output from emerge
> maildrop -vp.
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <vchkpw@inter7.com>
> Sent: Wednesday, June 29, 2005 2:07 PM
> Subject: Re: [vchkpw] Problems with qmail/vpopmail/maildop
>
>
>> Hi,
>>
>> I complied maildrop from the ebuild. Nothing has been compliled from raw
>> source. I have opened up the ebuild and checked the compile options.
>> They
>> are as follows:
>>
>> ./configure
>>     --prefix=/usr
>>     --host=i686-pc-linux-gnu
>>     --mandir=/usr/share/man
>>     --infodir=/usr/share/info
>>     --datadir=/usr/share
>>     --sysconfdir=/etc
>>     --localstatedir=/var/lib
>>     --with-devel
>>     --disable-tempdir
>>     --enable-syslog=1
>>     --enable-use-flock=1
>>     --enable-maildirquota
>>     --enable-use-dotlock=1
>>     --enable-restrict-trusted=1
>>     --enable-trusted-users=apache dspam root mail daemon postmaster
>> qmaild
>> mmdf vmail
>>     --enable-maildrop-uid=root
>>     --enable-maildrop-gid=mail
>>     --with-default-maildrop=./.maildir/
>>     --enable-sendmail=/usr/sbin/sendmail
>>     --cache-file=/var/tmp/portage/maildrop-1.8.0-r3/work/maildrop-1.8.0/co
> nfiguring.cache
>>      --with-db=gdbm
>>
>>
>> > The first question that comes to mind is, did you compile maildrop
>> from
>> > src
>> > or did you let portage to it for you? the guide you mentioned uses
>> > ebuilds,
>> > ebuilds that replace Maildir with .maildir in the source of courier,
>> > vpopmail, and qmail. Maildrop from source might not know about this
>> > change.
>> > ----- Original Message -----
>> > From: <[EMAIL PROTECTED]>
>> > To: <vchkpw@inter7.com>
>> > Sent: Wednesday, June 29, 2005 1:41 PM
>> > Subject: [vchkpw] Problems with qmail/vpopmail/maildop
>> >
>> >
>> >> Hi,
>> >>
>> >> I am having problems trying to get maildrop working in my mail
>> server.
>> >> Have been using this configuration on a Redhat box for over a year
>> and
>> >> recently moved to a Gentoo solution. Getting maildrop to work is the
>> >> only
>> >> part that is failing.
>> >>
>> >> To build the server, I have used the following gentoo documentation:
>> >> http://www.gentoo.org/doc/en/qmail-howto.xml
>> >>
>> >> Everything is running well but I get permission problems when I try
>> to
>> >> introduce maildrop. I am getting the following errors in the
>> qmail-send
>> >> logs:
>> >>
>> >> @4000000042bdac521ae5d764 new msg 1109815
>> >> @4000000042bdac521ae5e704 info msg 1109815: bytes 1568 from
>> >> <[EMAIL PROTECTED]> qp 2638 uid 210
>> >> @4000000042bdac521d5d0954 starting delivery 4890: msg 1109815 to
>> local
>> >> [EMAIL PROTECTED]
>> >> @4000000042bdac521d5dfb84 status: local 1/10 remote 0/20
>> >> @4000000042bdac522a5dbdc4 delivery 4890: deferral:
>> >>
>> >
> maildrop:_error_writing_to_mailbox.//usr/bin/maildrop:_Unable_to_deliver_to_
>> > mailbox./
>> >> @4000000042bdac522a5dcd64 status: local 0/10 remote 0/20
>> >>
>> >> I have checked the permissions of all the maildrop related files and
> the
>> >> maildir:
>> >>
>> >> xen2 qmail-send # ls -la /usr/bin/maildrop
>> >> -rwxr-x---  1 vpopmail mail 166816 May 18 19:25 /usr/bin/maildrop
>> >> xen2 qmail-send # ls -la /etc/maildrop/mailfilter
>> >> -rw-------  1 vpopmail vpopmail 545 May 18 20:28
>> >> /etc/maildrop/mailfilter
>> >>
>> >> This is my .qmail-default and corresponding mailfilter.
>> >>
>> >> xen2 qmail-send # cat
>> /var/vpopmail/domains/hippotje.com/.qmail-default
>> >> |
>> >
>> >> /usr/bin/maildrop /etc/maildrop/mailfilter
>> >>
>> >> xen2 qmail-send # cat /etc/maildrop/mailfilter
>> >> import EXT
>> >> import HOST
>> >> import HOME
>> >> MAX = 15
>> >> VHOME=`/var/vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
>> >> VPOP="| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox"
>> >> JUNKFOLDER=".Spam"
>> >> if ($VHOME)
>> >> {
>> >>    `test -d "$VHOME/.maildir/$JUNKFOLDER"`
>> >>    if( $RETURNCODE != 1 )
>> >>    {
>> >>       if ( $SIZE < 262144 )
>> >>       {
>> >>          exception {
>> >>             xfilter "/usr/bin/spamc -f -u [EMAIL PROTECTED]"
>> >>          }
>> >>       }
>> >>    }
>> >>    if (/^X-Spam-Flag: *YES/)
>> >>    {
>> >>       to "$VHOME/.maildir/$JUNKFOLDER/"
>> >>    }
>> >>    else
>> >>    {
>> >>       to "$VHOME/.maildir/"
>> >>    }
>> >> }
>> >> else
>> >> {
>> >>    to $VPOP
>> >> }
>> >>
>> >> And finally -v output from maildrop.
>> >>
>> >> xen2 root # maildrop -v
>> >> maildrop 1.8.0 Copyright 1998-2004 Double Precision, Inc.
>> >> GDBM extensions enabled.
>> >> Courier Authentication Library extension enabled.
>> >> Maildir quota extension enabled.
>> >> This program is distributed under the terms of the GNU General Public
>> >> License. See COPYING for additional information.
>> >> xen2 root #
>> >>
>> >> Does anybody have any advice? This is the key to my complete mail
>> >> server!!
>> >> I don't know if this is maildrop or vpopmail or qmail causing me the
>> >> issue.
>> >>
>> >> Kind regards,
>> >>
>> >> Dougal
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
>


Reply via email to