Re: error writing to filter (bogofilter)

Christian Ebert writes:

> * Sam Varshavchik on Saturday, June 15, 2013 at 19:08:06 -0400
> > Christian Ebert writes:
> >> * Sam Varshavchik on Saturday, June 15, 2013 at 16:55:04 -0400
> >>> I'll just guess that bogofilter does not decode base64-encoded content
> >>> on the fly, but tries to save them in a temporary file, and then reads
> >>> it back; and the temporary files locations are specified by
> >>> environment variables; which should be defined, but are not; or even
> >>> the other way around; bogofilter reads some environment variable
> >>> that's not normally defined, and then uses some fallback setting, but
> >>> this environment variable is set here, and bogofilter tries to use it.
> >>
> >> But then it would fail on its own or via procmail, wouldn't it?
> >
> > If the conditions would be the same, as I described previously.
>
> Here the conditions looks pretty much the same:
>
> $ maildrop < testbogomsg
> maildrop: error writing to filter.
> maildrop: Unable to filter message.
> $ procmail < testbogomsg
> [ is delivered with bogofilter adding its header ]

I already explained how conditions are not the same, namely the environment  
variables that are set or cleared, by maildrop, for started processes. As I  
wrote before, see "Environment" in the maildropfilter man page, and  
replicate how bogofilter gets invoked, by setting or clearing the same  
environment variables, and piping the message to its standard input.

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

_______________________________________________
Courier-maildrop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/courier-maildrop

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iEYEABECAAYFAlG9A18ACgkQx9p3GYHlUOJNcgCeM1JzJQptANpivEJROlBQ7ads
SLgAni2a5pPa7I32yaZ+38tWCY0GAgwG
=/CKD
-----END PGP SIGNATURE-----