Email Delivery. This executed Agreement (and executed counterparts of this Agreement), may be delivered by email.
Email Delivery. Any notice sent by electronic mail must have been acknowledged by the recipient as having been received before the notice is deemed to have been given.
Email Delivery. This executed Agreement (and executed counterparts of this Agreement), may be delivered by email to Xxxxxx Xxx at Xxxxxx@xxxxxx.xxx for Transferor, and to the Director of Housing, with copies to Office of Economic Development and City Attorney for Transferee. Any party may change its recipients for purposes of this Section by giving notice to the other party as provided in Section 5 above.
Email Delivery. VIPRE will attempt delivery of 100% of all Qualified Email delivered to the VIPRE systems. An email will not be considered lost unless Customer can prove that the email reached VIPRE’s systems and that the email server to which VIPRE attempted delivery was fully functional when delivery was attempted. Table 1 applies.
Email Delivery. Delivery of a copy of this Agreement together with an executed signature page of a counterpart (in AdobeTM Portable Document Format (PDF), JPEG or other agreed format) sent by email shall take effect as delivery of a duly signed counterpart of this Agreement.
Email Delivery. FuseMail will attempt delivery of 100% of all Qualified Email delivered to the FuseMail systems. An email will not be considered lost unless Customer can prove that the email reached FuseMail’s systems and that the email server to which FuseMail attempted delivery was fully functional when delivery was attempted. Table 1 applies.
Email Delivery. This Service Level measupsres the ability to deliver email messages to or from Barracupsda’s servers. Barracupsda agrees that youps will be able to deliver email messages to and from Barracupsda Essentials email servers, if youps have pupsrchased the relevant supsbscription, at least 99.9% of the time each calendar month, provided however that downtime or oupstages related to any server on the Internet, cupsstomer premise equpsipment, transportation of data across the Internet, or any periods dupsring schedupsled or emergency maintenance windows or cupsstomer-requpsested service interrupsptions are not inclupsded within the scope of, and are exclupsded from, this availability commitment (“Email Delivery Commitment”). Additionally, the service levels will not apply to following circupsmstances: • To emails containing attachments that cannot be scanned (i.e., encrypted or password protected attachments). • The implementation by Cupsstomer of excessively complex fupsll text content policies. • To emails sent by Cupsstomer to large external distribupstion lists, which may be supsbject to serialized delivery. • Cupsstomer or third party inability to access the primary or backupsp MX hosts servers dupse to a failing in the Internet. • Virupsses introdupsced to Cupsstomer’s systems by Cupsstomer. • Problems caupssed by mail servers that are not RFC-822 compliant.
Email Delivery. This Service Level measures the ability to deliver email messages to or from Barracuda’s servers. Barracuda agrees that you will be able to deliver email messages to and from Barracuda’s Email Gateway Defense email servers, if you have purchased the relevant subscription, at least 99.9% of the time each calendar month, provided however that downtime or outages related to any server on the Internet, customer premise equipment, transportation of data across the Internet, or any periods during scheduled or emergency maintenance windows or customer-requested service interruptions are not included within the scope of, and are excluded from, this availability commitment (“Email Delivery Commitment”). Additionally, the service levels will not apply to following circumstances: • To emails containing attachments that cannot be scanned (i.e., encrypted or password protected attachments). • The implementation by Customer of excessively complex full text content policies. • To emails sent by Customer to large external distribution lists, which may be subject to serialized delivery. • Customer or third-party inability to access the primary or backup MX hosts servers due to a failing in the Internet. • Viruses introduced to Customer’s systems by Customer. • Problems caused by mail servers that are not RFC-822 compliant.
