Max Mazurov
Max Mazurov
Blocked by https://github.com/emersion/go-smtp/issues/147
The up-to-date spec is RFC 8617 (https://datatracker.ietf.org/doc/rfc861). Also see https://tools.ietf.org/html/draft-ietf-dmarc-arc-usage-07 for usage recommendations.
Implementation considerations I see. Also plan for actions if somebody wants to get that into maddy. Of course that first needs to have library support in go-msgauth. That likely involves...
Removing from 0.1 milestone. Despite being a standard (RFC 5321), many services and email stack implementations do not support it. I do not see a practical reason to bother bending...
Extensions merged into IMAP4rev2 specification: - UNSELECT (#342) - UIDPLUS (blocked by #322) - ESEARCH (create issue) - SEARCHRES (create issue) - ENABLE (go-imap-enable, needs merging) - SASL-IR :heavy_check_mark: -...
postgrey uses SHA1(sender subnet (/24 or /64), normalized sender address, recipients list) as a greylist key. Sender address is stripped of VERP and BATV tags.
Is there anything in the stderr? go-imap should log the actual error that caused the connection to close.
>But then how to handle extensions? Then we can't get [third-party extensions implementation](https://github.com/foxcpp/go-sqlmail/tree/dev/imap/children) because they often need to parse custom commands. So I don't think it's a good idea.
To be honest, I am not familiar with either of these technologies. Probably?
>It would be nice to have a list of when we're allowed to send each type of unilateral update AFAIK, will check RFCs later: - FLAGS, EXISTS, RECENT can be...