mail-tracker | Package for Laravel to inject tracking code into outgoing emails

 by   jdavidbakr PHP Version: 7.6 License: MIT

kandi X-RAY | mail-tracker Summary

kandi X-RAY | mail-tracker Summary

mail-tracker is a PHP library. mail-tracker has no vulnerabilities, it has a Permissive License and it has low support. However mail-tracker has 18 bugs. You can download it from GitHub.

Package for Laravel to inject tracking code into outgoing emails.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              mail-tracker has a low active ecosystem.
              It has 463 star(s) with 117 fork(s). There are 14 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 2 open issues and 156 have been closed. On average issues are closed in 48 days. There are 2 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of mail-tracker is 7.6

            kandi-Quality Quality

              mail-tracker has 18 bugs (0 blocker, 0 critical, 10 major, 8 minor) and 82 code smells.

            kandi-Security Security

              mail-tracker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              mail-tracker code analysis shows 0 unresolved vulnerabilities.
              There are 28 security hotspots that need review.

            kandi-License License

              mail-tracker is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              mail-tracker releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi has reviewed mail-tracker and discovered the below as its top functions. This is intended to give you an instant insight into mail-tracker implemented functionality, and help decide if they suit your requirements.
            • Create trackers
            • Install the package s routes .
            • Get smtp info
            • Get sent emails
            • Get a transparent image
            • Handle a request
            • Migrate sent email .
            • Register the sent emails .
            • Handle transient messages .
            • Get the connection name .
            Get all kandi verified functions for this library.

            mail-tracker Key Features

            No Key Features are available at this moment for mail-tracker.

            mail-tracker Examples and Code Snippets

            No Code Snippets are available at this moment for mail-tracker.

            Community Discussions

            Trending Discussions on mail-tracker

            QUESTION

            Laravel delaying emails breaks links
            Asked 2020-Sep-11 at 08:29

            I need to send e-mails with a delay of a couple hours. Everything I create in the construct function of my mailable works: image links, pulling stuff from the database, ...

            The mails look good but the only weird thing is that all the outgoing links appear to be broken.

            In a mail without a delay the link looks like this: https://example.url.com/

            In a mail with delay it looks like this: http://localhost/email/n?l=https%3A%2F%2Fexample.url.com&h=Kv1wny2TTU8RhdgPUXQEDpX8xHdKavz1

            I have no idea why these links transform to this... I tested it without a delay and everything works like it should.

            I use the delay like this:

            ...

            ANSWER

            Answered 2020-Sep-11 at 08:29

            The APP_URL in my .env file was 'http://localhost' so mail-tracker used that to transform the tracked links.

            Once I changed it to the correct url, it worked fine

            Source https://stackoverflow.com/questions/63693785

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install mail-tracker

            In 4.x and previous, there was a recipient column in the sent_emails table that stored the RFC standard email format <Name> email@example.com. 5.x has updated to store the name and email separately. The recipient and sender columns have been removed from the sent_emails table migration, but no migration was added to drop those columns. Accessors have been added to retain the model's recipient and sender attributes, so no updates should need to be made to any code that currently uses those unless you are specifically querying the sender or recipient columns. To retain your existing data afer upgrading, run the artisan command mail-tracker:migrate-recipients. This will convert the existing recipient and sender data into the new format. At this point you may drop the recipient and sender columns. There is also a new pair of attributes in the sent_emails table: opened_at and clicked_at. Those store the first time the user opened and clicked, respectively. This has been added to the default tracker index page. You are welcome to add it into yours, or use those values as you see fit.
            There are no breaking changes from 3.x to 4.x with the exception that 4.x is for Laravel 7+ only.
            There was a breaking change with the update to version 3.0, specifically regarding the events that are fired. If you are listening for the PermanentBouncedMessageEvent to catch all undeliverables, there are now two separate events: PermanentBouncedMessageEvent will be fired only on permanent bounces, and a new event ComplaintMessageEvent will be fired on complaints. There is also an new event EmailDeliveredEvent that is fired for each successful delivery event. For information about setting up the SES/SNS environment to receive notifications regarding these events, see the documentation below.
            First, upgrade to version 2.2 by running:. If you are updating from an earlier version, you will need to update the config file and run the new migrations. For best results, make a backup copy of config/mail-tracker.php and the views in resources/views/vendor/emailTrackingViews (if they exists) to restore any values you have customized, then delete that file and run. Also note that the migration for the sent_emails_url_clicked table changed with version 2.1.13. The change is that the URL column is now a TEXT field to allow for longer URLs. If you have an old system you may want to manually change that column; there is no migration included to perform that update.
            Publish the config file and migration. Note: If you would like to use a different connection to store your models, you should update the mail-tracker.php config entry connection before running the migrations.

            Support

            Please see CONTRIBUTING and CONDUCT for details.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/jdavidbakr/mail-tracker.git

          • CLI

            gh repo clone jdavidbakr/mail-tracker

          • sshUrl

            git@github.com:jdavidbakr/mail-tracker.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link