On Wed, 22 May 2002, Brandon Wittenburg wrote:
>
> >
> > have just upgraded my XMail server for the first time, and found some
> > strange things during the process.
> > Is there any one out there that have a best practice about how to upgrade
> > XMail on Linux (RH 7.2)?
> >
> > Anyway, What I did was to stop XMail, renamed /var/MailRoot ->
> > /var/Mailroot.1.6 (Yes I skipped 1.7)
> > Installed 1.8 from the prebuilt RPM (had to do it with the --force
> option),
> > I copied the .tab files from /var/MailRoot.1.6 to /var/MailRoot.1.8 (A
> small
> > change in server.tab was kept from the 1.8 server.tab)
> > I also copied the domains and spool directories (after having removed the
> > existing ones).
> >
> > XMail then started without any problems and I was able to send outgoing
> > mail, but incomming mail did not work.
> > Testing resulted in an "failure delviery" with the following information
> >
> > ---snip---
> > Unable to deliver message to the following address(es).
> > <[EMAIL PROTECTED]>:
> > 217.215.11.128 does not like recipient.
> > Remote host said: 550 Relay denied
> > Giving up on 217.215.11.128.
> > ---snip---
> >
> > It wasn't until I deleted another (testing)domain and enabled it again,
> the
> > incomming mail started to work.
> > It works fine now.
> > Any ideas why this happend,
> > and any ideas on how to upgrade the next time.
> >
> > Hans Birgander
> >
> > Btw. Thanx for an outstanding dedication to the program Davide.
> >
> >
> >
> >
>
> You should not have to move your mailroot (making a backup would be good
> though) when you upgrade with the rpm. just do a # rpm -Uhv
> xmailxxx.i386.rpm. From 1.6 to 1.8 you should only have to re-enter your
> command line values if you had messed with them before. All of your users
> and domains should be kept intact.
indeed. XMail's .rpm does not try to overwrite an existing $MAIL_ROOT :
%post
if [ ! -f /var/MailRoot/server.tab ]
then
cp -R /var/MailRoot.sample/* /var/MailRoot
fi
>
> Also, what did you need the --force flag for? I have done many setups using
> the rpm on RH7.2 boxes without any need for the --force flag on any of them.
> I have also upgraded flawlessly from 1.6 to 1.7 as well as 1.6 to 1.8
> without error.
gcc & glibc upgrades, sadly enough, are not so smooth. that's why i'm
suggesting to everyone is able to run a make and to do some cp to build
binaries from sources instead of using the .rpm
- Davide
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
