semvec/pypi-packages huggingface dataset:
incenp.davpoint 0.2.1
Davfs2 wrapper to mount SharePoint filesystems

Davpoint - Davfs2 wrapper to mount SharePoint filesystems
=========================================================

Davpoint is a wrapper for the
[Davfs2](http://savannah.nongnu.org/projects/davfs2) tool. It allows to
mount remote SharePoint filesystems that require cookie-based
authentication.


Rationale
---------
Although SharePoint services are available through the standard WebDAV
protocol, they may require the client to provide an authentication token
in the HTTP header in addition to the standard username and password.
The WebDAV client for Linux ``davfs2`` does not directly support this
mode of authentication, but it does allow to set any arbitrary cookie in
its configuration file and its developer [has
suggested](http://savannah.nongnu.org/support/?109122#comment1) to
“create some start script to automate” the retrieval of the
authentication token.

Davpoint provides precisely such a script. Given a little extra
configuration (see below), it will automatically authenticate a user to
a SharePoint service, get the authentication token, then call ``davfs2``
(through the standard ``mount (8)`` command) with the required
configuration options to mount the SharePoint filesystem.


Configuration & Usage
---------------------
Davpoint requires the WebDAV resource and its intended mount point to be
listed in the ``/etc/fstab`` file. The username and password must also
appear in Davfs2’s “secrets” file (either ``/etc/davfs2/secrets`` or
``~/.davfs2/secrets``), according to Davfs2’s documentation.

In addition, Davpoint needs a dedicated configuration file, which it
expects in ``~/.davfs2/sharepoint.conf`` by default. This file uses the
.ini format, where each section represents a SharePoint resource.

Each section must contain at least two options: ``endpoint``, which is
the WebDAV resource to mount, and ``mountpoint``, which is the location
on the local filesystem where the resource should be mounted. The values
must match what is configured in the ``/etc/fstab`` file. All other
options will be passed verbatim to Davfs2.

Importantly, the main Davfs2 configuration file
(``/etc/davfs2/davfs2.conf`` or ``~/.davfs2/davfs2.conf``) is *ignored*
when Davfs2 is called by Davpoint. Any Davfs2 options needed for a given
SharePoint resource *must* be specified in the ``sharepoint.conf`` file
instead of the ``davfs2.conf`` file.

Here is an example of a ``~/.davfs2/sharepoint.conf`` file:

```
[example]
endpoint: https://example.com/personal/alice_example_com/Documents
mountpoint: /home/alice/example
use_locks: 0
```

With such a configuration, the resource may be mounted by the following
command:

```
$ davpoint example
```

Unmounting the resource is done as usual with the standard ``umount
(8)`` command.


Copying
-------
Davpoint is distributed under the terms of the GNU General Public
License, version 3 or higher. The full license is included in the
[COPYING file](COPYING) of the source distribution.
verify-email 2.4.4.dev0
A small package for email verification

# verify-email

`verify-email` can verify any email address by efficiently checking the domain name and pinging the handler to verify its existence.

## Features

- Syntax checks
- MX(Mail Exchange records) verification
- Email Handler verification
- Caching domain lookups to improve performance
- Supports `asyncio` for concurrency
- For `multiprocessing` usage, see [fast_verify.py](https://github.com/kakshay21/verify_email/blob/master/verify_email/fast_verify.py)).

## Compatibility
- Written in Python 3.7.
- Supports Python 3.7+.
- It should work on Linux, Mac and Windows.

## Installation
### From [pypi.org](https://pypi.org/project/verify-email/)
```
$ pip install verify-email
```
### From source code
```
$ git clone https://github.com/kakshay21/verify_email
$ cd verify_email
$ virtualenv env
$ source env/bin/activate
$ python setup.py develop
```

## Usage
```
>>> from verify_email import verify_email
>>> verify_email('foo@bar.com')
False
>>> verify_email(['foo@bar.com', 'example@foo.com'])
[False, False]
```
Also, note that some emails will likely fail in validation, if so you can check the reason of failure
using debug flag.
```
>>> from verify_email import verify_email
>>> verify_email('foo@bar.com', debug=True)
```

see for more examples [examples.py](https://github.com/kakshay21/verify_email/blob/master/examples.py)

## Contribute
- Issue Tracker: https://github.com/kakshay21/verify_email/issues
- Source Code: https://github.com/kakshay21/verify_email

## Support
If you are having issues, please create an issue for it. And feel free to contribute as well 😄.