summary refs log tree commit diff
path: root/synapse/push/pusher.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Clean up startup for the pusher (#6558)Richard van der Hoff2019-12-181-5/+7
| | | | | | | | | | | | | | | | | | | | | | | * Remove redundant python2 support code `str.decode()` doesn't exist on python3, so presumably this code was doing nothing * Filter out pushers with corrupt data When we get a row with unparsable json, drop the row, rather than returning a row with null `data`, which will then cause an explosion later on. * Improve logging when we can't start a pusher Log the ID to help us understand the problem * Make email pusher setup more robust We know we'll have a `data` member, since that comes from the database. What we *don't* know is if that is a dict, and if that has a `brand` member, and if that member is a string.
* Allow Synapse to send registration emails + choose Synapse or an external ↵Andrew Morgan2019-09-061-6/+11
| | | | | | | | | | | | | | | | server to handle 3pid validation (#5987) This is a combination of a few different PRs, finally all being merged into `develop`: * #5875 * #5876 * #5868 (This one added the `/versions` flag but the flag itself was actually [backed out](https://github.com/matrix-org/synapse/commit/891afb57cbdf9867f2848341b29c75d6f35eef5a#diff-e591d42d30690ffb79f63bb726200891) in #5969. What's left is just giving /versions access to the config file, which could be useful in the future) * #5835 * #5969 * #5940 Clients should not actually use the new registration functionality until https://github.com/matrix-org/synapse/pull/5972 is merged. UPGRADE.rst, changelog entries and config file changes should all be reviewed closely before this PR is merged.
* Run Black. (#5482)Amber Brown2019-06-201-6/+4
|
* Add ability to perform password reset via email without trusting the ↵Andrew Morgan2019-06-061-2/+2
| | | | | | | | | | | | identity server (#5377) Sends password reset emails from the homeserver instead of proxying to the identity server. This is now the default behaviour for security reasons. If you wish to continue proxying password reset requests to the identity server you must now enable the email.trust_identity_server_for_password_resets option. This PR is a culmination of 3 smaller PRs which have each been separately reviewed: * #5308 * #5345 * #5368
* Send out emails with links to extend an account's validity periodBrendan Abolivier2019-04-171-1/+5
|
* Drop logging level of creating a pusherErik Johnston2019-02-221-1/+1
|
* Logging improvements for the pusher (#4691)Richard van der Hoff2019-02-201-5/+6
|
* run isortAmber Brown2018-07-091-1/+2
|
* make imports localAdrian Tschira2018-04-281-1/+1
| | | | Signed-off-by: Adrian Tschira <nota@notafile.com>
* replace 'except:' with 'except Exception:'Richard van der Hoff2017-10-231-1/+1
| | | | what could possibly go wrong
* Fix typo when getting app nameErik Johnston2017-06-061-1/+1
|
* Fix wrong number of argumentsErik Johnston2017-06-061-1/+1
|
* Only load jinja2 templates onceErik Johnston2017-05-221-12/+44
| | | | | Instead of every time a new email pusher is created, as loading jinja2 templates is slow.
* Fix emailpusher importDavid Baker2016-05-161-1/+11
| | | | Try importing at the root level rather than conditionally importing, as per comment
* spell out emailpusher full pathMatthew Hodgson2016-05-051-1/+1
|
* pep8David Baker2016-05-041-0/+1
|
* copyrightMatthew Hodgson2016-05-041-0/+22
|
* Only import email pusher if email notifs are onDavid Baker2016-04-281-6/+8
|
* First bits of emailpusherDavid Baker2016-04-191-1/+3
| | | | Mostly logic of when to send an email
* Make pushers use the event_push_actions table instead of listening on an ↵David Baker2016-04-061-0/+10
event stream & running the rules again. Sytest passes, but remaining to do: * Make badges work again * Remove old, unused code