Ideally, the ImapClientDemo sample would also demo IDLE support and restoring the connection if/when it gets dropped.

With 1.8 we will have a fully working kubernetes based deployment of mailu and a helm chart. Helm 3 is out, so the helm chart can fully replace the current static k8s examples (static k8s files can be created with helm3 at client side without special requirements to the kubernetes cluster and even without running kubernetes).

I'd like to modify the documentation:

• replace existing kubernetes

The Help Browser is a new feature to bring online help to NeoMutt.
The code is in the devel/help branch.

It adds a new config variable: $help_doc_dir which should point to a copy of the test-doc repo.
Help can be activated by pressing Alt-H

Part 1

Add a new config var

DoS vulnerability fixed in https://github.com/gorilla/websocket/releases/tag/v1.4.1

🚀 Feature

It would be nice to automatically add a user's Github repositories when github connect is enabled.

Design, Layout, Architecture

It should be pretty easy to query the user's repositories and add them to the user settings on github connect. The Github API already has an endpoint to list them, so we just need to write some code to fetch the list, parse it, and add them to the us

Steps:
Run standalone Greenmail server with the -Dgreenmail.auth.disabled option
send an email to the server for [email protected] //new account is created
Try to fetch emails for [email protected] from the server connecting as [email protected] with any password

Expected: The emails fetch successfully since documentation states:

Disables user authentication check, so that any password works. 
``

Hello.

I would like to implement Davmail for a mailbox hosted in Exchange Online (Office 365).
Conditional Access in Azure AD requires MFA to access the mailbox with a browser from a non-compliant device.
Davmail 5.4.0 runs as a service on Ubuntu 18.04 Server without a desktop environment.

I have created an application in Azure AD with the required permissions

Can someone share a dav

Hey guys, like many of us, I am currently going through the motions of updating a happily working Eventum 2.2 to the latest versions for continued PHP support. (Thanks for making something that has served my team for that long!)

I've successfully migrated my database and my workflow. I'm stuck on my old customer integration (formerly /includes/customer/{customintegration}.php).

It see

Feature: Well written, clear and formatted documentation.

Recommended approaches
Currently, Most of the configuration files and yml files have well put variable names and functionality. Unfortunately, explaining each choice and option has not been done well enough and what has been written, is written by a mathematics researcher with her very little experience in writing nicely formatted d

Submission type

• Feature Request

YAM version

current master branch

It would be great if there was some documentation regarding the environment requirements, in order to compile the project from source.
E.g. MUI, the various MCCs, the NDK 3.9 (if needed), etc.

Even with an educated guess that I made, I'm still missing some references to some files which don't seem to be part of

It is convention for examples to be in a examples directory. Cargo actually has a flag to run examples in the examples directory by name.