[qmailadmin-devel] alias2forward.pl, other notes on upgrading

[Tom C. <to...@to...>]

I have 'alias2forward.pl' working (80 lines), and just need to add a 
few prompts to it (prompt for qmail path if it isn't /var/qmail, prompt 
for whether it should do a dry-run and show what will happen, or just 
go for it).

It turned out to be a little tricky, because it has to work with hashed 
domains (e.g., ~vpopmail/domains/0/test.com).  It ignores alias domains 
where it's already processed the "real domain".  I also included code 
to ignore symbolic links (ezmlm files).  It could probably be done with 
a shell script, but I lack the mad shell skillz to do it.

It only rewrites the file if it made changes.  It only changes lines 
that start with /, and end with /Maildir (with an optional trailing /). 
  I ran into some files on my system (ezmlm list owner aliases) that 
didn't have the trailing slash, and worried that there might be some 
other instances where it's missing, so I made it optional.

Since it overwrites the old file with the new information (again, only 
if there were changes), the permissions remain unchanged.  I'll put it 
online, or post it to the list for others to test on development 
servers, and it will be included with the 1.0.25 release, along with 
notes in the CHANGELOG, README and UPGRADING files.

If anyone wants to take the plunge and start writing a document that 
will help vpopmail 5.2.1/qmailadmin 1.0.6 admins upgrade to the 
vpopmail 5.4/qmailadmin 1.2 release, I'd appreciate it.  You would have 
to review the Changelogs, summarize architectural changes that would 
affect them, and introduce some of the new features (like valiases, the 
new vlimits code, current state of SpamAssassin integration, new 
configure options, etc.).

--
Tom Collins
to...@to...
http://sniffter.com/ - info on the Sniffter hand-held Network Tester