Email Delivery Sample Clauses

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.
Sample 1Sample 2Sample 3
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.
Sample 1Sample 2
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.
Sample 1Sample 2
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.
Sample 1
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.
Sample 1
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.
Sample 1
AutoNDA by SimpleDocs

Related to Email Delivery

  • Mail Service The Union shall be permitted to use the State inter and intra-office paper mail system. This usage shall be limited to matters that involve the Union and the Employer. It is not to be used for the purpose of mass mailings to membership and/or bargaining unit employees. The Employer agrees not to open employee union mail when clearly marked as such. Where security is of concern, the mail shall be opened in the presence of the addressee. When feasible, and where equipment is currently available, Union stewards and/or officers may utilize electronic mail and/or facsimile equipment solely for contract enforcement and interpretation and grievance processing matters. Such transmissions will be primarily to expedite communication regarding such matters, will be reasonable with respect to time and volume, and limited to communications with the grievant, if any, appropriate supervisors and employee’s staff representatives. Long distance charges which may be incurred must be approved prior to transmission.

  • Transmission The Custodian and the Fund shall comply with SWIFT’s authentication procedures. The Custodian will act on FT Instructions received via SWIFT provided the instruction is authenticated by the SWIFT system. § Written Instructions. Instructions may be transmitted in an original writing that bears the manual signature of an Authorized Person(s).

  • pdf The vendor must download the Vendor Agreement from the attachment tab, fill in the requested information and upload the completed agreement. DO NOT UPLOAD encrypted or password protected files.

  • Email You acknowledge that we are able to send electronic mail to you and receive electronic mail from you. You release us from any claim you may have as a result of any unauthorised copying, recording, reading or interference with that document or information after transmission, for any delay or non-delivery of any document or information and for any damage caused to your system or any files by a transfer.

  • Transmission encryption All data transmissions of DHCS PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Electronic Delivery The Company may, in its sole discretion, decide to deliver any documents related to the Award or other awards granted to the Participant under the Plan by electronic means. The Participant hereby consents to receive such documents by electronic delivery and agrees to participate in the Plan through an on-line or electronic system established and maintained by the Company or a third party designated by the Company.

  • Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.

  • Facsimile Where any Notice is provided or submitted to a Party via facsimile, an original of the Notice sent via facsimile shall promptly be sent by regular mail. For greater certainty, a notice given via facsimile shall not be invalid by reason only of a Party’s failure to comply with this Section 11.2.

  • Email Notice Any reference in this Agreement to “written notice” shall include notice by email, where there is reasonable certainty that such email notice originated either from a valid OANDA email address, or from the email address registered to your Account, as the case may be, and may be relied upon as valid and authentic written communication.

Time is Money Join Law Insider Premium to draft better contracts faster.