Query: All Stories

	Include stories about projects I am a member of.

Don't create the user, test the supposedly existing one instead

In D5046#63456, @machniak wrote:

BTW, none of the other registered passport clients are added via the migration. Maybe they should too. However, as all of them depend on existing-in-config client secrets and Ids, I'm still not sure migration is the correct place. Maybe we should have something like a "global seeder".

BTW, none of the other registered passport clients are added via the migration. Maybe they should too. However, as all of them depend on existing-in-config client secrets and Ids, I'm still not sure migration is the correct place. Maybe we should have something like a "global seeder".

Check for existence first

We call the seeder after migration, so the seeder will fail because the record already exists.

We should probably contemplate a standard mechanism for cases like this, so we don't copy paste these definitions around.

move the migration to the environment specific overlay

Make amavis aware of local domains via sql query

Entirely bypass virus checks without clamav

Start OAUTH login when loading the roundcube login page

function to regenerate certs

Check dkim alignment on mailtransporttest

Switch to roundcube 1.6

amavis reload script

Amavis: Sign all mail with the same key for dkim alignment

Log exceptions to stdout also with the logfmt driver

Avoid reparenting special folders.

Support configuring the oauth redirect uri

logfmt stdout logger

Add a backtrace when an exception is raised so we know where it

per_user_logging for stdout logging

Also print an error on E_COMPILE_ERROR

Do not log deprecation messages no production systems

Optimize fetchPartBody() for huge results w/o formatting and decoding

Don't log an imap authentication error when log_logins=true

Added the kolab skin because the other repo is not publicly available

CS fixes, update changelog

Fixed managesieve.js

Use rcube_utils::remote_addr() to take HTTP_X_FORWARDED_FOR into account

Introduce optional support to inject PROXY protocol headers after

Add a warning regarding implicit ssl

Added a composer.json

Enigma: WOAT Support (#8626)

Fix Oauth issues with use_secure_urls=true (#9722)

Fix preg_match()'s $flags type (#9686)

BUG: get_variable for postgres never returns a value (#9710)

Added German translation for "Keep Formatting" (#9701)

Introduce security@roundcube.net as security contact (#9694)

Fix PHP fatal error when parsing some malformed BODYSTRUCTURE responses (#9689)

Backport virtuser file email2user fix (#9691)

Password: Remove reference to non-existing 'password_zxcvbn_min_score' option…

Support configuring the oauth redirect uri

Disable the mandate if we retrieve an invalid one

user:resync: efficient resync for created/deleted users

Adjust failed init/cleanup metrics to what the resync command does

kolab_payers metrics

Some payment & transaction metrics

Single kolab_users_count metric with state label

I tried taking into account how states override each other

Avoid noisy warnings on unauthenticated ping requests by outlook on

Avoid pushing resync jobs for deleted users

This warning message is not that useful without a wallet ID, I suppose.

Regarding syncrotons needs:

I think we need to get away from the timestamp comparisons and instead store whatever we need to as part of the synchronization state (tied to the synckey)
Ideally we find something better to store than all entries in a folder that are part of the tag, or at least a more efficient representation than huge urls.

just as an fyi, purging users became less of a priority, so I'm parking this diff for now.

Do not disable a pending mandate

Really only test the IMAP_READY status

Rewrote resync to use separate queries for created/deleted

All Stories
Use Results
Edit Query
Hide Query

Today

Thu, Dec 5

Wed, Dec 4

Tue, Dec 3

Fri, Nov 29

Thu, Nov 28

Wed, Nov 27

Tue, Nov 26

All StoriesUse ResultsEdit QueryHide Query