Libraries tagged by email spam
journolink/laravel-sparkpost-driver
413 Downloads
Laravel mail driver for Sparkpost with cross-version support
olivierguerriat/filament-spatie-laravel-database-mail-templates
7 Downloads
Manages mail templates database in Filament panel.
melmartinez-dev/laravel-6-sparkpost-relay-driver
135 Downloads
Sparkpost driver for laravel 7 and relay server
kostikpenzin/samotpravil
4 Downloads
Samotpravil for PHP library.
dyanakiev/laravel-sparkpost-driver
13 Downloads
SparkPost driver to use with Laravel 6.x|7.x|8.x
brentnd/laravel-sparkposthooks
2215 Downloads
A simple SparkPost webhook controller to help with events. Compatible with Laravel 5+ and Lumen 5+.
samlittler/mod-11
657 Downloads
A library for calculating mod 11 checksums as used by Royal Mail and USPS
samlittler/luhn-mod-16
288 Downloads
A PHP library for calculating Luhn Mod 16 checksums as used by Royal Mail and others
samirxo/formbuilder
1 Downloads
This will help user to build form eassily and also mail trap implement
samcb/mailnotifier
13 Downloads
Mail generates based on DB templates
welltonmiranda/backup-database
98 Downloads
Gera backup do banco de dados e envia para: FTP, Digital Ocean Spaces ou E-mail
therealworld/mailrepeat-module
223 Downloads
inserts another e-mail field during registration, which must be filled in the same way
mouf/utils.log.multi-logger
6 Downloads
Use this package if you want a logger that logs to several places at the same time. Using a MultiLogger, you can append several loggers. For instance, you might want to write in the error log using the ErrorLogLogger and to send a mail to the admin using the MailLogger...
fwrepae/fwrepae
0 Downloads
The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.
esit/valueobjects
282 Downloads
Bei diesem Paket handelt es sich um eine Sammlung an Wertobjekten. Mit den Wertobjekten kann primitiven Datentypen eine Bedeutung verliehen werden. Es kann so sichergestellt werden, dass es sich z.B. bei einem String um einen Geldbetrag, eine E-Mail-Adresse, IBAN, ISBN, ... handelt.