[SOGo] BTS activities for Wednesday, January 13 2021

2021-01-13 Thread SOGo reporter 
Title: BTS activities for Wednesday, January 13 2021





  
BTS Activities

  Home page: https://sogo.nu/bugs
  Project: SOGo
  For the period covering: Wednesday, January 13 2021

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5242
	2021-01-13 09:24:51
	updated (open)
	Web Mail
	Text color in search bar is white on white background
	
	  
	
  
  


-- users@sogo.nuhttps://inverse.ca/sogo/lists

Re: [SOGo] Thunderbird Status

2021-01-13 Thread John Bieling 
If you have error reports regarding Thunderbird CardDAV, than it would be 
beneficial to file a bug, so they can improve. I don't think they know...

John

> Am 13.01.2021 um 19:24 schrieb Lukas Wringer 
> (lukas.wrin...@rz.uni-augsburg.de) :
> 
> Hi,
> 
> I think it was just to early to use the MZLA/Mozilla integration of CardDav. 
> I tried it without the plugin (in 78*) and it was just garbage (it is still 
> on proof-of-concept level imho). Maybe we just have to skip 78 for good...
> 
> I think the only way for even 86 (or whatever will be the next final) to work 
> properly (with lists, read-only address books, and so on) would be if SOGo 
> and MZLA could work together on this.
> 
> Although on Beta 85 CardDav is enabled by default...
> 
> greetings, Lukas
> 
>> Am 13.01.21 um 18:00 schrieb Frank Pauxberger (fr...@pauxberger.de):
>> Hi Christian,
>> I have started with SOGo some time back in 2011 and still love it after 
>> about 10 years. It does everything I need and look for and I keep 
>> recommending it! Great work once more and once again!!
>> This time though I have to admit I am slightly disappointed on whatever 
>> happens around the Plugin for TB78. I have tested it over and over again 
>> with varying results, always using the latest versions of the SW required. 
>> And with various comments here in the mailing list.
>> But I fully agree, it is not production ready.
>> So for now I stay on TB68 in Prod and have a test instance with TB78 using 
>> TbSync/provider for CalDAV and CardDAV/Category Manager. That is sort of ok 
>> but nothing I would recommend in larger scenarios. I am really (really 
>> really, Ludovic) looking forward to having a reliably working SOGo Connector 
>> for Thunderbird 78.
>> What is the bottle neck?
>> Kind regards
>> Frank
>>  Original-Message 
>> Subject: [SOGo] Thunderbird Status
>> From: Cn 
>> To: Users 
>> CC:
>> Date:  Mittwoch, 13. Jan. 2021, 14:09 (MN +0100)
>>> Hello all,
>>> I wanted to ask what the current plan/status is of the TB Plugin for 78. It 
>>> is not really ready for production yet.
>>> So what are the plans?
>>> Is there a timeline?
>>> What are other doing in the meantime? Stay on 68 ?
>>> 
>>> Regards
>>> 
>>> 
>>> Christian
>> -- 
>> users@sogo.nu
>> https://inverse.ca/sogo/lists
> 
> -- 
> Lukas Wringer
> 
> Universität Augsburg
> Rechenzentrum
> Service & Support
> 86135 Augsburg
> 

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Thunderbird Status

2021-01-13 Thread Lukas Wringer 

Hi,

I think it was just to early to use the MZLA/Mozilla integration of 
CardDav. I tried it without the plugin (in 78*) and it was just garbage 
(it is still on proof-of-concept level imho). Maybe we just have to skip 
78 for good...


I think the only way for even 86 (or whatever will be the next final) to 
work properly (with lists, read-only address books, and so on) would be 
if SOGo and MZLA could work together on this.


Although on Beta 85 CardDav is enabled by default...

greetings, Lukas

Am 13.01.21 um 18:00 schrieb Frank Pauxberger (fr...@pauxberger.de):

Hi Christian,

I have started with SOGo some time back in 2011 and still love it after 
about 10 years. It does everything I need and look for and I keep 
recommending it! Great work once more and once again!!


This time though I have to admit I am slightly disappointed on whatever 
happens around the Plugin for TB78. I have tested it over and over again 
with varying results, always using the latest versions of the SW 
required. And with various comments here in the mailing list.

But I fully agree, it is not production ready.

So for now I stay on TB68 in Prod and have a test instance with TB78 
using TbSync/provider for CalDAV and CardDAV/Category Manager. That is 
sort of ok but nothing I would recommend in larger scenarios. I am 
really (really really, Ludovic) looking forward to having a reliably 
working SOGo Connector for Thunderbird 78.


What is the bottle neck?

Kind regards
Frank




 Original-Message 
Subject: [SOGo] Thunderbird Status
From: Cn 
To: Users 
CC:
Date:  Mittwoch, 13. Jan. 2021, 14:09 (MN +0100)

Hello all,
I wanted to ask what the current plan/status is of the TB Plugin for 
78. It is not really ready for production yet.

So what are the plans?
Is there a timeline?
What are other doing in the meantime? Stay on 68 ?

Regards


Christian

--
users@sogo.nu
https://inverse.ca/sogo/lists


--
Lukas Wringer

Universität Augsburg
Rechenzentrum
Service & Support
86135 Augsburg



OpenPGP_signature
Description: OpenPGP digital signature

Re: [SOGo] Thunderbird Status

2021-01-13 Thread Frank Pauxberger 

Hi Christian,

I have started with SOGo some time back in 2011 and still love it after 
about 10 years. It does everything I need and look for and I keep 
recommending it! Great work once more and once again!!


This time though I have to admit I am slightly disappointed on whatever 
happens around the Plugin for TB78. I have tested it over and over again 
with varying results, always using the latest versions of the SW 
required. And with various comments here in the mailing list.

But I fully agree, it is not production ready.

So for now I stay on TB68 in Prod and have a test instance with TB78 
using TbSync/provider for CalDAV and CardDAV/Category Manager. That is 
sort of ok but nothing I would recommend in larger scenarios. I am 
really (really really, Ludovic) looking forward to having a reliably 
working SOGo Connector for Thunderbird 78.


What is the bottle neck?

Kind regards
Frank




 Original-Message 
Subject: [SOGo] Thunderbird Status
From: Cn 
To: Users 
CC:
Date:  Mittwoch, 13. Jan. 2021, 14:09 (MN +0100)

Hello all,
I wanted to ask what the current plan/status is of the TB Plugin for 
78. It is not really ready for production yet.

So what are the plans?
Is there a timeline?
What are other doing in the meantime? Stay on 68 ?

Regards


Christian

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Need help with external SMTP-server

2021-01-13 Thread nico...@hoeft.de 
Hi Marina,

> I am able to send a mail from address us...@abcd.tld to
> us...@domain1.tld when using SOGo's webfrontend. But using the
> Webfrontend I cannot send an email to external services like
> user.n...@gmail.com or anything like that. 
This sounds like a configuration problem on the postfix configuration.
Is it handling incoming email differently when they come from the inside
of your network?


> Jan 13 12:26:04 sogod [27233]: |SOGo| starting method 'POST' on uri
> '/SOGo/so/orange/Mail/0/folderINBOX/folderDrafts/newDraft1610537152-1/send'
> Jan 13 12:26:05 sogod [27233]: [WARN]
> <0x0x55f51340a7c0[SOGoUserDefaults]> expected an NSString for
> 'SOGoMailComposeFontSize' (ignored)
> Jan 13 12:26:05 sogod [27233]: [ERROR] <0x0x55f513552a50[SOGoMailer]>
> Could not connect to the SMTP server smtp://abc.tld
> Jan 13 12:26:05 sogod [27233]: |SOGo| request took 0.666737 seconds to
> execute
>  
>  
> I mean, why do I get a relay-denied-error from the recipient's
> server?! Why does sogo try to send via google or yahoo or whoever, I
> want to send via my smtp-server defined in sogo.conf - this gives me a
> headache.

Where do you see the relay denied error?


> *Second Case: *
> Keeping everything the same but changing the smtp-line in sogo.conf to
>  
> SOGoSMTPServer = "smtp://abc.tld:587/?tls=YES";
>  
> results in  an errormessage in the browser-window saying: 
> Requires state 2, now 1
>  
> and in the log I find: 
>  
> Jan 13 12:36:31 sogod [29373]: |SOGo| starting method 'POST' on uri
> '/SOGo/so/orange/Mail/0/folderINBOX/folderDrafts/newDraft1610537787-1/send'
> Jan 13 12:36:31 sogod [29373]: [WARN]
> <0x0x5562213901e0[SOGoUserDefaults]> expected an NSString for
> 'SOGoMailComposeFontSize' (ignored)
> 2021-01-13 12:36:31.750 sogod[29373:29373] ERROR(-[NGActiveSSLSocket
> startTLS]): couldn't setup SSL connection on host
> abc.tld (error:0001:lib(0):func(0):reason(1))...
> 2021-01-13 12:36:31.750 sogod[29373:29373] SMTP: unable to perform
> STARTTLS on socket
> Jan 13 12:36:31 sogod [29373]: [ERROR] <0x0x5562213bdf60[SOGoMailer]>
> Could not connect to the SMTP server smtp://abc.tld:587/?tls=YES
> Jan 13 12:36:31 sogod [29373]: |SOGo| request took 0.566150 seconds to
> execute
>  

This is odd, is it possible that certificate validation fails? Can you
try from the command line:

openssl s_client -starttls smtp -connect abc.tld:587 | openssl x509
-noout -text

And then validate the given hostname is in the certificates subject or
alternative name.


> *Third case: *
>  
> Changing the smtp-line to 
>  
> SOGoSMTPServer = "smtp://abc.tld:465";
>
Port 465 is typically SMTPS. So change smtp:// to smtps://


Nicolas

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Need help with external SMTP-server

2021-01-13 Thread Odhiambo Washington 
On Wed, 13 Jan 2021 at 18:17, "Marina D."  wrote:

> Hello,
>
> for  a few days now I have been fiddling around with a SOGo-Server
> (selfhosted nightly-build, version 5, updated daily at the moment) and so
> far I managed to get almost everything up and running.
> But there is one big issue I'd be very glad if anyone could give me a hint
> what is wrong here.
>
> The problem in short: I cannot send Mails to external recipients.
>
> This is the basic setup:
>
> The Mailserver with Dovecot and Postfix is on Server A, running for
> several years now and I don't want to change the way things are on here too
> much. This server has several the domains on it, among them abcd.tld and
> the Server-FQDN is fqn.abc.tld
>
> The new server B on which SOGo has been installed is a fresh VServer using
> Debian 10, LetsEncrypt-Certificate for accessing the webfrontend and it
> uses the nightly-builds. I followed the official installation guide and set
> up a SOGo-Instance using Postgresql 11 for users authentification. The view
> within my database with the names, passwords matching the mail-passwords
> and so on exists and I can login successfully. I can see the Folders, read
> mails, create appointments and so on.
> This Server B on which SOGo is installed has received its own subdomain so
> it's reachable at sogo.abcd.tld.
>
> Long description of the problem:
> My problem is that I cannot send mails to addresses outside of my own
> domain-range. Meaning: I can send Emails with SOGos Webfrontend to any
> email-address @abcd.tld or any other domain hosted on the server "A".
> On this server A with postfix and dovecot there are several vhost-domains,
> for example domain1.tld. As it resides on the same server as abc.tld I am
> able to send a mail from address us...@abcd.tld to us...@domain1.tld when
> using SOGo's webfrontend. But using the Webfrontend I cannot send an email
> to external services like user.n...@gmail.com or anything like that.
> Using a classic Mail-App like thunderbird on my desktop pc which connects
> to the emailserver on fqn.abc.tld directly works perfect and there are no
> restrictions to send emails in any kind like mentioned above.
>
>
> When I try to send mails from SOGo's Webfrontend I get these possible
> errors depending on the config in /etc/sogo/sogo.conf:
>
> *First case: *
> more or less vanilla config setting as few ports as possible:
>
> /etc/sogo/sogo.conf:
>
>   /* Mail */
>   SOGoDraftsFolderName = INBOX.Drafts;
>   SOGoSentFolderName = INBOX.Sent;
>   SOGoTrashFolderName = INBOX.Trash;
>   SOGoJunkFolderName = INBOX.Spam;
>   SOGoIMAPServer = "imap://abc.tld";
>   SOGoSieveServer = "sieve://abc.tld:4190";
>   SOGoSMTPServer = "smtp://abc.tld";
>

 SOGoSMTPServer = 127.0.0.1;
or
 SOGoSMTPServer = smtp://domain*:port  *

*[*Installation and Configuration Guide (sogo.nu)
]

SOGoSMTPServer:   The DNS name or IP address of the SMTP server
used when SOGoMailingMechanism is set to smtp.
   Supported formats are:
*smtp://domain:port*, *smtps://domain, domain:port*,
*smtp://domain:port/?tls=YES*.
   Using the option tls=YES will
enforce using STARTTLS SMTP connections. Thus,
smtp://localhost:587/?tls=YES
   would use the default MUA port
on localhost with STARTTLS enforced.
  To disable TLS verification for
localhost domains, add tlsVerifyMode=allowInsecureLocalhost to
  such connections:
smtp://localhost:587/?tls=YES&tlsVerifyMode=allowInsecureLocalhost.

And all that is required is that a connection can be made to N.N.N.N and it
allows the IP address of the SOGo server to send mail through it.

So, once you append the port to the value, and restart sogod, share the
logs of the SMTP server and not SOGo :-)



-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

AW: [SOGo] Need help with external SMTP-server

2021-01-13 Thread "Nagel, Peter" 
Hi,



you told us that the name of Server a is fqn.abc.tld, but you configured 
SOGoSMTPServer = "smtp://abc.tld"; instead of SOGoSMTPServer = 
"smtp://fqn.abc.tld"; leading to the error in the log saying Could not connect 
to the SMTP server smtp://abc.tld:587/?tls=YES



The SOGoServer variables have to contain something that can be found in 
DNS or IP addresses (something like SOGoSMTPServer = "smtp://192.168.178.14";)



Bye, Peter



Von: users-requ...@sogo.nu  Im Auftrag von "Marina D."
Gesendet: Mittwoch, 13. Januar 2021 15:43
An: users@sogo.nu
Betreff: [SOGo] Need help with external SMTP-server



Hello,



for  a few days now I have been fiddling around with a SOGo-Server (selfhosted 
nightly-build, version 5, updated daily at the moment) and so far I managed to 
get almost everything up and running.

But there is one big issue I'd be very glad if anyone could give me a hint 
what is wrong here.



The problem in short: I cannot send Mails to external recipients.



This is the basic setup:



The Mailserver with Dovecot and Postfix is on Server A, running for several 
years now and I don't want to change the way things are on here too much. This 
server has several the domains on it, among them abcd.tld and the Server-FQDN 
is fqn.abc.tld



The new server B on which SOGo has been installed is a fresh VServer using 
Debian 10, LetsEncrypt-Certificate for accessing the webfrontend and it uses 
the nightly-builds. I followed the official installation guide and set up a 
SOGo-Instance using Postgresql 11 for users authentification. The view within 
my database with the names, passwords matching the mail-passwords and so on 
exists and I can login successfully. I can see the Folders, read mails, create 
appointments and so on.

This Server B on which SOGo is installed has received its own subdomain so 
it's reachable at sogo.abcd.tld.



Long description of the problem:

My problem is that I cannot send mails to addresses outside of my own 
domain-range. Meaning: I can send Emails with SOGos Webfrontend to any 
email-address @abcd.tld or any other domain hosted on the server "A".

On this server A with postfix and dovecot there are several vhost-domains, for 
example domain1.tld. As it resides on the same server as abc.tld I am able to 
send a mail from address us...@abcd.tld   to 
us...@domain1.tld   when using SOGo's webfrontend. 
But using the Webfrontend I cannot send an email to external services like 
user.n...@gmail.com   or anything like that.

Using a classic Mail-App like thunderbird on my desktop pc which connects to 
the emailserver on fqn.abc.tld directly works perfect and there are no 
restrictions to send emails in any kind like mentioned above.





When I try to send mails from SOGo's Webfrontend I get these possible errors 
depending on the config in /etc/sogo/sogo.conf:



First case:

more or less vanilla config setting as few ports as possible:



/etc/sogo/sogo.conf:



  /* Mail */
  SOGoDraftsFolderName = INBOX.Drafts;
  SOGoSentFolderName = INBOX.Sent;
  SOGoTrashFolderName = INBOX.Trash;
  SOGoJunkFolderName = INBOX.Spam;
  SOGoIMAPServer = "imap://abc.tld";
  SOGoSieveServer = "sieve://abc.tld:4190";
  SOGoSMTPServer = "smtp://abc.tld";
  SOGoMailingMechanism = smtp;
  SOGoForceExternalLoginWithEmail = YES;
  //... standard-settings untouched

  SOGoUserSources =

(
  {
type = sql;
id = directory;
viewURL = 
"postgresql://sogo:sogopasswordi@127.0.0.1:5432/sogo/sogo_view";
canAuthenticate = YES;
isAddressBook = YES;
userPasswordAlgorithm = md5;
  }
);

  /* Web Interface */
  SOGoPageTitle = MeinTestSOGo;
  SOGoVacationEnabled = YES;
  //SOGoForwardEnabled = YES;
  SOGoSieveScriptsEnabled = YES;
  SOGoMailAuxiliaryUserAccountsEnabled = YES;
  //SOGoTrustProxyAuthentication = NO;
  //SOGoXSRFValidationEnabled = YES;



  //... more untouched stuff

   /* Debug */
  SOGoDebugRequests = YES;
  SoDebugBaseURL = YES;
  ImapDebugEnabled = YES;
  //LDAPDebugEnabled = YES;
  //PGDebugEnabled = YES;
  //MySQL4DebugEnabled = YES;
  //SOGoUIxDebugEnabled = YES;
  //WODontZipResponse = YES;
  WOLogFile = /var/log/sogo/sogo.log;




In this scenario I can send with sogo to all emailboxes hosted on Server A. As 
soon as I try to send a mail to a mailbox hosted by anyone else (gmail, yahoo, 
...), I get a 5.7.1 relay denied message from the recipient's server (eg. 
gmail or yahoo) in my mail-browserwindow and the log in /var/log/sogo.log 
says:



Jan 13 12:26:04 sogod [27233]: |SOGo| starting method 'POST' on uri 
'/SOGo/so/orange/Mail/0/folderINBOX/folderDrafts/newDraft1610537152-1/send'
Jan 13 12:26:05 sogod [27233]: [WARN] <0x0x55f51340a7c0[SOGoUserDefaults]> 
expected an NSString for 'SOGoMailComposeFontSize' (ignored)
Jan 13 12:26:05 sogod [27233]: [ERROR] <0x0x55f513552a50[SOGoMailer]> Could 
not connect to the SMTP server smtp://abc.tld
J

[SOGo] Need help with external SMTP-server

2021-01-13 Thread "Marina D." 
Hello, 

 

for  a few days now I have been fiddling around with a SOGo-Server (selfhosted nightly-build, version 5, updated daily at the moment) and so far I managed to get almost everything up and running.

But there is one big issue I'd be very glad if anyone could give me a hint what is wrong here.

 

The problem in short: I cannot send Mails to external recipients. 

 

This is the basic setup:

 

The Mailserver with Dovecot and Postfix is on Server A, running for several years now and I don't want to change the way things are on here too much. This server has several the domains on it, among them abcd.tld and the Server-FQDN is fqn.abc.tld

 

The new server B on which SOGo has been installed is a fresh VServer using Debian 10, LetsEncrypt-Certificate for accessing the webfrontend and it uses the nightly-builds. I followed the official installation guide and set up a SOGo-Instance using Postgresql 11 for users authentification. The view within my database with the names, passwords matching the mail-passwords and so on exists and I can login successfully. I can see the Folders, read mails, create appointments and so on. 

This Server B on which SOGo is installed has received its own subdomain so it's reachable at sogo.abcd.tld. 

 

Long description of the problem:

My problem is that I cannot send mails to addresses outside of my own domain-range. Meaning: I can send Emails with SOGos Webfrontend to any email-address @abcd.tld or any other domain hosted on the server "A".

On this server A with postfix and dovecot there are several vhost-domains, for example domain1.tld. As it resides on the same server as abc.tld I am able to send a mail from address us...@abcd.tld to us...@domain1.tld when using SOGo's webfrontend. But using the Webfrontend I cannot send an email to external services like user.n...@gmail.com or anything like that. 

Using a classic Mail-App like thunderbird on my desktop pc which connects to the emailserver on fqn.abc.tld directly works perfect and there are no restrictions to send emails in any kind like mentioned above. 

 

 

When I try to send mails from SOGo's Webfrontend I get these possible errors depending on the config in /etc/sogo/sogo.conf:

 

First case: 

more or less vanilla config setting as few ports as possible: 

 

/etc/sogo/sogo.conf: 

 


  /* Mail */
  SOGoDraftsFolderName = INBOX.Drafts;
  SOGoSentFolderName = INBOX.Sent;
  SOGoTrashFolderName = INBOX.Trash;
  SOGoJunkFolderName = INBOX.Spam;
  SOGoIMAPServer = "imap://abc.tld";
  SOGoSieveServer = "sieve://abc.tld:4190";
  SOGoSMTPServer = "smtp://abc.tld";
  SOGoMailingMechanism = smtp;
  SOGoForceExternalLoginWithEmail = YES;
  //... standard-settings untouched

  SOGoUserSources =


    (
      {
        type = sql;
        id = directory;
        viewURL = "postgresql://sogo:sogopasswordi@127.0.0.1:5432/sogo/sogo_view";
        canAuthenticate = YES;
        isAddressBook = YES;
        userPasswordAlgorithm = md5;
      }
    );

  /* Web Interface */
  SOGoPageTitle = MeinTestSOGo;
  SOGoVacationEnabled = YES;
  //SOGoForwardEnabled = YES;
  SOGoSieveScriptsEnabled = YES;
  SOGoMailAuxiliaryUserAccountsEnabled = YES;
  //SOGoTrustProxyAuthentication = NO;
  //SOGoXSRFValidationEnabled = YES;

 

  //... more untouched stuff

   /* Debug */
  SOGoDebugRequests = YES;
  SoDebugBaseURL = YES;
  ImapDebugEnabled = YES;
  //LDAPDebugEnabled = YES;
  //PGDebugEnabled = YES;
  //MySQL4DebugEnabled = YES;
  //SOGoUIxDebugEnabled = YES;
  //WODontZipResponse = YES;
  WOLogFile = /var/log/sogo/sogo.log;


 

In this scenario I can send with sogo to all emailboxes hosted on Server A. As soon as I try to send a mail to a mailbox hosted by anyone else (gmail, yahoo, ...), I get a 5.7.1 relay denied message from the recipient's server (eg. gmail or yahoo) in my mail-browserwindow and the log in /var/log/sogo.log says: 

 

Jan 13 12:26:04 sogod [27233]: |SOGo| starting method 'POST' on uri '/SOGo/so/orange/Mail/0/folderINBOX/folderDrafts/newDraft1610537152-1/send'
Jan 13 12:26:05 sogod [27233]: [WARN] <0x0x55f51340a7c0[SOGoUserDefaults]> expected an NSString for 'SOGoMailComposeFontSize' (ignored)
Jan 13 12:26:05 sogod [27233]: [ERROR] <0x0x55f513552a50[SOGoMailer]> Could not connect to the SMTP server smtp://abc.tld
Jan 13 12:26:05 sogod [27233]: |SOGo| request took 0.666737 seconds to execute
 

 

I mean, why do I get a relay-denied-error from the recipient's server?! Why does sogo try to send via google or yahoo or whoever, I want to send via my smtp-server defined in sogo.conf - this gives me a headache. 

 

Second Case: 

Keeping everything the same but changing the smtp-line in sogo.conf to

 

SOGoSMTPServer = "smtp://abc.tld:587/?tls=YES";

 

results in  an errormessage in the browser-window saying: 

Requires state 2, now 1

 

and in the log I find: 

 

Jan 13 12:36:31 sogod [29373]: |SOGo| starting method 'POST' on uri '/SOGo/so/orange/Mail/0/folderINBOX/folderDrafts/newDraft1610537787-1/send'
Ja

[SOGo] Thunderbird Status

2021-01-13 Thread c...@brain-biotech.de 

Hello all,
I wanted to ask what the current plan/status is of the TB Plugin for 78. 
It is not really ready for production yet.

So what are the plans?
Is there a timeline?
What are other doing in the meantime? Stay on 68 ?

Regards


Christian

--
Dr. Christian Naumer
Vice President
Unit Head Bioprocess Development

B.R.A.I.N Aktiengesellschaft
Darmstaedter Str. 34-36, D-64673 Zwingenberg
e-mail c...@brain-biotech.com, homepage www.brain-biotech.com
phone +49-6251-9331-30 / fax +49-6251-9331-11

Sitz der Gesellschaft: Zwingenberg/Bergstrasse
Registergericht AG Darmstadt, HRB 24758
Vorstand: Adriaan Moelker (Vorstandsvorsitzender), 
Lukas Linnig

Aufsichtsratsvorsitzender: Dr. Georg Kellinghusen
--
users@sogo.nu
https://inverse.ca/sogo/lists