Ask Bjørn Hansen (a...@develooper.com)

I think actually it's been reasonably scratched -- the debian package  
for example does it.

The "problem" is that qpsmtpd in many ways is a developer tool and the  
default setup is optimized for that -- and many installs are just  
following that.  I'd like us to move towards doing a "proper" standard- 
ish install as the default.

(For that matter it'd be nice to move the standard plugins towards  
being module based, too, and eventually make the plugins themselves  
easier to subclass/plug/otherwise modify at arms length.).

So: Patches to improve Makefile.PL and a standard install are welcome.


   - ask

On Jan 2, 2009, at 8:49, Robert Spier wrote:

> Can anyone think of any cases where he leading/trailing whitespace in
> config-file might be significant?

They should be quoted, escaped or something else then (which we'd then  
support).


  - ask

On Dec 19, 2008, at 18:56, Matt Sergeant <matt@sergeant.org> wrote:

> Shall we do a release for xmas? It's been forever...

Sounds good to me!  Any reason we can't release what is in git^WSVN  
right now?

You could make a plugin if you have a static mapping from the "clean"  
filenames to the ugly backend ones.  Otherwise the canonical way is to  
have a dynamic backend return a "reproxy" header.

  - ask

Don't enable it if the backend servers are run by another organization/
group/... that you don't trust.  They'll be able to make your perlbal  
access things you might not want them to access.