Repository navigation
Releases
Releases · jackson-asmith/keel
keel 1.1.1
Fixed
- Overlapping sends in one process could resend a message after a 504. The Graph SDK's retry settings are shared by every runspace in a process, for example under
ForEach-Object -Parallel. When twoSend-Emailcalls overlapped, one could restore SDK retries while the other's request was going out, so the SDK resent it after a 504. The last send to finish also left SDK retries turned off for the rest of the process. Sends through the SDK now take a process-wide lock around changing and restoring those settings, so they run one at a time. A send that waits more than 5 minutes for the lock fails without sending, and SMTP fallback still applies. (#12)
Scripts that send from one runspace at a time, and sends that use an access token directly, aren't affected.
keel.Http has no changes; it's at 1.1.1 because both modules share a version.
keel 1.1.0
What's new
Send-Emailgains three new parameters:-Port— override the SMTP port (defaults to 587)-UseSsl— control SSL/TLS explicitly-Priority— set message priority (Low / Normal / High)
- Improved documentation for
PortandUseSslbehaviour - Additional negative-path test coverage for
-Port
keel 1.0.0
First release of keel: PowerShell modules for unattended automation that sends email and calls REST APIs.
keel.Mail 1.0.0
Send-Email sends mail through Microsoft Graph by default, with Send-MailMessage-style parameters.
- Graph authentication: an access token, an existing Microsoft Graph SDK session, or app-only sign-in with a certificate or client secret.
- SMTP: explicit SMTP delivery, or SMTP fallback when Graph refuses a message or can't be reached.
- No duplicate sends: retries and fallback happen only when the failure proves Graph didn't accept the message. When delivery is uncertain,
Send-Emailstops with aGraphDeliveryUnknownerror instead of risking a second copy. The Graph SDK's own retries are turned off for each send for the same reason. - Attachments: one or more files, checked against Graph's 3 MB inline limit before anything is sent.
- Host configuration: defaults for routing, credentials, Cc, and Reply-To come from
KEEL_*environment variables, so many scripts on a host can be reconfigured in one place. Explicit parameters always win. - Supports
-WhatIfand-Confirm.
keel.Http 1.0.0
Vendor-neutral retry helpers for REST calls.
Invoke-WithBoundedRetry: exponential backoff with jitter, a configurable list of retryable status codes, andRetry-Aftersupport.Get-RetryableStatusCode: reads the HTTP status from errors raised byInvoke-RestMethod,Invoke-WebRequest, and the Graph SDK, across PowerShell versions.
Requirements
- Windows PowerShell 5.1 or PowerShell 7+.
- For Graph delivery: the
Mail.Sendapplication permission, plus an access token orMicrosoft.Graph.Authentication.
On Windows PowerShell 5.1, SMTP delivery can't set a Reply-To header, because 5.1's Send-MailMessage has no -ReplyTo parameter. The message is sent without it and a warning is written.
Documentation
- README: installation, usage, environment variables, and testing.
- ADR 0001: why configuration comes from environment variables.
- ADR 0002: why keel never resends after an ambiguous Graph failure.
Tested on Ubuntu, macOS, and Windows with PowerShell 7, and on Windows PowerShell 5.1.