" New Feature Announcements Archives - LuxSci

Archive for the ‘New Feature Announcements’ Category

New From LuxSci: Updates to the WebMail Portal

Monday, July 17th, 2023

LuxSci is pleased to announce that the first phase of design and user experience improvements has been deployed on the LuxSci WebMail portal.

In the first phase of updates, you will notice significant changes to the main navigation and organization of the portal. These developments reflect our commitment to:

  • Supporting customers’ business workflows and processes
  • Streamlining the administrative experience
  • Improving ease of use for customers of all technical backgrounds
  • Providing an accessible online experience
  • Modernizing our brand

Over the next few months, we will continue to iterate on these changes and introduce additional updates. If you have any questions about the new interface, please contact our support team. Thank you for partnering with LuxSci and trusting us to secure your data.

New Feature Announcement: Automated Reporting with Webhooks

Monday, February 27th, 2023

The LuxSci team is pleased to announce the release of automated reporting with webhooks to help organizations manage their data workflows. These updates will allow administrators to push information and analytics from their email campaigns into existing dashboards or to email recipients in close to real time. 

“Webhooks give us the ability to receive real-time notifications and events from LuxSci in bulk, which will streamline our internal analysis, reporting, and, therefore, decision-making,” said Katie Ali, Product Manager at Signify Health. 

“Today, our analysis is limited due to the number of resources we have on hand to pull email data. Now that we are implementing webhooks, we can start to automate the analytic process from end to end. Webhooks also eliminate the complexity of a reoccurring polling logic to achieve the same effect.” 

automated reporting webhooks

What are Webhooks?

A webhook is an HTTP request triggered by an event in a source system and sent to a destination system. In other words, webhooks push data to the customer’s website URL for processing.

LuxSci’s webhooks are available for all our API reports, including email sending, delivery status changes, email opens, email clicks, login failures, and unsubscribes.

In addition to traditional webhooks that post data to a URL, LuxSci also allows API reports to be automatically sent via TLS-encrypted email to any email address at a custom frequency. The report data is attached to the email in JSON, CSV, or HTML format. 

Why are LuxSci’s Webhooks Useful? 

Webhooks allow customers to automatically push information about email events via LuxSci’s API as they are happening without pulling from the API. That allows customers to record and review this information and take timely action based on these events. 

LuxSci’s webhooks are incredibly scalable, unlike those of many other providers. Instead of sending one webhook notification to the customer for each event (which could be millions of notifications a day), LuxSci sends a digest of all events that happened over a specified period. By sending a digest instead of individual notifications, it is easier to process the notifications at scale. Batching the notifications reduces the server resources the customer requires to receive and process high volumes of webhooks by a significant amount.

Our webhooks are also resilient to customer webhook processing service failure. LuxSci will automatically retry webhook delivery when customer processing servers are down or failing, so events are less likely to be lost than webhooks provided by other services.

How to Set Up Automated Reporting with Webhooks

Login to your LuxSci account and visit the Report section of the user interface. In the sidebar, select Automated Reports. First, you will need to select the data you want to report. Choose from API reports including:

  • Emails sent
  • Delivery status updates
  • Emails opened
  • Emailed links clicked
  • SMTP login failures
  • Email addresses suppressed or unsubscribed
  • Emails marked as spam

Then select the data source (either SMTP/API or WebMail). The reports can include account-wide events or can be restricted to only certain users. Name the report and how frequently you want to check for new events. Webhooks reporting is configurable to any desired granularity from once every minute to once a day.

Reports will only be sent when there are new events. For example, a report with five-minute intervals checks for new events every five minutes but only sends a report if there are new events.

Finally, choose how the data should be delivered (via a webhook or email with TLS encryption) and in what format for email reports (JSON, HTML, or CSV). Enter an email address to notify if there are errors with the report, and then you can enable it.

Automated reports can be further customized by using parameters. For example, they help limit reporting to specific domains, campaigns, or email headers. Please contact our team today to learn more about how LuxSci’s Automated Reporting can enhance your data workflows. 

New Feature: API Priority Queue

Tuesday, November 22nd, 2022

Maximize efficiency by employing our new email-sending prioritization features. Secure High Volume Email customers utilizing APIs for sending can now set a message priority to determine the order in which messages are sent out.

email api priority queue

What is the API Priority Queue Feature?

This feature allows customers to set a priority on email messages sent via API. Customers can pass an optional parameter in their API to set the message priority on a scale of 0 – 9. Zero is the lowest priority, nine is the highest, and four is the default priority setting.

The API priority queue feature allows customers to send out higher-priority messages faster when the sending queue is already long.

Why is the API Priority Queue Useful?

Traditionally, all customer emails were processed in a “first come, first serve” method. Customers can now use the priority queue to determine the sending order when they simultaneously send transactional and marketing messages via the API.

For example, time-sensitive password resets could be stuck in the queue while a large blast of marketing emails is transmitted. Depending on the size of the email list and server capacity, the password reset email could be held up for several minutes to even hours. This situation is unacceptable for many business use cases.

Customers can designate transactional emails as high-priority with the API priority queue feature enabled. When transactional emails are given a high-priority status, they can jump the line and go out before less time-sensitive emails like marketing messages.

How to Utilize the API Priority Queue

This feature is only available to Secure High Volume Email customers utilizing APIs to send emails. It does not work for SMTP sending. Customers can add the optional parameter and desired value while crafting their API call to send emails. Additionally, customers can use the API configuration editor in the LuxSci UI to change the default priority value for all messages. You can review the details of our API by going to: https://luxsci.com/rest-api.html.

New from LuxSci: Accessibility Updates to SecureLine Escrow and SecureSend Portals

Tuesday, August 23rd, 2022

LuxSci is happy to announce that new accessibility features are now enabled in the SecureLine Escrow and SecureSend portals. These enhancements improve the portals’ usability and provide a more inclusive experience for people with disabilities. Everyone should be able to use the internet, and proper accessibility guarantees that.

accessibility updates

What is Accessibility?

The Americans with Disabilities Act (ADA), passed in 1990, helps ensure that anyone with a disability will receive the same opportunities as an individual without a disability. Some of the most visible changes included requiring new buildings have wheelchair ramps and accessible bathrooms. However, this law does not exclusively apply to physical infrastructure but also to online services. Poor technology implementations should not prevent people from accessing information online.

The Web Content Accessibility Guidelines (WCAG) were developed by the World Wide Web Consortium (W3C) to make accessibility more manageable for web designers and developers. The W3C is an international community that develops regulations and recommendations for the internet to help ensure its longevity and usability. The W3C established the WCAG standards to provide detailed guidelines for creating websites, digital content, and markup through accessible approaches that work seamlessly with assistive technologies used by people with disabilities.

Accessibility Updates to the LuxSci SecureLine Escrow and SecureSend Portals

LuxSci primarily serves the healthcare industry, and equal access to health information is critical. Everyone should be able to access important information about their health status online. We worked with compliance experts to update the SecureSend and SecureLine Escrow portals to comply with WCAG 2.1 AA standards. We are continuing to improve the accessibility of our website to ensure we provide equal access to all our users. LuxSci is committed to making our SecureSend website as accessible as possible to people with disabilities, including those with visual, hearing, cognitive, and motor impairments.

Don’t hesitate to contact customer service with any specific questions or concerns about the accessibility of any particular web page or feature. We will respond to feedback within ten business days. We thank you for your assistance in enhancing the accessibility of our website, and we look forward to serving your needs!

New Feature: Custom Bounce Domains

Tuesday, July 26th, 2022

LuxSci has introduced a new feature to improve reporting for bounced transactional and marketing messages. The new “Custom Bounce Domains” feature allows administrators to set a custom domain for bounce processing that will not break DMARC.

custom bounce domains

What is DMARC?

DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. It protects users from forged emails and instructs the email provider on what to do with messages that fail SPF or DKIM. Implementing DMARC is highly recommended to help stop suspicious messages from reaching inboxes.

Why Custom Bounce Domains are Needed

However, implementing SPF and DMARC records can sometimes cause issues for transactional and marketing messages. To understand why let’s look at how DMARC verifies SPF records.

The Return-Path specifies the email address where bounced email messages should be sent if there are unable to be delivered. It is usually the same domain as the sender’s email address. However, when sending marketing or transactional emails, the Return-Path email address is often different from the sender for various tracking and reporting reasons.

If the Return-Path address does not match the domain or subdomain used in the SPF record, it can cause DMARC to fail, and the bounced messages won’t be routed according to the pre-defined rules.

How to Implement Custom Bounce Domains

Now, our customers can create custom bounce domains to prevent DMARC from failing. To set it up, log in to your account and visit the Account Settings -> Email Custom Bounce Domains. Make sure that the “Bounce Processing” settings are enabled before altering the Custom Bounce Domain setting.

Before adding the new bounce domain to your account, you must create a new CNAME (like bounces.yourdomain.com) in the domain’s DNS settings that points to the new destination. At LuxSci, the default is “returnto.luxsci.com.” Once set up, return to the settings and add the new subdomain to specify the Return-Path. After this is enabled, emails will align with SPF for DMARC since the sender’s domain and Return-Path domain match.

Questions? Please contact our support team for more information on enabling these settings.