[Obm] Fwd: Problem after mail migration from old server to a new one

[Benoit CROQUIN]

Hello,

Thanks for your quick answer.
Please find below more info of our migration.

Server S1 was well configured and mails were getting well treated for hostname H1.
Server S2 was well configured and mails were getting well treated for hostname H2.

Our goal is to update S1’s configuration files and then copy mails and configuration from S2 to S1
The steps we followed :

-          Updating S1 configuration files

-          Updating hostnames and domain names on S1 server

-          Recursive Copy /var/spool/cyrus and /var/spool/sieve from S2 to S1

We have 6 mailboxes to migrate.

The Perl script run from the yellow pill or directly : perl -T update.pl --incremental --domain-id 2 --user 4 returns no error.
We also check log messages in (tail -f /var/log/obm-services/obm-services.log) but no error is returned.

As far as we inspect the log file, the problem might occur during :
2016/03/21 17:15:59:14725 [5309]: OBM::Postfix::smtpInEngine:189 INFO - obtention des serveurs SMTP-in à mettre à jour
2016/03/21 17:16:01:16516 [5309]: OBM::ObmSatellite::client:260 INFO - requête 'https://127.0.0.1:30000/postfixsmtpinmaps/host/mydomain' : 200 OK

Besides, if files are generated from the content of OBM’s LDAP directory, is it possible to browse this content to find a misconfiguration ?

Benoit Croquin

De : Obm [mailto:obm-bounces at list.obm.org] De la part de David DOLCIMASCOLO
Envoyé : lundi 21 mars 2016 15:33
À : obm at list.obm.org
Objet : Re: [Obm] Fwd: Problem after mail migration from old server to a new one

Hello,

These files are all generated and maintained by OBM, more precisely by the "automaton" (the Perl script that runs when you click on the yellow pill in OBM web interface). It is generated from the content of OBM's LDAP directory, and depends on the spreading of the mailboxes on your various email backends.

Can you give us some insights on your current configuration:

  *   Number of mailboxes
  *   Number of Cyrus backends
  *   Configuration of your domain (most notably, your domain hosts)

Also, what exactly was your mail migration? For instance, did the hostname of the server change? The IP address?
The more details you give us, the easier it is for us to help :)

Thanks,
Regards,

David DOLCIMASCOLO

Resp. Equipe OBM / OBM Team Lead

Resp. Adjoint Equipe OpenPaas / OpenPaas Team Deputy

-------------------------------------------

+33 6 76 20 62 28

-------------------------------------------

80 rue Roque de Fillol

92800 Puteaux

FRANCE

-------------------------------------------

Message envoyé avec OBM, La messagerie Libre :  http://www.obm.org/
Le 21/03/2016 13:29, David DOLCIMASCOLO a écrit :

-------- Message transféré --------
Sujet :

Problem after mail migration from old server to a new one

Date :

Mon, 21 Mar 2016 12:09:20 +0000

De :

Benoit CROQUIN <b.croquin at labsoft.fr><mailto:b.croquin at labsoft.fr>

Pour :

obm-owner at list.obm.org<mailto:obm-owner at list.obm.org> <obm-owner at list.obm.org><mailto:obm-owner at list.obm.org>



Hello,



After a mail migration from a server to another by

   - copying /var/spool/sieve/ and /var/spool/cyrus

   - updating all suspected configuration files

, email are still not received.



After a deep search in mail logs and google searches, we have found that the following files are curiously empty :

 - /etc/postfix/transport

 -/etc/postfix/virtual_alias

 -/etc/postfix/virtual_domains

 -/etc/posrtif/virtual_mailbox



When these files have been replaced by the old ones, emails are sent and received again.

But as we add a user in obm interface each file is empty again, and as a result no mail get treated.



Do you know what process make these files empty ?





Thanks in advance.



Benoit CROQUIN








_______________________________________________

Obm mailing list

Obm at list.obm.org<mailto:Obm at list.obm.org>

http://list.obm.org/listinfo/obm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.obm.org/archives/obm/attachments/20160321/cbc1a946/attachment-0001.html>