On Fri, Aug 25, 2000 at 09:53:44AM -0500, Ken Jones wrote:
> > I'm not sure if I have screwed something up or if this is a legitimate
> > bug:
> >
> > When I delete a pop account and choose the option to add a forward for
> > that account, I get an Internal Server Error. Going to the "Forwards"
> > menu does not show the new forward, but the pop account was deleted. If
> > I then try to add a new forward with that name, it says "name already in
> > use". Actually viewing that domain's directory shows a zero-byte .qmail
> > file for that user. Delete that and everything is peachy again.
>
> Hmm. I don't get the internal server error. Might be the changes I
> made to 0.36. I dunno.
I'm still getting the same error with 0.37. It reaches the point
where it creates the .qmail-user file but it breaks before it can
actually write out the forwarding address to the file, leaving me with
an empty .qmail-user file.
FWIW, qmailadmin is running on a pair of load-balanced Solaris 2.7
boxes, mounting up the ~vpopmail/ tree off a NetApp filer that is also
mounted by the mail server.
> > As a side point, the inability to add forwards for existing pop accounts
> > is proving to be a problem for us. Specifically, we need to be able to
> > add forwards for the postmaster accounts. Almost all of our virtual
> > domains forward the postmaster mail elsewhere, and with v0.35, tech
> > support is bringing all of those to me to set up.
>
> Yep yep. Changed ;]
Damn spiffy. Now, one last request in this vein: I can add a forward
for the postmaster account, but if I make it the catch-all it delivers
it directly to the maildir rather than noticing that it should be
forwarded. Would there be any way to allow remote addresses (or local
forwards, I suppose) to be selected to be the catch-all? I'm
configuring 'em that way by hand now by editing the .qmail-default.
Ben
--
Ben Beuchler [EMAIL PROTECTED]
MAILER-DAEMON (612) 321-9290 x101
Bitstream Underground www.bitstream.net
