Maybe a mass conversion script would be worth including with qmailadmin
(in contrib/ or something) that finds old-style aliases and turns them
into forwards? Maybe something that runs along the lines of "a2fconvert
domain.com" that would then lookup domain.com's base directory, do a grep
for Maildir in .qmail*, then take the last string after "Maildir/" and
assume that to be "[EMAIL PROTECTED]" and replace the contents with
"&[EMAIL PROTECTED]", overwriting the existing .qmail* file.
Does this seem like a good idea?
> Well done Tom for organising the recent releases of qmailadmin!
>
> I have cranked up 1.0.21 on my server and would like to provide some
> feedback :
>
> ISSUE 1:
> When you add a new forward, the wording that is displayed apon completion
> is
> pretty contorted. eg :
>
> "Alias for Email Account added successfully testme2
> [EMAIL PROTECTED]"
>
> It shouldn't say "alias" since you are ditching this concept and are now
> creating
> everything as forwards. Can I suggest it gets altered to simply be token
> 152
> ("Forward Added Successfully"). I looked through the dictionary file, and
> couldn't see any better way to write it without going to the hassle of
> adding
> extra tokens.
>
> I have attached a patch so you can see my suggestion. The patch also
> renames the a couple of the columns in the various forwards menus.
> Take a look and see if you think the patch is worth incorporating or not.
>
> ISSUE 2:
> I think there is going to be some confusion for domain postmasters when
> they go to the new v1.0.21's "forwards" menu.
>
> If the domain already has some aliases setup, then the information
> displayed
> on this screen is going to be a bit inconsistent.
>
> For example one of the reasons for ditching aliases was to avoid having
> mail copied directly to users maildirs. Now if you go in via v1.0.21 and
> add
> a few forwards for local recipients, you wont be able to tell it apart
> from existing entries that are using old alias style delivery. If you are
> trying
> to setup some fancy per-user stuff like spamassassin, then you are going
> to
> get
> inconsistent results because some local users will be getting the old
> alias
> delivery and some will be getting the new forward delivery.
>
> Same deal with the count displayed at the top of the screen. The
> count will be inconsistent if you have existing alias delivery local
> users.
>
> I think the best solution would be to convert any existing alias
> deliveries over to be forward deliveries. That would allow all the
> delivery and limit stuff to remain consistent.
>
> For sites with a lot of domains/users it really wouldn't be suitable to
> have to make these changes by hand. I reckon what we need is
> some sort of script that can scan the vpopmail/domains tree and
> converts any aliases over to be forwards....
>
> I hope you find my feedback to be of use!
>
> Michael
>
--
Benjamin Tomhave, Senior Systems Engineer
[EMAIL PROTECTED]
Sofast Communications www.sofast.net
