nextmail support
Every command in this namespace, with its arguments, flags and examples.
Commands
Write to the people who build Nextmail, as the contact page does. The reply goes by email to the account behind the client.
Every command here also takes the global flags, such as --json, --profile and --dry-run. See the global flags
nextmail support send
Write to Nextmail support
Usage
nextmail support send --topic <value> --message <value> [flags] nextmail support send --data <json|@file|-> [flags]
Sends a message to the people who build Nextmail, as the contact page does for somebody signed in. The name and the address the reply goes to come from the account behind the client: the workspace owner for an API key, and the person who connected the app for an access token. The workspace is named in the message, so support knows which one it is about.
Flags
--topic <value>What it is about in a few words, up to 64 characters, such as
Bug reportorDomains & DNS. Required, here or in--data.--message <value>The message itself, up to 8,000 characters. Required, here or in
--data.--data <json|@file|->The whole
bodyas JSON, inline, from a file with @path, or - for standard input. Flags override its keys.
Examples
nextmail support send --topic 'Bug report' --message 'Scheduled sends to one address stay queued since this morning.'nextmail support send --data @support.jsonAlso available in
- API
POST /support- TypeScript
nextmail.support.send()- Python
support.send()- Ruby
support.send- PHP
support->send- Go
Support.Send- Java
support().send- C#
Support.SendAsync
Google Workspace