2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Postfix+Mysql+Maildro...
FromSent OnAttachments
Gatis GailisApr 8, 2003 1:46 am 
Claudio TornadoApr 8, 2003 11:39 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Postfix+Mysql+Maildrop configActions...
From:Gatis Gailis (Gati@verdi.lv)
Date:Apr 8, 2003 1:46:43 am
List:net.sourceforge.lists.courier-maildrop

Hi,

I have been fighting with the same problem for some days, also read that thread with Claudio-Emiliano conversation. My problem now is something around this in maillog: Apr 8 10:55:59 sieta postfix/pipe[89166]: fatal: request to deliver as mail system owner Apr 8 10:56:00 sieta postfix/qmgr[89162]: warning: premature end-of-input from private/maildrop socket while reading input attribute name Apr 8 10:56:00 sieta postfix/master[89160]: warning: process /usr/local/libexec/postfix/pipe pid 89166 exit status 1 Apr 8 10:56:00 sieta postfix/master[89160]: warning: /usr/local/libexec/postfix/pipe: bad command startup -- throttling Apr 8 10:56:00 sieta postfix/qmgr[89162]: warning: private/maildrop socket: malformed response Apr 8 10:56:00 sieta postfix/qmgr[89162]: warning: transport maildrop failure -- see a previous warning/fatal/panic logfile record for the problem description

Claudio - it certainly seems that you have made it through this mess.:) Could you please post detailed config of your maildrop setup; also so that we don't have to ask you the same questions, just look at your setup.

# ____________________________________________________________ # 1. cat /etc/maildrop/maildropmysql.conf

# 2. Your final maildrop ./configure options

# 3. cat /etc/maildrop/maildroprc

# 4. Maildrop binary permissions and owner ls /usr/local/bin/maildrop* maildrop -v

# 5. Postfix # That master.cf line # What exactly you changed in main.cf

# 6. Mysql # It looks from one of your posts that you have entry like this: #transport #intern.de maildrop: # Is the colon actually there after maildrop in your config? Was it there when you had virtual in that field? My config is without it. # ____________________________________________________________

I can execute: echo "Hello" | maildrop -d "not-@mg.lv <mailto:not-@mg.lv> " and I actually get that mail. Sql query looks beautiful: 357 Query SELECT address, uid, gid, maildir, maildir, bool1, bool2 FROM users WHERE address = "not-@mg.lv <mailto:not-@mg.lv> " 357 Quit My maildrop user ir postfix, the same as postfix user. I can successfully execute sudo -u postfix echo "Hello" | maildrop -d "not-@mg.lv <mailto:not-@mg.lv> " and get that mail message. But when I change transport.transport from virtual to maildrop I get that error mentioned at the top of this mail. I can post any info needed.

Thanx for your help,

Gatis