When moving files between buckets or “folders” with Amazon’s command line interface, aws s3, it would be great to be able to skip files already at the destination preventing overwrites and wasted bandwidth. Unfortunately, there is no documented feature for aws s3, but s3cmd does have this feature.
You cannot “skip-existing” files with aws s3 command line interface.
The message undelivered returned email from Office 365 [onmicrosoft.com] is a mailer-daemon equivalent mailing system which notifies the sender of the delivery issues. These issues can range from user-not-found to mailbox full, or attachment rejections. If you are having trouble with this message, leave a detailed comment at the bottom!
Here is an example rejection email from Office365 for an invalid user on an enterprise domain name.
The address may be misspelled or may not exist. Try one or more of the following:
Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link “To send this message again, click here.” Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don’t select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they’ve set up is working correctly.
This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn’t exist at the destination domain. The error is reported by the recipient domain’s email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don’t fix the problem, and you’re the email admin for the recipient, try one or more of the following:
The email address exists and is correct – Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories – If you have a hybrid environment and are using directory synchronization make sure the recipient’s email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule – Check for forwarding rules that aren’t behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Recipient has a valid license – Make sure the recipient has an Office 365 license assigned to them. The recipient’s email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit).
Mail flow settings and MX records are not correct – Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384)
Original Message Headers
Received: from SN2PR17CA0028.namprd17.prod.outlook.com (10.169.188.166) by
BLUPR17MB0130.namprd17.prod.outlook.com (10.160.190.26) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
15.1.860.13; Mon, 30 Jan 2017 15:07:01 +0000
Received: from CO1NAM03FT055.eop-NAM03.prod.protection.outlook.com
(2a01:111:f400:7e48::206) by SN2PR17CA0028.outlook.office365.com
(2603:10b6:804:1a::38) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12 via
Frontend Transport; Mon, 30 Jan 2017 15:07:01 +0000
Authentication-Results: spf=softfail (sender IP is 18.104.22.168)
smtp.mailfrom=rehmann.co; kinesissurvey.com; dkim=fail (signature did not
dmarc=none action=none header.from=rehmann.co;
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
rehmann.co discourages use of 22.214.171.124 as permitted sender)
Received: from us-smtp-1.mimecast.com (126.96.36.199) by
CO1NAM03FT055.mail.protection.outlook.com (10.152.81.162) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id
15.1.888.7 via Frontend Transport; Mon, 30 Jan 2017 15:07:00 +0000
Received: from mail-ot0-f177.google.com (mail-ot0-f177.google.com
[188.8.131.52]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id
us-mta-133-_r7Wi_YoNH2ngwqioJp7JQ-1; Mon, 30 Jan 2017 10:06:56 -0500
Received: by mail-ot0-f177.google.com with SMTP id f9so244090514otd.1
for <[email protected]com>; Mon, 30 Jan 2017 07:06:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
X-Received: by 10.157.45.73 with SMTP id v67mr10051697ota.202.1485788815621;
Mon, 30 Jan 2017 07:06:55 -0800 (PST)
To: <[email protected]com>
From: Luke R <[email protected]>
Date: Mon, 30 Jan 2017 07:06:55 -0800
Message-ID: <CALub9Fd7Cb=TLa_7ZxHCndhA211hg7qK6w4aVeUjBZrYn[email protected]>
spf=softfail (spfCheck: transitioning domain of rehmann.co does not designate 184.108.40.206 as permitted sender) client-ip=220.127.116.11; envelope-from=[email protected]; helo=mail-ot0-f177.google.com
Content-Type: text/plain; charset="UTF-8"
Return-Path: [email protected]
———- Forwarded message ———-
From: Luke R <[email protected]>
To: <[email protected]nesissurvey.com>
Date: Mon, 30 Jan 2017 07:06:55 -0800
This message was automatically generated by Gmail.
GoogleWebLight, as you may see in your referral traffic as “googleweblight.com” optimizes web traffic for slow 2G / 3G connections. When Google detects a user is browsing the web with a slow connection and they are about to access a content-heavy page, the user will then be redirected to https://googleweblight.com/?lite_url=http://example.com where example.com is the original URL. Google’s support page for this product is here.
See The GoogleWebLight Version Of Any URL [WebLight Tester]:
“Google shows faster, lighter pages to people searching on slow mobile connections in selected countries. To do this, we transcode (convert) web pages on the fly into a version optimized for slow networks, so that these pages load faster while saving data.”
How to prevent your site from being shown in GoogleWebLight Version?
If you do not want your pages to be transcoded, set the HTTP header “Cache-Control: no-transform” in your page response. If Googlebot sees this header, your page will not be transcoded.
Please note that pages that opt-out of being transcoded will be labeled in search results to indicate to users that they may take longer to load and may use more data.
To prepare your Kalm with Kava Concentrate is quite simple. Just add half the bottle to 8 or so ounces of juice, water, or smoothie. Each bottle is 2 ounces. A serving size is 1 ounce.
For those who don’t have superhuman vision, here are the ingredients in the January 2017 batch of Kalm with Kava Guava Concentrate
Serving Size 1 oz (30 ml) – add to 7oz of water
Amount per Serving
% of Daily Value
Servings per container:
3 grams / 1% DV
103 mg / 171% DV
*Daily Value Not Established
*Contains 15% Alcohol from Extraction
Other Ingredients: Natural Flavors, Citric Acid, Sodium Benzoate, Potassium Sorbate, Sucralose, Yellow 6, Red 40
Manufactured by Monsoon Beverates LLC, Billings, MT
FDA Disclaimer: This product is not intended to diagnose, prevent, treat, or cure any disease and has not been evaluated by the FDA. Excessive Consumption may impair one’s ability to drive or operate heavy equipment. Not recommended for pregnant or nursing women. Ask a healthcare professional before use if you have or have had liver problems, frequently use alcohol, or are taking any medication.
On a personal note, I’m quite disappointed this concentrate includes Sodium Benzoate, Potassium Sorbate, Sucralose, Yellow 6 and Red 40. Vitamin E and Vitamin C make great alternative preservatives, sucralose should be replaced by Stevia Extract, and the colorings are completely unnecessary (how about annatto extract for the same color but naturally?)
After raising this concern with Monsoon Beverages, here is their reply:
Thanks for your business and feedback! Yes, the current formulation is not ideal and our only product that is not 100% natural. Unfortunately it has proved very difficult to produce the concentrate as 100% natural but I assure you we are working hard at it! Natural colors notoriously have settling issues that affect the appearance of the drink. We’ve tried all the usual options like turmeric, beet root, etc to no avail but have recently made a break-through with some newer natural ingredients. Kava is very unique being a botanical that is hard to work with for shelf stability as well. Citric acid actually changes the effectiveness and stability of certain kavalactones but we have some food scientists looking into other options.
In short, this is an issue that is very important to us and we’re very close to making some changes to get rid of the ingredients you’ve mentioned. Hoping to roll out a new formula in the next couple of months.
Thanks again for your message and please let us know if you have any other comments/questions!
The data files will remain here for archival purposes.
The zip file contains 3 files:
StationAliases.txt 4MB | 64,138 Lines
Header: Organization ID Station ID Station Name Station Alias Station Alias Type
StationWeights.txt 44.2 MB | 702,574 Lines
Organization ID Station ID Station Name Project ID Location Weighting Factor Location Weighting Factor Unit Location Statistical Stratum Text Location Category Location Status Reference Location Type Reference Location Start Date Reference Location End Date Citation ID
Stations.txt 358.5 MB | 798,964 Lines
Header: Org ID Beach ID/Project ID Station ID Station Name Org Name Primary Type Secondary Type S/G/O Indicator Well Number Well Name Pipe Number NAICS Code Spring Type Improvement Permanence USGS Geologic Unit Code-Name Spring Other Name USGS Lithologic Unit Code-Name Location Point Type Point Sequence Number Point Name Latitude Longitude Horizontal Datum Converted Latitude Converted Longitude Converted Horizontal Datum Geopositioning Method Horizontal Accuracy Map Scale Elevation Elevation Unit Elevation Datum Elevation Method Country Name State County Hydrologic Unit Code Hydrologic Unit Name Generated Hydrologic Unit Code Generated Hydrologic Unit Name RF1 Segment Code RF1 Segment Name RF1 Mileage On Reach Ind NRCS Watershed ID Primary Estuary Secondary Estuary Other Estuary Name Great Lake Name Ocean Name Tribal Land Indicator Natv American Land Name FRS Key Identifier Description Text Well Type Aquifer Name Formation Type Well Hole Depth Measure Well Hole Depth Measure Unit Station Document/Graphic Name Station Document/Graphic URL HUC Twelve Digit Code Generated HUC Twelve Digit Code Last Change Date User ID Last Change Last Trans
There were 61 Unique requests sent for over 220,000,000 lines of data. Here are the links to the original and mirror data files. [check back later, still downloading]