ukr.net mail
ukr.net · Storage · 2 records · JSON
- UKR.NET Mail — 100 GB per single message, 1024 attachments/message Storagecaveatemailno cardIper-object-capdisagrees
- ukr.net mail Storagefails: quotaemail?card?Rdisagrees
UKR.NET Mail — 100 GB per single message, 1024 attachments/message Storage
caveatemailno cardIper-object-capdisagrees
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 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 |
| Per-object cap | per-object-cap claimed 100 GB (100000000000 bytes) |
| Retention | not stated |
| Egress | Unmetered by provider; mailbox service, no transfer billing. |
| Identity | email derived from the record's prose, not from an identity field, and no signup was executed: und anywhere in this niche — 40x Yahoo's APPENDLIMIT and 3x Outlook's SMTP SIZE. The 100 GB claim is a docs statement with no probe evidence behind it and one plausible unit error (Гб |
| 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. |
| Binding | per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota |
| 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. |
| Notes | 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. |
| Evidence rung | inferred One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-20 |
| 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 | withheld | probe: openssl s_client -connect imap.ukr.net:993 -> * OK IMAP4 ready; CAPABILITY has no APPENDLIMIT |
Unknown or withheld values (5)
$.evidence[2].urlprivate-url$.free_tier.notesprocess$.per_object_cap.notesnot-extracted$.retention.notesnot-extracted$.retention.statednot-extracted
ukr.net mail Storage
fails: quotaemail?card?Rdisagrees
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 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 n unit none; metered on none |
|---|---|
| Price | none stated |
| Per-object cap | not recorded |
| Retention | not recorded |
| Egress | not recorded |
| Identity | email (placeholder) not published |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | unknown |
| Tooling | not recorded |
| Composes with | 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 n |
| Notes | 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 |
| Evidence rung | reported |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
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 n",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (15)
$.chainingnot-recorded$.confidence_notewithheld$.egress.termsnot-recorded$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.identity_cost.detaildefaulted$.identity_cost.kindidentity-defaulted$.interfaceinterface-unknown$.interface_detailwithheld$.limits_noteprocess$.per_object_cap.notesnot-recorded$.per_object_cap.statednot-recorded$.retention.notesprocess$.retention.statednot-recorded$.toolingnot-recorded