Run: 2026-03-12-01KKHZS3DM1EE386BVY5026RRD

john.doe@example.com,jane@smith-family.net,support@company.co.uk,info@subdomain.example.org ## Explanation The extraction first scans the provided text for candidate strings that contain the mandatory @ separator dividing a local-part from a domain. Only those satisfying basic syntactic requirements (non-empty local-part, at least one dot-separated label in the domain, and no leading @) are retained as valid. The five candidates are evaluated sequentially: john.doe@example.com passes because its local-part and example.com domain meet the criteria; jane@smith-family.net qualifies with a valid local-part and hyphen-allowed domain; support@company.co.uk is accepted as the domain contains the permissible two-level suffix .co.uk; info@subdomain.example.org satisfies the rule with its three-level subdomain structure. In contrast, not.an.email.com is rejected for lacking an @ symbol, and @missing-username.com is discarded because its local-part is empty. The retained addresses are emitted in strict textual order, delimited by commas with no intervening whitespace to satisfy the output specification.