[Obm] Is there a way to install OBM from a script ?

[Ali Larab]

Hello,
I have installed OBM by using the "apt-get install obm".
I have a simple question: Is it possible to install OBM from a script and give it the necessary parameters from an input text file (or pipe command)?
If so, what is the format of this file?

Ex.
echo "Site Internet\nNom_de_courrier\nlocalhost\n127.0.0.1\nMYSQL\n127.0.0.1\nobm\nlabobm\nPassword_ob_user..."| apt-get install obm
or
apt-get install < param_obm.txt

With content of param_obm.txt :
site Internet
nom_de_courrier
localhost
127.0.0.1
MYSQL
127.0.0.1
Obm
labobm
password_ob_user

I'm under debian 6.
Cordialy


De : Obm [mailto:obm-bounces at list.obm.org] De la part de Thomas HILAIRE
Envoyé : lundi 18 janvier 2016 20:06
À : Benoit CROQUIN <b.croquin at labsoft.fr>; David DOLCIMASCOLO <ddolcimascolo at linagora.com>; obm at list.obm.org
Objet : Re: [Obm] ERROR in opush.log file ImapTimeoutException

Hello,

No the STARTTLS command is not required, but strongly encouraged to encrypt exchanges between opush and cyrus. In your case both services run on the same host, so it'd be acceptable to not use STARTTLS for a time.

Does the STARTTLS command run successfully with telnet or curl? I don't think about an issue which can block Opush from running it.

Regards,

Envoyé depuis mon smartphone avec la messagerie libre OBM.org et Opush
-------- Original message --------
From: Benoit CROQUIN
Date:2016/01/06 10:58 (GMT+01:00)
To: Thomas Hilaire ,David DOLCIMASCOLO ,obm at list.obm.org
Subject: RE: [Obm] ERROR in opush.log file ImapTimeoutException


Hello,

Thanks for your answer, I have good news :)

In response to your questions :

1.       Yes, synchronization was working and stopped suddenly.

2.       No change to imap configuration was made.

3.       Still no sync by modification on imap timeout change.

4.
The good news is that disable imap.activateTLS get rid of connection troubles.
Synchronization is now running :)

As the synchronization was previously working with imap.activateTLS set to true, the problem might be due to :

-          The STARTTLS command
or

-          The imap server configuration

As no modification was made on imap server configuration, the problem might be due to the STARTTLS command.

I think that synchronization stopped because a full size disk problem occurred about this time.
So, maybe the full size disk problem obstruct the STARTTLS command execution and freeze its re-execution.

Could you tell us if STARTTLS command is required or a possible way to fix its no-execution ?

Thanks,

Regards

De : Thomas Hilaire [mailto:thilaire at linagora.com]
Envoyé : mercredi 6 janvier 2016 09:27
À : Benoit CROQUIN; David DOLCIMASCOLO; obm at list.obm.org<mailto:obm at list.obm.org>
Objet : Re: [Obm] ERROR in opush.log file ImapTimeoutException

Hello,

Can you confirm that your synchronization was working but it has stopped suddently ?
In such case, it may come from a change on the configuration of your imap or opush servers ?

Please first try with a higher timeout value to be sure that it's not a regular timeout.
Set "imap.timeoutInMs=60000" in /etc/opush/mail_conf.ini then restart opush and retry a sync.

Also, opush is trying to initiate a STARTTLS command on your imap connection.
Are you sure that your imap server is well configured to accept it ?
Try to disable that with "imap.activateTLS=false" to see if you continue to have connection troubles.

Regards,


Thomas Hilaire - Linagora LGS/R&D

Lead-Tech OBM

Dev Open-Paas

+33 6 43 65 66 03



thilaire at linagora.com<mailto:thilaire at linagora.com>


On 01/05/2016 06:01 PM, Benoit CROQUIN wrote:
Hello,

Thanks for your quick answer.
Please find the following results and enclosed opush.log file :


·         Configured IP address :
                Imap_frontend                127.0.0.1
                Imap     127.0.0.1
                smtp_out           127.0.0.1


·         telnet 127.0.0.1 143
root at enzo-rosso:~# telnet 127.0.0.1 143
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE STARTTLS AUTH=PLAIN SASL-IR] enzo-rosso Cyrus IMAP v2.4.16-Debian-2.4.16-2~obm60+1 server ready


·         IMAP timeout of opush has been increased  to 10000 but synchronization still fails after restarting opush service

Thanks,
Regards,


Benoit CROQUIN

De : Obm [mailto:obm-bounces at list.obm.org] De la part de David DOLCIMASCOLO
Envoyé : mardi 5 janvier 2016 16:22
À : obm at list.obm.org<mailto:obm at list.obm.org>
Objet : Re: [Obm] ERROR in opush.log file ImapTimeoutException

Hello,

Your IMAP server is probably slow to answer, if reachable at all.
Can you do the following and give us the results here:

  *   The configured IP address of your imap_frontend, imap and smtp_out hosts for your domain.
  *   On the opush machine, telnet <ip address of the IMAP server> 143
  *   Increase the IMAP timeout of opush, as documented in http://docs.obm.org/opush/opush.html#_mail_configuration, then restart opush and try again.

And please send a complete log file exposing the issue, not just the stacktrace.

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 05/01/2016 16:15, Benoit CROQUIN a écrit :
1.       Reference : OBMFULL-6446<https://ci-obm.linagora.com/jira/browse/OBMFULL-6446>


Dear Sir,
We face up with a synchronisation problem.
Mobile devices like phones are no more synchronized with obm.
If the devices are well listed in obm configuration page as shown in enclosed file : periphMobile.JPG, there is no first synchronisation.
Opush log file contains ERROR log on ImapTimeoutException, this error occured at every synchronisation attempt, as shown in opush.log enclosed file.
After restarting opush service, obm-tomcat service and even the VM, the problem still persists.
After removing and re-installing opush and obm-sync, the problem still persists.
Could you provide us some information to debug this issue please ?
Does a file or a record in tables opush_* lock this synchronisation process ?
Best regards,
Benoit Croquin





_______________________________________________

Obm mailing list



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





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






_______________________________________________

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/20160205/347f431b/attachment-0001.html>