>> On 19.07.11 19:53, Alessandro Vesely wrote: >>>Yes, _was_ until version 57.1, announced on 14 October 2007 (The line >>>saying "Invoke Courier filters after closing all control files.")
Perfect, I mentioned this in drweb bugreport. >On 21/Jul/11 14:28, Matus UHLAR - fantomas wrote: >> Is there any recommended way to alter the data file? >> (e.g. create new D* in tmp, move it to msgs/ ?) On 21.07.11 19:44, Alessandro Vesely wrote: >I didn't find any. The file is already in some tmp, so I concatenate >the filter name and its (forked) process id to the data filename, e.g. >/var/courier/localstatedir/tmp/131126/D6144051zdkimfilter2766 >After rewriting, I rename (mv) such name to the original data >filename. Should errors occur, I'd try and delete the rewritten file >(never happened.) Does courier do an autoclean if the filter fails? Or is the filter expected to be so robust that it's not needed? >> It currently seems to cause courier to drop the mail (hmm, how?) > >The practice used to consist in marking all recipients as delivered, >so that courier won't act on the message. This seems to be what drweb-courier does. >> and pipe modified mail to sendmail. I'd be satisfied if it said courier >> to just accept the mail "200 Ok" but current drweb-courier seems to lack >> this functionality now. >Without sources, you had better have it done by the upstream >developer. As a workaround, you could insert a wrap-filter that calls >drweb-courier rather than having it called by courier directly. The >wrapper could pass a dummy control file to drweb, and thus control the >destiny of a message. You'd need a dummy sendmail as well... Is that >worth? I don't think it's worth it. Imho it's better to ask drweb to change drweb-courier to behave more nicely... Currently I have other problem: Jul 26 19:00:59 w05 drweb-sender.real: [47819500582672] sender INFO absT3gOH6/000000000005866C.000000004E2EF038.000072A2 get msg [from: <[email protected]>; to:<[email protected]>] from queue for processing... Jul 26 19:00:59 w05 submit: Permission denied Jul 26 19:00:59 w05 submit: Failed to connect to: /var/lib/courier/allfilters/drweb-courier Jul 26 19:00:59 w05 drweb-sender.real: [47819500582672] sender.pipe WARN absT3gOH6/000000000005866C.000000004E2EF038.000072A2 normal termination, exit status = 75; was error (pid=29789) It seems that sendmail is unable from some reason to connect to /var/lib/courier/allfilters/drweb-courier, I have tried to find out why... -r-s--x--x 1 root mail 1093472 Jul 11 16:28 /usr/bin/sendmail.courier -rws--s--x 1 mail drweb 618824 May 23 16:46 /usr/lib/courier/filters/drweb-courier -rwxr-x--- 1 mail mail 128 Jul 26 19:12 /usr/lib64/courier/courier/submit drwxr-xr-x 2 mail mail 4096 Jul 26 18:32 /var/lib/courier/allfilters/ srw-rw---- 1 mail drweb 0 Jul 26 18:32 /var/lib/courier/allfilters/drweb-courier I replaced submit by a script that logs the file and 'id -a output' this is the original one: uid=8(mail) gid=12(mail) groups=12(mail) -src=smtp -rfc3848=ESMTP esmtp dns; fantomas.fantomas.sk (fantomas.fantomas.sk [195.168.3.66]) IDENT: uhlar and this when drweb-courier calls it: uid=100(drweb) gid=12(mail) groups=3004(drweb),0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy),20(dialout),26(tape),27(video) local dns; localhost (localhost [127.0.0.1]) uid 100 How does submit process connect to courierfilter? > Why doesn't drweb at least publish an API? I can only guess here, but they seem to do all the stuff for themselves. They created maild just to provide more functionality than formerly (drweb-courier version 4.* worked as I wanted, it's unsupported for about a month). -- Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 42.7 percent of all statistics are made up on the spot. ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
