SubmissionEmailGateway
Corex\Mail\SubmissionEmailGateway · interface · Core layer
Optional Email Studio operations consumed by the core-neutral Submissions domain.
Public API
Section titled “Public API”readiness(): ReplyReadiness
Section titled “readiness(): ReplyReadiness”What sending a reply from this site would do now: deliver it, keep it, or refuse it. Asked before a reply is written, so the reply box can say so (spec 106, FR-028). It must be the decision {@see reply()} acts on, not a second reading of the same settings.
reply(string $recipient, string $subject, string $htmlBody, ?ReplyConversation $within): MailResult
Section titled “reply(string $recipient, string $subject, string $htmlBody, ?ReplyConversation $within): MailResult”conversation(string $recipient, array $attemptIds): ReplyConversation
Section titled “conversation(string $recipient, array $attemptIds): ReplyConversation”The emails this site sent one person that a reply can be sent under, among the attempts named (spec 106, FR-038). Empty where none of them can be: a reply is then a new email.
preview(string $recipient, string $subject, string $htmlBody): array
Section titled “preview(string $recipient, string $subject, string $htmlBody): array”The email {@see reply()} would send for the same three values, and sends nothing. It must be built by what builds the sent one, so that what a person approves is what the recipient gets (spec 106, FR-005).