Hi @scheini72,

I can’t give you a date on the 9.x release, but it will not work with any php packages, than those that the distribution provides for this exact release.

The reason is that php-mapi needs to be built against the abi of a given php release and if you switch the release this abi will no longer match.

@fbartels Personal? Where ever did I get personal?

And since you edited: Good way to communicate? You were complaining about my formatting, a formatting that is acceptable English everywhere else, a style that is used throughout your own manuals… I have absolutely no idea how to change it in order to make it conform to your standard because you have not GIVEN any other standard to adhere to. All you’ve said is that paragraphs are too long, ok so I shortened it. That wasn’t good enough and you wanted them even shorter… And now somehow took offense because I shortened it too much?

It’s like you’re trying to deflect the problem in Spooler to try and point to something, ANYTHING else in order to avoid answering. I seriously hope that’s not the case, but it certainly is looking more and more like that is what this is currently about…

@lendl said in Postfix Übergabe an Kopano / Postfix-Kopano connection:

mailbox_command

I would rather recommend to use lmtp for the final delivery. The documentation explains how.

@lendl said in Postfix Übergabe an Kopano / Postfix-Kopano connection:

but the name of the Fetchmail user (catcher@localhost).

You can specify in your fetchmailrc where to deliver to locally. e.g. is "jsmith" here;

Hi @tahrens,

at this point in time importing the calendar (for example with the documentation you already found) is the best way.

Yes now the log is gone, it was
olcDbIndex: mail eq,sub

Claus

@longsleep @fbartels
Thanks for that info
both project/daemon and project/python-daemon have daemon to import
Very confusing. name conflict
kopano-search-10.0.4 is running now

No, I would say essentially WebApp is “just” a client as well. It may be a powerful client, but in the end it also just uses a defined api to talk to the server backend.

@smguenther said in kopano-migration-imap : Unable to get reminder property: not found:

Do you agree, that splitting the migration into db and attachements would be the least troublesome way?

Yes, probably. You only have to account for the time it takes to export and import the database. If you only have a small window where your server can be offline you could speed it up by working with mysql master/slave replication.

Ok @xthbx and @fbartels you were right. I found the issue, the domain I use on the Kopano Server was still stored as alias on the old mailserver. Thank you for the tip with the overlapping.

@fbartels I used Kerio Connect before and now I try Kopano, maybe it will be the successor.

Hi @Allyfied,

sure you could by the means of moving the database and attachment data to another system, also connecting this system back to your ucs is possible.

But how exactly this can be achieved always depends on the actual implementation. It could for example be an option as well to setup the new server us a ucs slave server, which means that it gets access to the existing ldap automatically.

Hello.,
it works! fine!
Thanks
Thomas

Sorry for jumping on an old thread. Can you elaborate slightly on this?

I am having the exact same problem, but I’m not using ldap, I’m just using KopanoDB?

@EtherMan said in Konnectd with ldaps fails verification but no setting for allowing.:

Though I must point out that “by using a secure CA and together with secure DNS, you can be sure that the connection is made to the desired system and to that system only.” is in no way true. DNS is inherently open to multiple vulnerabilities and injection attacks happen on a daily basis.

While this is generally the case, it should be a little different in your internal environment where you have full control of all involved resolvers.

@EtherMan said in Konnectd with ldaps fails verification but no setting for allowing.:

Since I’ll be using containers, I suppose the easiest solution is to mount in the CA as a secret in place of that file such that it only has a single CA in total. Would that work or are there external checks that it has to do that requires one of the standard CAs?

Yes, that should do it. Generally when using containers, it is recommended to mount the trusted CA’s from a location controlled by the local system. Most containers might not even ship any trusted CA.

@EtherMan said in Konnectd with ldaps fails verification but no setting for allowing.:

There’s the survey service that does, but that can be disabled and I’m unsure if that verifies identity though I assume it does.

The survey client uses the normal default CA list to discover if the connection is trusted. So it is effected by SSL_CERT_FILE and/or SSL_CERT_DIR. Since the survey client or its success is entirely optional, any runtime error it produces is not fatal.

As I said though, the command itself does nothing to answer the question of acceptable formats, and clearly it’s NOT enough that the certs are in a format accepted by openssl, since that accepts other formats as well. It’s also completely incorrect KC doesn’t care about uses, because I’ve been over this now and despite being client auth certs, Kopano requires the certs to be server auth as well, even when being used only for client auth. And no, it doesn’t do subject validation either. It may do it for the server, I have not actually tested that, but this is about the client certs. As in the cert the client is presenting to the server. It’s not connecting fom an URL to have a subject line like that. Anyway, as I’ve said, this part is finished. Search is working. Trying to get konnect and webapp to work is a whole new level of stuff to deal with. It’s in times like these where you try to do anything even just slightly out of the box, that you find out how poorly documented a project like this truly is.

Fantastic! That was easy, thanks!

hey there, thank you for the repsonse

sadly it’s not yet what I search for.
if I use:
kopano-migration-pst ./user.pst -f “Sent Elements” -u user@domain.tld --import-root=“Sent Objects”

it creates a subfolder inside “Sent Objects”.
my target is to have all the e-mails inside “Sent Objects”

right now I need to modify the .pst manually.

The starting point is that if something is an alias for a mailbox, then its the same as the mailbox itself. This is the reason why dagent will resolve it to your user guilia.

I think the better approach here is to have a dedicated mailbox for the “invoice” address. This will also reduce the chance that the user forgets to set the “from” address to it when replying.

Since its already the external system who delivers the mail into the mailbox of guilia I would not expect that you need an extra fetchmail job to retrieve the mail, but you for sure need an inactive user or a group to be able to allow guilia to send-as/delegate mail as that additional address.

And the default value for ldap_user_search_filter is the empty string. It all plays together.