On Thu, Jun 29, 2000 at 02:03:46AM +0200, Andre Morin wrote:
>
> Unfortunately, the second option is what I have to face.
Then unless you have a way of definitively identifying which emails
to extract from whathever local delivery method each user employs,
then you have no perfect solution.
If the user has control of the delivery/forwarding in any way,
they may not be retreivable at all. If there was some user mail on the
clone prior to the MX mixup, then you'll need a way to separate them.
If you are lucky and the only delivey method is Maildir and the only
emails on that system are ones that can be redirected, then you
can probably qmail-inject them back into your clone system with
an smtproutes entry. You may need to grep out certain Delivered-to:
headers to avoid hitting the anti-loop code of qmail.
If you are not so lucky, then it'll be painful and thankless and
probably imperfect and there is no one solution.
Regards.
> > It depends on where the mail is on this clone server. Is it in the
> > mail queue or has it been locally delivered to users there?
> >
> > The former is much easier to deal with than the latter.
> >
> >
> > Regards.
> >
> > On Thu, Jun 29, 2000 at 01:56:31AM +0200, Andre Morin wrote:
> > >
> > > First of all, this is a really stupid situation we should never have run
> > > into in the first place ; however :
> > >
> > > Due to some not so interesting reasons, for a couple of days our DNS has
> > > pointed to another machine with our cloned qmail-configuration on
> > > another IP in another town. I have complete root access to that machine.
> > >
> > > Now everything is back as before, but while this machine was MX for quite
> > > a bunch of virtual domains we host, the mail arrived there.
>
