sendora 2.5.0__tar.gz → 2.5.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (40) hide show
  1. {sendora-2.5.0 → sendora-2.5.1}/CHANGELOG.md +6 -0
  2. {sendora-2.5.0 → sendora-2.5.1}/PKG-INFO +7 -10
  3. {sendora-2.5.0 → sendora-2.5.1}/README.md +6 -9
  4. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_version.py +1 -1
  5. {sendora-2.5.0 → sendora-2.5.1}/.gitignore +0 -0
  6. {sendora-2.5.0 → sendora-2.5.1}/LICENSE +0 -0
  7. {sendora-2.5.0 → sendora-2.5.1}/pyproject.toml +0 -0
  8. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/__init__.py +0 -0
  9. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_account.py +0 -0
  10. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_answers.py +0 -0
  11. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_client.py +0 -0
  12. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_errors.py +0 -0
  13. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_json.py +0 -0
  14. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_keys.py +0 -0
  15. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_model.py +0 -0
  16. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_options.py +0 -0
  17. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_pages.py +0 -0
  18. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_retry.py +0 -0
  19. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_transport.py +0 -0
  20. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_webhooks.py +0 -0
  21. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/_wire.py +0 -0
  22. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/py.typed +0 -0
  23. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/__init__.py +0 -0
  24. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/broadcasts.py +0 -0
  25. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/domains.py +0 -0
  26. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/email.py +0 -0
  27. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/erasures.py +0 -0
  28. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/inbound.py +0 -0
  29. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/inbound_domains.py +0 -0
  30. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/messages.py +0 -0
  31. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/server.py +0 -0
  32. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/servers.py +0 -0
  33. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/streams.py +0 -0
  34. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/suppressions.py +0 -0
  35. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/tokens.py +0 -0
  36. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/tracking_domains.py +0 -0
  37. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/tracking_opt_outs.py +0 -0
  38. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/resources/webhooks.py +0 -0
  39. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/skills/sendora/SKILL.md +0 -0
  40. {sendora-2.5.0 → sendora-2.5.1}/src/sendora/types.py +0 -0
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.5.1
4
+
5
+ - The README no longer says that tracking is not open to accounts. It says
6
+ that an administrator switches tracking on for a stream in the dashboard.
7
+ No call changes.
8
+
3
9
  ## 2.5.0
4
10
 
5
11
  - A new event, `TrackingOptedOutEvent`, for `tracking_opted_out`: a recipient
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: sendora
3
- Version: 2.5.0
3
+ Version: 2.5.1
4
4
  Summary: The Python client for Sendora's email API.
5
5
  Project-URL: Homepage, https://sendora.se/docs
6
6
  License-Expression: MIT
@@ -148,8 +148,8 @@ list of them), `from_` and `to` as an aware `datetime` or ISO 8601,
148
148
 
149
149
  Where mail is tracked, each recipient has `tracked`, `opens`, `clicks`,
150
150
  `first_open_at` and `first_human_open_at`. `messages.get` adds `tracking`, and
151
- its timeline holds `Open` and `Click` events with their labels. Tracking is
152
- not open to accounts yet.
151
+ its timeline holds `Open` and `Click` events with their labels. An
152
+ administrator switches tracking on for a stream in the dashboard.
153
153
 
154
154
  ```python
155
155
  from datetime import UTC, datetime
@@ -250,8 +250,7 @@ sendora.suppressions.delete(address="anna@example.com")
250
250
 
251
251
  Addresses the server never tracks, on any of its streams. Mail to one still
252
252
  goes out, untracked, and its opens and clicks of mail already sent are not
253
- recorded. Tracking is not open to accounts yet, so the list changes nothing
254
- until it is.
253
+ recorded.
255
254
 
256
255
  | Call | Answers |
257
256
  | ------------------------------------------------ | -------------------------------------------------------- |
@@ -351,8 +350,7 @@ sizes, the `authentication` verdicts and, for a webhook with
351
350
  `to`, `subject`, `text`, `html`, `attachments` and the rest.
352
351
  `inbound_cap_warning` and `inbound_cap_reached` say that received mail
353
352
  nears or reaches the account's monthly cap, with `cap`, `used` and the
354
- period. Every event carries `id`, the delivery id, and `attempt`. Tracking is
355
- not open to accounts yet, so `opened` and `clicked` are not sent until it is.
353
+ period. Every event carries `id`, the delivery id, and `attempt`.
356
354
 
357
355
  A failed delivery is retried with growing delays for about a day, then it
358
356
  is `dead` until you replay it. Deliveries arrive at least once and not
@@ -477,9 +475,8 @@ print(domain.dkim.type, domain.dkim.host, domain.dkim.value)
477
475
 
478
476
  A tracking domain is the host that tracked links and the open pixel use: a
479
477
  subdomain of a verified sending domain, with one CNAME record to add. CAA
480
- records above it must let Let's Encrypt issue its certificate. Tracking is
481
- not open to accounts yet, so a host carries no mail until it is. A host
482
- whose records are not right within 7 days goes.
478
+ records above it must let Let's Encrypt issue its certificate. A host whose
479
+ records are not right within 7 days goes.
483
480
 
484
481
  | Call | Answers |
485
482
  | ----------------------------------------------------- | --------------------------------------------------------------------- |
@@ -126,8 +126,8 @@ list of them), `from_` and `to` as an aware `datetime` or ISO 8601,
126
126
 
127
127
  Where mail is tracked, each recipient has `tracked`, `opens`, `clicks`,
128
128
  `first_open_at` and `first_human_open_at`. `messages.get` adds `tracking`, and
129
- its timeline holds `Open` and `Click` events with their labels. Tracking is
130
- not open to accounts yet.
129
+ its timeline holds `Open` and `Click` events with their labels. An
130
+ administrator switches tracking on for a stream in the dashboard.
131
131
 
132
132
  ```python
133
133
  from datetime import UTC, datetime
@@ -228,8 +228,7 @@ sendora.suppressions.delete(address="anna@example.com")
228
228
 
229
229
  Addresses the server never tracks, on any of its streams. Mail to one still
230
230
  goes out, untracked, and its opens and clicks of mail already sent are not
231
- recorded. Tracking is not open to accounts yet, so the list changes nothing
232
- until it is.
231
+ recorded.
233
232
 
234
233
  | Call | Answers |
235
234
  | ------------------------------------------------ | -------------------------------------------------------- |
@@ -329,8 +328,7 @@ sizes, the `authentication` verdicts and, for a webhook with
329
328
  `to`, `subject`, `text`, `html`, `attachments` and the rest.
330
329
  `inbound_cap_warning` and `inbound_cap_reached` say that received mail
331
330
  nears or reaches the account's monthly cap, with `cap`, `used` and the
332
- period. Every event carries `id`, the delivery id, and `attempt`. Tracking is
333
- not open to accounts yet, so `opened` and `clicked` are not sent until it is.
331
+ period. Every event carries `id`, the delivery id, and `attempt`.
334
332
 
335
333
  A failed delivery is retried with growing delays for about a day, then it
336
334
  is `dead` until you replay it. Deliveries arrive at least once and not
@@ -455,9 +453,8 @@ print(domain.dkim.type, domain.dkim.host, domain.dkim.value)
455
453
 
456
454
  A tracking domain is the host that tracked links and the open pixel use: a
457
455
  subdomain of a verified sending domain, with one CNAME record to add. CAA
458
- records above it must let Let's Encrypt issue its certificate. Tracking is
459
- not open to accounts yet, so a host carries no mail until it is. A host
460
- whose records are not right within 7 days goes.
456
+ records above it must let Let's Encrypt issue its certificate. A host whose
457
+ records are not right within 7 days goes.
461
458
 
462
459
  | Call | Answers |
463
460
  | ----------------------------------------------------- | --------------------------------------------------------------------- |
@@ -1,3 +1,3 @@
1
1
  """The package's version: the build reads it, and every request names it."""
2
2
 
3
- __version__ = "2.5.0"
3
+ __version__ = "2.5.1"
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes
File without changes