ukr.net mail
ukr.net · 2 records in Storage · JSON
Records 2
- caveatUKR.NET Mail — 100 GB per single message, 1024 attachments/message
Storagefree tieridentity email?card?limit per-object-capevidence inferredstale on 2026-11-21disagrees
- fails: quotaukr.net mail
Storageidentity email?card?evidence reportedstale on 2026-11-05disagrees
Sibling records disagree:
- verdict:
storage/ukr-net-mailsays fails-quota, storage/ukr-net-mail-100-gb-per-single-message-1024-attachments says qualifies-with-caveat
- Free allowance
- Help wiki states verbatim: "До кожного листа можна прикріпити до 1024 вкладень, однак пам'ятайте, що загальний розмір листа разом з усіма вкладеннями не повинен перевищувати 100 Гб." = up to 1,024 attachments per message, and the total message size including all attachments must not exceed 100 GB.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-capper-object-cap claimed 100 GB
- Evidence
- inferred3 sources; reasoned from other evidence
- Freshness
- stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21
| Free tier | Help wiki states verbatim: "До кожного листа можна прикріпити до 1024 вкладень, однак пам'ятайте, що загальний розмір листа разом з усіма вкладеннями не повинен перевищувати 100 Гб." = up to 1,024 attachments per message, and the total message size including all attachments must not exceed 100 GB. If that figure is real it is the largest per-object cap found anywhere in this niche — 40x Yahoo's APPENDLIMIT and 3x Outlook's SMTP SIZE. unit GB; metered on unstated |
|---|---|
| Price | none stated |
| Limits |
per-object-cap claimed 100 GB/message (unverified — no APPENDLIMIT in CAPABILITY, so the server may reject below that). Actual mailbox byte quota not published. IMAP requires a generated app password; the account password is refused. |
| Identity | email (inferred, not read) not published |
| Egress | Unmetered by provider; mailbox service, no transfer billing. |
| Per-object cap | per-object-cap claimed 100 GB (100000000000 bytes) |
| Retention | not stated |
| Interface | rest rest |
| Tooling | IMAP with app-specific passwords (account password blocked for IMAP since 2020-02-18). probe-verified live: imap.ukr.net:993 -> * OK IMAP4 ready / * CAPABILITY IMAP4rev1 IDLE ID XLIST NAMESPACE AUTH=PLAIN. Requires enabling IMAP in settings and generating a per-app password. |
| Composes with | Byte quota per account is not published at all — only the per-message cap. If the 100 GB/message figure holds, a handful of accounts covers 10 TiB; if it is a unit typo the real cap is likely 100 MB and the provider collapses to noise. This needs an authenticated test before it is counted. |
| Reliability | The 100 GB claim is a docs statement with no probe evidence behind it and one plausible unit error (Гб vs Мб); do not size anything against it until an authenticated APPEND succeeds. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | wiki.ukr.net/WorkWithMessages | "до 1024 вкладень ... не повинен перевищувати 100 Гб", read live 2026-10-21 |
| 2026-10-21 | wiki.ukr.net/ManageIMAPAccess | IMAP enabled + app password required since 2020-02-18 |
| 2026-10-21 | source not published | probe: openssl s_client -connect imap.ukr.net:993 -> * OK IMAP4 ready; CAPABILITY has no APPENDLIMIT |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read
ukr.net mail
StorageSibling records disagree:
- verdict:
storage/ukr-net-mailsays fails-quota, storage/ukr-net-mail-100-gb-per-single-message-1024-attachments says qualifies-with-caveat
- Free allowance
- Fixed-country dial code on the registration form: the phone field is pre-set to '+380' with the note 'На цей номер ми надішлемо код підтвердження' we will send a confirmation code to this…
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Fixed-country dial code on the registration form: the phone field is pre-set to '+380' with the note 'На цей номер ми надішлемо код підтвердження' we will send a confirmation code to this… unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
| Reliability | Fixed-country dial code on the registration form: the phone field is pre-set to '+380' with the note 'На цей номер ми надішлемо код підтвердження' (we will send a confirmation code to this… |
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | accounts.ukr.net/registration | Fixed-country dial code on the registration form: the phone field is pre-set to '+380' with the note 'На цей номер ми надішлемо код підтвердження' we will send a confirmation code to this n |
More fields 1
| dead end | {"failure_class": "quota","why": "Fixed-country dial code on the registration form: the phone field is pre-set to '+380' with the note 'На цей номер ми надішлемо код підтвердження' (we will send a confirmation code to this…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field