File: /home/robovet/mail/new/1671222116.M192057P1566261.host40.registrar-servers.com,S=3521,W=3599
Return-Path: <>
Delivered-To: [email protected]
Received: from host40.registrar-servers.com
by host40.registrar-servers.com with LMTP
id yOcOCmTTnGM15hcAJ0Bl1A
(envelope-from <>)
for <[email protected]>; Fri, 16 Dec 2022 15:21:56 -0500
Return-path: <>
Envelope-to: [email protected]
Delivery-date: Fri, 16 Dec 2022 15:21:56 -0500
Received: from mailnull by host40.registrar-servers.com with local (Exim 4.95)
id 1p6HDQ-006qiq-3o
for [email protected];
Fri, 16 Dec 2022 15:21:56 -0500
X-Failed-Recipients: [email protected]
Auto-Submitted: auto-replied
From: Mail Delivery System <[email protected]>
To: [email protected]
References: <[email protected]>
Content-Type: multipart/report; report-type=delivery-status; boundary=1671222116-eximdsn-1031961930
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <[email protected]>
Date: Fri, 16 Dec 2022 15:21:56 -0500
--1671222116-eximdsn-1031961930
Content-type: text/plain; charset=us-ascii
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[email protected]
No Such User Here
--1671222116-eximdsn-1031961930
Content-type: message/delivery-status
Reporting-MTA: dns; host40.registrar-servers.com
Action: failed
Final-Recipient: rfc822;[email protected]
Status: 5.0.0
--1671222116-eximdsn-1031961930
Content-type: message/rfc822
Return-path: <[email protected]>
Received: from robovet by host40.registrar-servers.com with local (Exim 4.95)
(envelope-from <[email protected]>)
id 1p6HDP-006qiX-QK
for [email protected];
Fri, 16 Dec 2022 15:21:55 -0500
To: [email protected]
Subject: Robovet "Transactional emails"
X-PHP-Script: www.robovet.com/index.php for 5.59.135.26, 5.59.135.26
X-PHP-Filename: /home/robovet/public_html/index.php REMOTE_ADDR: 5.59.135.26
Date: Fri, 16 Dec 2022 20:21:55 +0000
From: Robovet <[email protected]>
Reply-To: [email protected]
Message-ID: <[email protected]>
X-Mailer: PHPMailer 6.5.0 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Sender: <[email protected]>
From: Hermantrord <[email protected]>
Subject: Transactional emails
Message Body:
<a href=https://unione.io/en/blog/transactional-emails-types-and-examples>Transactional emails</a> are the ilk of emails you send to a heiress to facilitate commercial activity. You send it following a commercial matter or in reaction to a certain action performed by way of the recipient. An example is a confirmation email that you send to a person that ordered a effect from your co-op give credence to; this missive lets the heiress be sure that they entered into a valid transaction. Because <a href=https://unione.io/en/blog/transactional-emails-types-and-examples>transactional emails</a> are required to aid pivotal transactions, businesses do not need to capture explicit consent from the receiver to send them, unlike marketing emails where consent is required.
--
This e-mail was sent from a contact form on Robovet (http://www.robovet.com)
--1671222116-eximdsn-1031961930--