Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

9,730

Downloads of v 0.8.0-dev-5:

736

Last Update:

10 Nov 2018

Package Maintainer(s):

Software Author(s):

  • Inveigle.net

Tags:

cmail commandline mail freeware

CMail

This is a prerelease version of CMail.

  • 1
  • 2
  • 3

0.8.0-dev-5 | Updated: 10 Nov 2018

Downloads:

9,730

Downloads of v 0.8.0-dev-5:

736

Maintainer(s):

Software Author(s):

  • Inveigle.net

CMail 0.8.0-dev-5

This is a prerelease version of CMail.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Inveigle.net. The inclusion of Inveigle.net trademark(s), if any, upon this webpage is solely to identify Inveigle.net goods or services and not for commercial purposes.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install CMail, run the following command from the command line or from PowerShell:

>

To upgrade CMail, run the following command from the command line or from PowerShell:

>

To uninstall CMail, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade cmail -y --source="'INTERNAL REPO URL'" --version="'0.8.0-dev-5'" --prerelease [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade cmail -y --source="'INTERNAL REPO URL'" --version="'0.8.0-dev-5'" --prerelease
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install cmail
  win_chocolatey:
    name: cmail
    version: '0.8.0-dev-5'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'cmail' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.8.0-dev-5'
  options  '--prerelease'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller cmail
{
    Name        = "cmail"
    Version     = "0.8.0-dev-5"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'cmail':
  ensure          => '0.8.0-dev-5',
  install_options => ['--prerelease'],
  provider        => 'chocolatey',
  source          => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

WARNING

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

Description

CMail is a freeware command line e-mail sending tool for Windows, primarily intended for sending scripted e-mail, but it is simple enough to be used interactively. If you are looking for an alternative to Blat with SSL support, or more control over message formatting, CMail may be a good choice.

CMail is not intended to be a better Blat, it was developed to assist with testing mail server and content analysis software, and as such has evolved with a completely different feature set. While being very easy to use in its basic form, CMail provides advanced options for those who require them, allowing users to specify such things as the encoding mechanism for the message body and individual attachments, the types of authentication mechanisms to use, aliases for all recipients (similar software often doesn't support aliases, or can only send to a single user), and per-recipient Delivery Status Notification settings. Users can also control various aspects of the SMTP session, including enforcing the use of SSL/TLS where security is a consideration, setting the HELO/EHLO, adding custom headers, and mandating the use of IPv4 or IPv6.

Features

  • IPv6 support.
  • TLS/SSL via STARTTLS or SMTPS (SSL-enabled version). Built-in, stunnel not required.
  • Support for adding multipart/alternative HTML message bodies (UTF-8) and embedded images.
  • Delivery Status Notification and Message Disposition Notification (Read receipt) support.
  • SMTP authentication using CRAM-MD5, PLAIN, and LOGIN.
  • Message bodies using plain text, base64, or quoted printable encoding.
  • Unlimited attachments using base64, quoted printable, uuencoding or yEnc.
  • Wildcard attachment support to attach directory content.
  • Unlimited To/Cc/Bcc recipients, with aliases and DSN options for each if desired.
  • Read message body from command line, stdin or file.
  • Sending via SOCKS or HTTPS proxies.
  • Flexible configuration via files or the command line.
  • Written entirely in C - no need for .NET libraries, Java, or other prerequisites.
  • No installation required. Download, extract, use.
  • Free for private and commercial use.

legal\LICENSE.txt
CMail is provided as-is, free of charge. It may be used for both personal or commercial purposes, and be distributed without restriction, provided the software remains unmodified. Please ensure any acknowlegements in ThirdParty.txt (SSL-enabled version only at present) are preserved.
legal\ThirdParty.txt
-- LibreSSL license --

  LibReSSL files are retained under the copyright of the authors. New
  additions are ISC licensed as per OpenBSD's normal licensing policy,
  or are placed in the public domain.

  The OpenSSL code is distributed under the terms of the original OpenSSL
  licenses which follow:

  LICENSE ISSUES
  ==============

  The OpenSSL toolkit stays under a dual license, i.e. both the conditions of
  the OpenSSL License and the original SSLeay license apply to the toolkit.
  See below for the actual license texts.  In case of any license issues
  related to OpenSSL please contact [email protected].

  OpenSSL License
  ---------------

/* ====================================================================
 * Copyright (c) 1998-2011 The OpenSSL Project.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.
 *
 * 3. All advertising materials mentioning features or use of this
 *    software must display the following acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
 *
 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
 *    endorse or promote products derived from this software without
 *    prior written permission. For written permission, please contact
 *    [email protected].
 *
 * 5. Products derived from this software may not be called "OpenSSL"
 *    nor may "OpenSSL" appear in their names without prior written
 *    permission of the OpenSSL Project.
 *
 * 6. Redistributions of any form whatsoever must retain the following
 *    acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
 *
 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 * OF THE POSSIBILITY OF SUCH DAMAGE.
 * ====================================================================
 *
 * This product includes cryptographic software written by Eric Young
 * ([email protected]).  This product includes software written by Tim
 * Hudson ([email protected]).
 *
 */

 Original SSLeay License
 -----------------------

/* Copyright (C) 1995-1998 Eric Young ([email protected])
 * All rights reserved.
 *
 * This package is an SSL implementation written
 * by Eric Young ([email protected]).
 * The implementation was written so as to conform with Netscapes SSL.
 *
 * This library is free for commercial and non-commercial use as long as
 * the following conditions are aheared to.  The following conditions
 * apply to all code found in this distribution, be it the RC4, RSA,
 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
 * included with this distribution is covered by the same copyright terms
 * except that the holder is Tim Hudson ([email protected]).
 *
 * Copyright remains Eric Young's, and as such any Copyright notices in
 * the code are not to be removed.
 * If this package is used in a product, Eric Young should be given attribution
 * as the author of the parts of the library used.
 * This can be in the form of a textual message at program startup or
 * in documentation (online or textual) provided with the package.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *    "This product includes cryptographic software written by
 *     Eric Young ([email protected])"
 *    The word 'cryptographic' can be left out if the rouines from the library
 *    being used are not cryptographic related :-).
 * 4. If you include any Windows specific code (or a derivative thereof) from
 *    the apps directory (application code) you must include an acknowledgement:
 *    "This product includes software written by Tim Hudson ([email protected])"
 *
 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 *
 * The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
 */
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://www.inveigle.net/cmail/download.shtml>
and can be verified by doing the following:

1. Download the following:
  32-Bit software: <https://www.inveigle.net/downloads/CMail_0.8.0_x86-dev-5.zip>
  64-Bit software: <https://www.inveigle.net/downloads/CMail_0.8.0_amd64-dev-5.zip>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum32: 627A183B8DFBDEDF954B4060C44EA4B48B00A31F148A65E430A56641098B3F80
  checksum64: A3FA7A4A2B7F811D31D44949FDF58A79A955CA77902DCB491D84F18D045B225D

The file 'LICENSE.txt' has been obtained from their FAQ located at <https://www.inveigle.net/cmail/faq.shtml>
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  fileType    = 'zip'
  file        = "$toolsPath\CMail_0.8.0_x86-dev-5.zip"
  file64      = "$toolsPath\CMail_0.8.0_amd64-dev-5.zip"
  destination = "$toolsPath"
}

Get-ChocolateyUnzip @packageArgs
Remove-Item $toolsPath\*.zip -ea 0
tools\CMail_0.8.0_amd64-dev-5.zip
md5: 0747B5912D0113FCA40155AC4D074984 | sha1: BC41727C49DB1BB68A0BCDF9B3840F8A39567ABA | sha256: A3FA7A4A2B7F811D31D44949FDF58A79A955CA77902DCB491D84F18D045B225D | sha512: D03ED079D63E76DE6B11385316DC9F055C8234C55031EBC463F828F009BD44644C7ACC5754603C8C52A470E25AE18703DC7EA3E0D85EE906859175D72423C9D5
tools\CMail_0.8.0_x86-dev-5.zip
md5: 286CE9076C4D00FEBE018E10BC29D20E | sha1: DBF1C99B94B1A2949AA315194D47B54549B1B8FD | sha256: 627A183B8DFBDEDF954B4060C44EA4B48B00A31F148A65E430A56641098B3F80 | sha512: A6B661B7194ADDDC11FED20249173A8D94A4B274BFEF6FE6B5766CA6C139689DCAA380E36FBABE3DB35EA970F871D9D05656A63D552DFAE173628A50BDFB6158

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
CMail 0.8.10 168 Monday, March 11, 2024 Approved
CMail 0.8.9 544 Tuesday, September 5, 2023 Approved
CMail 0.8.8 114 Thursday, July 27, 2023 Approved
CMail 0.8.7 534 Friday, May 19, 2023 Approved
CMail 0.8.6 795 Tuesday, September 27, 2022 Approved
CMail 0.8.5 294 Friday, May 20, 2022 Approved
CMail 0.8.4 779 Monday, January 3, 2022 Approved
CMail 0.8.3 668 Tuesday, January 12, 2021 Approved
CMail 0.8.0-dev-9 872 Friday, July 19, 2019 Exempted
CMail 0.8.0-dev-8 519 Thursday, July 18, 2019 Exempted
CMail 0.8.0-dev-7 341 Sunday, February 17, 2019 Exempted
CMail 0.8.0-dev-6 501 Tuesday, November 20, 2018 Exempted
CMail 0.8.0-dev-5 736 Saturday, November 10, 2018 Exempted
CMail 0.8.0-dev-4 281 Thursday, July 26, 2018 Exempted
CMail 0.8.0-dev-3 299 Monday, July 2, 2018 Exempted
CMail 0.8.0-dev-2 329 Tuesday, May 15, 2018 Exempted
CMail 0.7.9.1 1002 Tuesday, May 15, 2018 Approved
Cmail 0.7.9 450 Tuesday, August 8, 2017 Approved

This package has no dependencies.

Discussion for the CMail Package

Ground Rules:

  • This discussion is only about CMail and the CMail package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or CMail, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus