Downloads:
12,430
Downloads of v 3.3.3:
64
Last Update:
17 Mar 2024
Package Maintainer(s):
Software Author(s):
- rnwood
Tags:
smtp4dev tools mail dev- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
smtp4dev
This is not the latest version of smtp4dev available.
- 1
- 2
- 3
3.3.3 | Updated: 17 Mar 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
12,430
Downloads of v 3.3.3:
64
Maintainer(s):
Software Author(s):
- rnwood
smtp4dev 3.3.3
This is not the latest version of smtp4dev available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by rnwood. The inclusion of rnwood trademark(s), if any, upon this webpage is solely to identify rnwood goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install smtp4dev, run the following command from the command line or from PowerShell:
To upgrade smtp4dev, run the following command from the command line or from PowerShell:
To uninstall smtp4dev, run the following command from the command line or from PowerShell:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download smtp4dev --internalize --version=3.3.3 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade smtp4dev -y --source="'INTERNAL REPO URL'" --version="'3.3.3'" [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 smtp4dev -y --source="'INTERNAL REPO URL'" --version="'3.3.3'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install smtp4dev
win_chocolatey:
name: smtp4dev
version: '3.3.3'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'smtp4dev' do
action :install
source 'INTERNAL REPO URL'
version '3.3.3'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller smtp4dev
{
Name = "smtp4dev"
Version = "3.3.3"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'smtp4dev':
ensure => '3.3.3',
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.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved as a trusted package on 17 Mar 2024.
Windows 7/Vista/XP/2003/2010 compatible dummy SMTP server. Sits in the system tray and does not deliver the received messages. The received messages can be quickly viewed, saved and the source/structure inspected. Useful for testing/debugging software that generates email.
$ErrorActionPreference = 'Stop';
$packageName= 'smtp4dev'
Write-Verbose "Removing shim"
Uninstall-BinFile `
-Name $packageName
Log in or click on link to see number of positives.
- smtp4dev.3.3.3.nupkg (7881ac15df6b) - ## / 61
- Rnwood.Smtp4dev-win-x64-3.3.3.zip (0199d8e23c1f) - ## / 62
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 |
---|---|---|---|---|
smtp4dev 3.6.1 | 457 | Thursday, May 16, 2024 | Approved | |
smtp4dev 3.6.0 | 59 | Tuesday, May 14, 2024 | Approved | |
smtp4dev 3.5.1 | 88 | Monday, May 6, 2024 | Approved | |
smtp4dev 3.4.1-ci20240505100 | 18 | Sunday, May 5, 2024 | Approved | |
smtp4dev 3.4.0 | 109 | Sunday, April 28, 2024 | Approved | |
smtp4dev 3.3.6 | 54 | Monday, April 22, 2024 | Approved | |
smtp4dev 3.3.5.1 | 62 | Friday, April 19, 2024 | Approved | |
smtp4dev 3.3.4 | 201 | Tuesday, March 19, 2024 | Approved | |
smtp4dev 3.3.3 | 64 | Sunday, March 17, 2024 | Approved | |
smtp4dev 3.3.2 | 126 | Monday, February 26, 2024 | Approved | |
smtp4dev 3.3.1 | 88 | Sunday, February 25, 2024 | Approved | |
smtp4dev 3.1.4 | 1555 | Saturday, May 14, 2022 | Approved | |
smtp4dev 3.1.3.2 | 1680 | Saturday, April 24, 2021 | Approved | |
smtp4dev 3.1.2 | 239 | Thursday, April 1, 2021 | Approved | |
smtp4dev 3.1.1.2 | 116 | Thursday, April 1, 2021 | Approved | |
smtp4dev 3.1.1.1 | 645 | Wednesday, November 18, 2020 | Approved | |
smtp4dev 2.0.10 | 2718 | Friday, June 1, 2018 | Approved | |
smtp4dev 2.0.9.1 | 3502 | Wednesday, June 20, 2012 | Approved | |
smtp4dev 2.0.9 | 627 | Thursday, May 31, 2012 | Approved |
Copyright (c) 2009-2018, smtp4dev project contributors
This package has no dependencies.
Ground Rules:
- This discussion is only about smtp4dev and the smtp4dev 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 smtp4dev, 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.