Skip to content

Ability to use pop in cron jobs #160

Description

@bulters

Is your feature request related to a problem? Please describe.
When I use pop in a script that runs in a cronjob, I get the error below:

Error: could not open a new TTY: open /dev/tty: no such device or address
Usage:
  pop [flags]
  pop [command]

Available Commands:
  completion  Generate completion script
  help        Help about any command

Flags:
  -a, --attach strings           Email's attachments
      --bcc strings              BCC recipients
  -b, --body string              Email's contents
      --cc strings               CC recipients
  -f, --from string              Email's sender ($POP_FROM)
  -h, --help                     help for pop
      --preview                  Whether to preview the email before sending
  -r, --resend.key string        API key for the Resend.com ($RESEND_API_KEY) (default "re_iCM73SeX_2121qYr3iumHRZMDS2afHKD6")
  -x, --signature string         Signature to display at the end of the email. ($POP_SIGNATURE)
  -e, --smtp.encryption string   Encryption type of the SMTP server (starttls, ssl, or none) ($POP_SMTP_ENCRYPTION)
  -H, --smtp.host string         Host of the SMTP server ($POP_SMTP_HOST)
  -i, --smtp.insecure            Skip TLS verification with SMTP server ($POP_SMTP_INSECURE_SKIP_VERIFY)
  -p, --smtp.password string     Password of the SMTP server ($POP_SMTP_PASSWORD)
  -P, --smtp.port int            Port of the SMTP server ($POP_SMTP_PORT) (default 587)
  -U, --smtp.username string     Username of the SMTP server ($POP_SMTP_USERNAME)
  -s, --subject string           Email's subject
  -t, --to strings               Recipients
  -u, --unsafe                   Whether to allow unsafe HTML in the email body, also enable some extra markdown features (Experimental)
  -v, --version                  version for pop

Use "pop [command] --help" for more information about a command.

Describe the solution you'd like
Allow passing a parameter (e.g. --no-tty/-n) that will result in pop doing it's thing and only outputting errors to STDERR.

Describe alternatives you've considered
Running the script as a daemon, but this goes against the concept of using cron jobs for scheduling tasks.

Additional context
N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions