mailserver-test | shell scripts created to test a mailserver 's setup | Email library
kandi X-RAY | mailserver-test Summary
kandi X-RAY | mailserver-test Summary
The Mailserver-Test scripts are designed to connect to the mail-server to verify its configuration. These scripts do not aim to be full-featured email clients. The smtp-test script can be used to verify that emails cannot be sent without SMTP authentication to avoid an open relay. It can also be used to verify the correct setup of StartTLS on the SMTP server. Incoming emails to the SMTP server can be simulated as well by defining the recipient email to an email address locally handled by the mail server. It can be a handy little script to verify SMTP setup without typing the SMTP commands manually into a telnet session. The imap-test script can be used to check the configuration of an IMAP server and its authentication settings. To make use of the full functionality of this script it is suggested that there should be an email in the INBOX as the script will fetch the first email from the IMAP server. It can be a handy little script to verify a server's setup without typing the IMAP commands manually into the telnet session.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mailserver-test
mailserver-test Key Features
mailserver-test Examples and Code Snippets
Community Discussions
Trending Discussions on mailserver-test
QUESTION
We use TeamCity as a build server and git for source control. When we build release packages I would like to update the password
for imapClientConfiguration
in TeamCity and not have to do it manually. Risking having production passwords in Git does not seem like a good idea but TeamCity is more restricted and having it as a password parameter there is OK.
My question now is how I can get the value from a Team City parameter and transform it into my application.config file? Transforming other values I use SlowCheetah.
My understanding is that you should add it as a parameter under System Properties
and then somehow pick it up during build. At the moment we use Visual Studio runner.
application.config
...ANSWER
Answered 2017-Feb-27 at 13:14Ended up with the following solution:
Add passwords and other information you do not wan't in Git, for example license keys as configuration parameters.
Now add a new file to git, I added a file called PasswordChange.ps1
.
Add a new build step before the actual build and select PowerShell as runner type. Run the script from a file and set Script file to match the path of your newly created file. Add script arguments like this -imapPassword %imapPassword%
In application.Release.config
set the value for password
to __imap_password_placeholder__
or something similar.
Then update your script with the following information:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install mailserver-test
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page