Download the PHP package initphp/mailer without Composer
On this page you can find all versions of the php package initphp/mailer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package mailer
Mailer
This is a simple library for sending mail with SMTP consisting of a single class.
Instalation
Requirements
- PHP 7.4 or higher
- MBString Extension
- Iconv Extension
- FileInfo Extension
Usage
Methods
newInstance()
Creates a new mailer object and returns it.
clear()
setHeader()
setFrom()
setReplyTo()
setTo()
setCC()
setBCC()
setSubject()
setMessage()
setAttachmentCID()
setAltMessage()
setMailType()
$type:textorhtml
setWordWrap()
setProtocol()
$protocol:mail,sendmailorsmtp
setPriority()
$n: An integer between 1 and 5 inclusive.
setNewline()
setCRLF()
attach()
send()
printDebugger()
Getting Help
If you have questions, concerns, bug reports, etc, please file an issue in this repository's Issue Tracker.
Getting Involved
All contributions to this project will be published under the MIT License. By submitting a pull request or filing a bug, issue, or feature request, you are agreeing to comply with this waiver of copyright interest.
There are two primary ways to help:
- Using the issue tracker, and
- Changing the code-base.
Using the issue tracker
Use the issue tracker to suggest feature requests, report bugs, and ask questions. This is also a great way to connect with the developers of the project as well as others who are interested in this solution.
Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in the issue that you will take on that effort, then follow the Changing the code-base guidance below.
Changing the code-base
Generally speaking, you should fork this repository, make changes in your own fork, and then submit a pull request. All new code should have associated unit tests that validate implemented features and the presence or lack of defects. Additionally, the code should follow any stylistic and architectural guidelines prescribed by the project. In the absence of such guidelines, mimic the styles and patterns in the existing code-base.
Credits
License
Copyright © 2022 MIT License
All versions of mailer with dependencies
ext-mbstring Version *
ext-iconv Version *
ext-fileinfo Version *