hlfh / automua Goto Github PK

RFC 6186
RFC 8314

Source: rseichter/automx2#12

Last update by @rseichter

By the way, on a technical note, the changes you made to populate_with_dict() do not really address a bug of automx2, but a quirk of either the particular MySQL driver you used with SQLAlchemy, or possibly of SQLAlchemy itself. Interesting.

sqlalchemy.exc.IntegrityError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely)
(MySQLdb.IntegrityError) (1452, 'Cannot add or update a child row: a foreign key constraint fails (`automx2`.`domain`, CONSTRAINT `domain_ibfk_1` FOREIGN KEY (`provider_id`) REFERENCES `provider` (`id`))')

I may have to investigate more.

And SQLite does not enforce foreign key constraints.

New setupmethod behaviour for flask 2.2.0: pallets/flask#4577

With:

make devtest

We get:

    raise AssertionError(
AssertionError: The setup method 'shell_context_processor' can no longer be called on the application. It has already handled its first request, any changes will not be applied consistently.
Make sure all imports, decorators, functions, etc. needed to set up the application are done before running it.

EDIT:

pip3.9 uninstall coverage
pip install -r requirements-ci.txt

Source: https://blog.rmilne.ca/2022/01/12/office-365-autodiscover-lookup-process-revisited/

Is it caused by Let's Encrypt expired root CA and a wrong SSL implementation on Microsoft's side?
Other example of issues with this expired root CA: transmission/transmission#1876 and this and that.
Theory: the SSL/TLS library used by Microsoft Remote Connectivity Analyzer has a TLS validation policy which will cause it to always fail if one of the intermediate paths fails, in our case the path using DST Root CA X3 because it is expired.

Microsoft Handshake failure with: https://testconnectivity.microsoft.com/tests/SslServer/input
Might be related to the root CA: https://stackoverflow.com/questions/6353849/received-fatal-alert-handshake-failure-through-sslhandshakeexception
The DST Root CA X3 expired in 09/2021: https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/.
Microsoft Outlook Connectivity test requests a HTTPS address.

ssldump repo
Notes on ssldump ClientHello versions
Some ssldump review
Some TLS handshake failure guide

Solution: being added to the Production ECDSA allow-list takes time (at least one week) but that may solve the TLS handshake failure issue... This will make us switch to the ISRG Root X2 cross-signed by ISRG Root X1 when we renew ECDSA certificates which makes the chain of trust fine. But ECDSA ciphers are not supported by Microsoft.

• Check Outlook AutoDetect ; GET request "https://prod-autodetect.outlookmobile.com/detect?services=office365,outlook,google,icloud,yahoo&protocols=rest-cloud,rest-outlook,rest-office365,eas,imap,smtp" with Headers 'x-email' => '[email protected]'.
• Reject any Autodiscover Exchange ActiveSync MobileSync XML requests ; NS http://schemas.microsoft.com/exchange/autodiscover/mobilesync/requestschema/2006 ; related to: rseichter/automx2#7
• Reject any Autodiscover Exchange ActiveSync JSON request ; related to: gronke/email-autodiscover#4 ; GET /autodiscover/autodiscover.json?Email=[email protected]&Protocol=ActiveSync&RedirectCount=1 HTTP/1.0 ; might help: https://github.com/mailcow/mailcow-dockerized/blob/master/data/web/autodiscover-json.php
• Have a look at Z-Push on Arch Linux: only works with ActiveSync clients and undocumented auth flow
• Have a look with autodiscover-email-settings: does not support signed .mobileconfig profiles & Outlook 2021 for Mac like automx2/automua
• Check so-called Autodiscover V2 and so-called Office 365 support ; might help: https://blog.rmilne.ca/2022/01/12/office-365-autodiscover-lookup-process-revisited/ and https://ingogegenwarth.wordpress.com/2018/05/22/get-autodv2/
• Fix Autodiscover Outlook XML request implementation: done with 2022.6.5
• Do some testing with Fiddle Everywhere
• Have a look with Kolab Autoconf: this is crap, only Apache, not Nginx
• Test https://testconnectivity.microsoft.com/tests/O365Ola/input with automua: this is crap and is messing with TLS: #11
• Analyze notes on Autodiscover and Office 365

I wonder whether automua really has such fine-tuned requirements on the versions of the dependencies as they are specified in pyproject.toml? For each dependency only one specific version is allowed. Or are the given constraints overly restrictive?

http://schemas.microsoft.com/exchange/autodiscover/mobilesync/requestschema/2006

Related to: rseichter/automx2#7

They are currently unsigned.

https://autodiscover.mydomain.tld/mobileconfig/[email protected]

Related to: rseichter/automx2#11

• Implement rseichter/automx2@8206152
• Add tests
• Add doc

When ./contrib/package.sh dist

/Users/hlfh/automx3/.venv/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.

Bug, as request argument is present

Invalid namespaces should be recognised as such and a better error should be displayed in that case.

GitHub pages: add environment, should be auto-deployed from this repo

• Add make gh-pages command 50c9339
• Add docs/gh-pages as a subtree
• Create Thunderbird autoconfig doc separate repo
• Deploy docs/gh-pages to GitHub Pages automua
• Recreate hlfh.github.io separated from project repos' docs
• Update path for make docs command: d44d35d and 5f1e964

Check: gronke/email-autodiscover#4

GET request on automua:

2:30] "GET /autodiscover/autodiscover.json?Email=MYEMAIL%MYDOMAINNAME.TLD&Protocol=ActiveSync&RedirectCount=1 HTTP/1.0" 404 

@HLFH This is not how a "fork" works. You took my existing repository https://github.com/rseichter/automx2 and modified the copyright notes, replacing my name with yours. That is a ripoff of my original work and just won't do. Please delete your Git repository ASAP.