Search the Community

If forum participants want to talk about challenge caches, the General Geocaching Topics forum is the place for that. This is the Creating Adventures forum.

I am very interested in this project. I have always been an advocate for Wherigo and I personally have built a lot of them and have helped many others build them as well. While I am not a coder I can test, build, tear apart, and am willing to do whatever necessary to help bring some advancement to this issue. Also, I do have the ability and the platform to get the word out through our Podcast Network (Geocache Talk). this could be handy if we need more testers or builders or just want some feedback. I am very interested in this project. I have always been an advocate for Wherigo and I personally have built a lot of them and have helped many others build them as well. While I am not a coder I can test, build, tear apart, and am willing to do whatever necessary to help bring some advancement to this issue. Also, I do have the ability and the platform to get the word out through our Podcast Network (Geocache Talk). this could be handy if we need more testers or builders or just want some feedback. Memfis Mafia

Greetings from the WISA Woodsat HQ! After the announcement of WISA Woodsat satellite trackable (TB9GB8G) mid August, we have over 6200 people on the watch list! That also means that I have received a fair amount of messages regarding the satellite itself, the procedure of logging it, launch schedule and many others. Unfortunately I am not able to answer them one by one, so, let's talk satellites in this discussion thread. The most common question is, how you can log the satellite trackable. I have added the instructions to the trackable page https://coord.info/TB9GB8G. The thing to note is that you can only do that AFTER the satellite has been launched. The trackable code is only visibile in the photos taken by the satellite itself with its selfie-camera. You can follow WISA Woodsat project progress on https://wisawoodsat.space. We have blogs and videos showing how the satellite materials are made, how they are machined, and tested. You can also find WISA Woodsat on Instagram and Twitter with the handles @wisawoodsat and #wisawoodsat. Anything else you would like to know about the satellite?

When I've introduced people to geocaching, I have never had them create a geocaching.com account or install an app (any app). As kunarion pointed out, that's a lot of finicky technical work, and it's more productive to introduce them to the "finding tupperware in the woods" part of geocaching. When I've taught one-hour classes on geocaching (usually, but not exclusively, to kids at church), I've spent the first half of the class explaining geocaching with as many hands-on examples as possible. Then I've taken everyone outside to a nearby spot where I've hidden a bunch of varied containers, and I've had them raise their hands when they've spotted a hidden container. In the class, I start by explaining that geocaching is like a modern scavenger hunt or game of hide the thimble, using GPS coordinates to show roughly where the container is hidden. (I specifically avoid the term "treasure hunt" because that gives people the wrong idea about what geocaching is.) To demystify GPS, I have three colored strings/ropes hanging from the ceiling. I explain that the GPS device (whether built into a phone or a separate handheld device) measures the precise distance from it to a GPS satellite. I grab one string and show that with one satellite, it defines a circle. Then I grab a second string and show that two satellites define two points, the places where the two circles intersect. I grab the third string and show that three satellites define a single point... except that there's another point "up there" so you have to assume I'm on the ground and not "up there". All this takes just a few minutes. The bulk of the explanation part is explaining and showing them different containers (sizes, types, camouflage), different trade items ("Trade up, trade even, or don't trade."), and different trackables (and that they are NOT trade items). I also explain difficulty and terrain ratings, and I briefly explain that most caches are traditional (a container at the GPS coordinates), but that some are more complicated (multi-caches, puzzles, etc.). By then, it's time to go outside to look for hidden containers. I generally try to have at least one hidden container per kid. If you don't have enough real cache containers, then any recycled jars/bottles covered in camo tape will do. Before the class, I hide them in an area where there are plenty of bushes, trees, and other landscaping features. Vary the hiding spots, and make a few of them really hard. I have the kids stay behind a line and raise their hands when they've spotted a hidden container. I try to call on everyone once before I call on anyone a second time. It's important to have a count of the number of containers hidden, and the number of containers spotted so far. As we get to the end, I let the kids know how many containers are left to find. If we run out of time, then I reveal the ones they missed. The other style of class that I've helped with has met at a trailhead parking lot in a county park. After a brief "chalk talk" explaining the basics (pretty much the same way I described above, without the colored strings/ropes to explain GPS), the new geocachers break up into small groups, with one experienced geocacher assigned to each group as a coach. Each group receives a preprogrammed GPS with real caches hidden along the trail. We used a popular trail that had become naturally saturated with a variety of caches placed by different owners (what we called a "power trail" before the advent of modern numbers trails like the ET Highway trail). Over the course of 2-3 hours, the new geocachers could find an assortment of different caches and be back at the trailhead in time for lunch. The experienced coach in each group was there mainly to answer questions, and to make sure there wasn't any confusion about trackables or replacing the cache as found or things like that.

i know that there are furries all over the world. i am also aware that a few of us geo cache. so i thought this could be a place we could meet and talk on line. so who else is out there * waves*

This water fountains, with the intent of providing water to the population - now or in the past - is definitely something deserving its own category. They are usually interesting, many are historic, pure heritage, and still, no place to place them in Waymarking. From time to time there is some talk about creating a category but so far, nothing came up. Fountains - as far as I can remember - only accept decorative fountains.

A lot depends on who it was that took it. For example, you'd talk very differently to a church custodian who didn't realize it was supposed to be there, than you would to a bored preacher's kid who got into some mischief.

I met pmaupin at the Mega GIFF in 2021, after I saw his signature on another event earlier that day and we had a good talk. I also know that some cachers I've met personally some time ago (in about 100km distance) do some Waymarking - but caching is more on their focus.

I haven't taken the survey yet. Any thoughts from those of you who have? https://www.geocaching.com/blog/2018/12/lets-talk-some-more-about-geocache-quality/

Ethical discussion on collecting countries. I realized a few days ago that it's still possible to visit Russia: Go to Gdansk, take bus to Kaliningrad. Well, it's not that simple. Depending on your home country you need an invitation, insurance and visa, or you need to actually talk to the Russian ambassador to get this visa. In some countries it's not possible anymore at all. But it would theoretically be possible here. How you actually get rouble for your stay is a completely different matter as creditcards might not work. But it's possible. On that note, there are buses from Austria to Ukraine. Just saying. Discuss

We...don't do that here. That's not so much unholy as heretic. We don't talk about Mm-mm, no, no, no! We don't talk about Mm-mm! Grew to live in fear of Mm-mm being mentioned here Newbies post, thread is toast, moderators near I associate Mm-mm with the sound of locking threads (click, click, click) ...

I eagerly anticipated attending an event hosted by a sort of infamous new geocacher who placed hides on private property, had hide coordinates hundreds of feet off, etc. In fact, several of those of us who attended were really interested to meet this person and talk to them about proper hide techniques. The event owner never showed up. Bummer! And hasn't hidden a cache since. And I think all their caches are archived at this point. I still attended the event with several others and we all logged it as attended. The event owner didn't though lol.

Watch it. I love learning. I dislike having to prove it. Weird is pretending you can "place" or "find" these geology quizzes, as if they were something tangible. Weird is that it's mixed in with a game about containers. Weird is that you need landowner permission to "place" nothing at their land. I'm EC-free for well over 10 years now. That hasn't changed. Oh, since they nuked Brass Cap Cache (searching for tangibles), I'm done with virtuals too. I offer the same ridicule for them as the special-case virtuals about geology. EDIT to avoid dragging this out. Nothing weird about events; we talk about finding caches, and don't pretend to "place" or "find" events. I love events.

Unless it's something dangerous, I'd expect it's allowed. AirTags simply use the tracking ability of the phone, and phones are allowed for Geocaching. But I'd prefer an option to shut off "tag trackers". There are many things that Apple either requires or won't allow, that I don't like. And now I've switched back to Android. By default Droid doesn't automatically talk to the tags. The TO's previous "Tile" tracking device traveled from the US to Europe, looks like without issue. For over a year. Until somecacher justified destroying it or hoarding it or "forgetting" it. Whatever. The usual.

For one, rock-climbing courses are generally more accessible than tree-climbing courses. But also, that's not the point. It is in no way a waste of time and money. My goal for the OP is for them to: Get comfortable with ropes, harnesses, belay devices, etc. in a safe, indoor setting before going outside. If they can find anything advertised as "tree-climbing lessons"; great—but I doubt it. Rock climbing lessons are similar enough that they will accomplish this same goal. Take a fall themselves or watch someone take a fall and realize that maybe climbing (anything) is really, really, dangerous. It is not a skill that can just be picked up for the sake of finding some caches; no, it needs to be learned separately. Actually talk to people (face-to-face!) about their goals and reasons, instead of asking random faceless strangers on the internet. Even if climbing gym staff aren't experts on tree climbing, they will be able to say smart things (and possibly even talk OP out of this.)

Great - I have a 'library cache', too that I'm proud of. Still, be careful in your cache writeup. It's easy to slip over the line. You can talk about what's there in the park and the trails they offer, the history, the beauty, the overlooks, but not the giftshop or how they're trying to fight Climate Change. You can say that there's an admission charge to the park if you don't have a membership, but you can't encourage people to GET a membership. You can tell cachers about how as of this year they'll have to pay for parking, but not how pissed off you are about it! You can mention the park's regular events, but not the one who's purpose is to push back against an encroaching housing development! Slippery slope stuff. And, to keep this on topic, as others have said that's not a 'partnership' cache.

But it's much too young compared to town hall of the "Queen of the Hanseatic League", so that modern town hall matches it quite well Just for classification: 50% of our team was born and raised in Lübeck, known as the Queen of the Hanseatic League. Both of us are Lübecker Kaufleute (Lübecks Merchantpeople), so we live in, with and from parts of the Hanseatic League. Churches played a great role at the Hanseatic League as well as the town halls. The most powerfull parts of the Hanseatic League were the merchants, not the kings, dukes. They decided what happend in those cities. Only the clergy had some powers over the merchantmens. Lets talk about that for a while: The City Council (which was 100% made of merchants, no Kings, no Queens, no Noblesse) had their own church which inhabited the city treasure. So if you want the Hanseatic League, you can't decline the churches. City Walls and city gates: The Hanseatic League had it's peak times in the closing mediaval times, where the times where rougher and peace was the exception, so one city had to defend them and their goods, as the City of the Hanseatic League were rich. So city walls and gates were essential for the wealth and so for the groth of the Hanseatic League. Without walls and gates, there wouldn't have been any Hanseatic League.

Are there historical markers or signs that discuss and explain Hanseatic heritage? This looks like just a very cool mural to me, which can go into the Murals Category. Please explain how someone from Texas traveling in Europe would know something they saw along their journey could be waymarked in a possible future Hanseatic Heritage category Let's talk it over

So as not to disappoint my fan base, I've edited the topic title. It seemed easier than urging people to only talk on topic about the Geocache of the Week.

Let's talk, you pick the subject. You will get our two cents worth... and take it with a grain of salt... oops, should have said: Open topic about Waymarking.

Perhaps someone thought there was a lot of value in the tags and that alone, regardless of what you say you were intending to do with them, was enough of a flag for the agent. That's unfortunate. Personally I might keep calling back to talk to someone about them, and hope to speak to a higher up who sympathizes and can find a way to let go of what is effectively other people's property... *shrug*

Sorry for the vague title, I didn't know how else to address this. So, I know there's a lot of talk about Geocaching and YouTube, and there's been a sort of agreement as far as I can tell that as long as you don't really post spoilers about a cache and it's specific location, for the most part all is well. Well, there's a pair of YouTubers whom I occasionally watch called MoreJStu that make all kinds of vlog type videos, several of which have recently included geocaching. At first I had no problem with what they were posting. I figured if it got some more people interested in our hobby, that's great! But then they posted this video today: https://www.youtube.com/watch?v=FEub1s5AXUI There is so much misinformation in it about geocaching that I was nearly yelling at my screen. I think it's okay that they're wanting to share a geocache with the fans, there's nothing wrong with that. Except they show where they pack snacks into the cache and encourage others to come out and trade snacks too. Not only that, but they practically bury the cache. It's one thing to hide it with some foliage, but they literally made a hole to put it in. I'm not here to get them in trouble or anything, but I just hate the fact that they're demonstrating behavior against the rules of Geocaching to their 2.7 million subscribers... They also make it kind of known that in more than one video they usually don't trade swag, only take it. If you look on the comments on their vids, you constantly see things like "Ya'll inspired me to start geocaching!" and "Because of ya'll I'm building a geocache fort!". Which is great, except the majority of their followers are young kids who I know aren't going to read any of the rules before going out and geocaching, which will just create more problems... What are ya'll's thoughts?

There's no difference between the two. A cache type is a cache type as far as the data framework goes. We may talk about other types of cache experiences like puzzle caches or challenge caches or (in some places) an adventure lab considered as one (and this has been discussed before), and even Benchmarks may have been referenced as a cache type by some (showing up in the find count of 'cache types', eg). Doesn't change the fact that something either is or is not a "real" cache type. If it's not, then it has special code if there are places where its usage mimics that of actual cache types (Traditional, Multi, Virtual, Event, Earthcache, etc), like the counts of finds in our stats under "cache types". A Geotour is a category of cache types, not a cache type itself. An Adventure is similar to a Geotour in that it's a wrapper for a set of Adventure Locations. And that's harping back to the initial setup of Adventure Labs, individual 'finds' that added +1 smiley in a separate data source that was wrapped into a user's public stats. So there's already a pseudo-parallel between Geotour and Adventure. But that's a far cry from making Adventures a new actual cache type. Right, however, the structure of an actual cache type is not similar to the structure of an Adventure. And the Adventure experience is its own app, its own functionality, its own framework, and its own code. And that's why I said: it would require a complete overhaul of the Adventure system and importing all the data into the existing geocache system patchworked to make Adventures a new cache type, in some way, which I would think would look absolutely nothing like Adventures do currently... they are simply fundamentally different experiences with functionalities that are miles apart.

@Mangatome Then from your perspective, we have not yet reached the limit of what we can do with lua if done correctly. What will need to be done is the following: The player app should be able to run one version of lua for all v1 cartridges (retaining compatibility, such as it is). We will run all v2 cartridges in the latest version of lua. When the player app requests a cartridge from the Wherigo API, the player app's current lua version will be included in the request. The Wherigo API is responsible for compiling a cartridge with the requested lua version. As long as the Wherigo API is updated prior to releasing an updated version of the app with a newer lua runtime environment, things will work as expected. In this manner, we can also deal with old versions of the app. (The Wherigo API reserves the right to tell the app when it is too old and must be upgraded.) Updates to the player app could include updates to either the lua environment or player app API. Because of this, once we expose an endpoint to a cartridge, it is fixed in stone and cannot be changed. I know how to version web-based APIs, but have not yet put time into determining how to version the player API. (In other words, we need to guarantee cartridges built in 2024 will still be able to run when the year is 2030--or even cartridges created in 2026 using a 2024 version of Urwigo.) I imagine we could just have an interface per player API version, which when upgraded will simply chain call into the newer method. As mentioned above, the Wherigo API's compiler service would need to load the compiler appropriate for the request. (I'll likely store a compiled cartridge when requested for the first time, then skip the compiling step during subsequent requests.) We will need to have living documentation that covers the player app's specification: lua versions, required libraries, and the player API (not only the part that allows interaction with the UI, but also that allows the subset of network features we desire). I would like cartridge state to be kept separate from the lua version if at all possible. I want to work on a more robust state management API. Other thoughts: I certainly don't mind exploring a version of player app that will allow cartridges to be written in C#. You definitely know player apps better than I: how difficult would it be to construct interfaces for the player app such that we could easily drop in different types of cartridges? Even if we stay with lua, that's my intent to preserve compatibility with v1 cartridges while continuing to update lua for v2 (unless we decide each cartridge's manifest can tell the player app the lua version against which it's supposed to run). My first priority is to everyone's security. I still would like to allow authors the ability to use network resources, so how about this idea? When an author wishes to use network resources, their cartridge can undergo review. Once approved, that particular URL scheme will be whitelisted for that cartridge. When a player app downloads a cartridge, it can also download the URL whitelist. The player API will expose a network layer whereby it will only allow whitelisted URLs to be called. In this way, we maintain security while at the same time giving authors the ability to consume network resources. As for in what the player app will be coded, I must leave that up those who will volunteer for the player app. My preference is for the environment to be something in which most people are familiar. That way, when some volunteers have to step away for a while, other people can take up the responsibility with not as much of a learning curve. My preference is MAUI or Blazor Hybrid. I know Groundspeak seems to like React Native (their Adventure Labs app is built using that), but Wherigo v2 is not going to be a Groundspeak project (though I still want Groundspeak's backing). For developing all this, I'll want public GitHub repos with a couple project leads (always more than one since we're all volunteers) set up to review and merge pull requests into the trunk. Anyone in the community can make a pull request. Whether we want these repos initially private is still a good question. I'm glad we're not all jumping into coding this. And some public news: I attended a mega event last weekend, and Jeremy from Groundspeak was there. We'll set up a time to talk with each other and see if I can get Groundspeak to agree to let the Wherigo Foundation run Wherigo if we can deliver.

No, it's the same issue that I described previously. Comcast is now throttling Weekly Mailer messages we attempt to send by deferment, so our server keeps retrying until the message is accepted or expired. In this case, it took ~4 days. Here are the logs: Sep 30 13:40:36 signal2 postfix/error[18592]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta34.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 14:21:55 signal2 postfix/error[27076]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=2478, delays=2478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 15:15:28 signal2 postfix/error[26069]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=5692, delays=5692/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta10.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 17:31:19 signal2 postfix/error[21426]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=13842, delays=13842/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta19.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 21:50:24 signal2 postfix/error[21488]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=29388, delays=29388/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta25.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 02:20:11 signal2 postfix/error[17888]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=45575, delays=45575/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta25.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 06:50:08 signal2 postfix/error[14401]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=61771, delays=61767/4.3/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta28.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 11:20:24 signal2 postfix/error[10233]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=77988, delays=77967/21/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta09.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 15:50:18 signal2 postfix/error[5719]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=94181, delays=94167/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta30.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 20:20:06 signal2 postfix/error[1014]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=110369, delays=110367/2.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta29.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 00:50:09 signal2 postfix/error[29149]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=126572, delays=126572/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta12.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 05:20:20 signal2 postfix/error[24714]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=142783, delays=142764/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta32.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 09:50:20 signal2 postfix/error[20450]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=158983, delays=158965/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta27.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 14:20:05 signal2 postfix/error[15686]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=175169, delays=175165/3.9/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta02.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 18:50:05 signal2 postfix/error[11213]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=191369, delays=191365/4/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta21.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 23:20:32 signal2 postfix/error[5842]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=207596, delays=207564/32/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta26.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 03:50:18 signal2 postfix/error[1119]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=223782, delays=223765/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta12.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 08:20:09 signal2 postfix/error[28593]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=239973, delays=239966/7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta38.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 12:50:08 signal2 postfix/error[23322]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=256172, delays=256167/4.6/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta17.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 17:20:18 signal2 postfix/error[18820]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=none, delay=272382, delays=272367/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta08.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 21:50:19 signal2 postfix/smtp[13687]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=288583, delays=288567/15/0.3/0, dsn=4.0.0, status=deferred (host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta18.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 02:20:12 signal2 postfix/smtp[8287]: DBBC5702B75: to=<earl.anderson@comcast.net>, relay=mx1.comcast.net[68.87.26.147]:25, delay=304776, delays=304768/6.3/0.3/0.7, dsn=2.0.0, status=sent (250 2.0.0 YxL81m02s3RP4Bm0QxL95o mail accepted for delivery) And I still don't get one. Yours is still in queue for delivery: Sep 30 14:23:56 signal2 postfix/error[17402]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=0.1, delays=0.1/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 17:01:53 signal2 postfix/error[20668]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=9478, delays=9478/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta14.westchester.pa.mail.comcast.net comcast Try again later) Sep 30 19:48:30 signal2 postfix/error[10666]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=19475, delays=19475/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Sep 30 23:50:09 signal2 postfix/error[26238]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=33974, delays=33974/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta21.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 04:20:05 signal2 postfix/error[22530]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=50169, delays=50169/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 08:50:11 signal2 postfix/error[18967]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=66376, delays=66367/8.7/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta35.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 13:20:23 signal2 postfix/error[14592]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=82587, delays=82569/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta17.westchester.pa.mail.comcast.net comcast Try again later) Oct 1 17:50:19 signal2 postfix/error[10261]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=98784, delays=98769/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta18.emeryville.ca.mail.comcast.net comcast Try again later) Oct 1 22:20:17 signal2 postfix/error[5594]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=114981, delays=114969/13/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta06.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 02:50:19 signal2 postfix/error[1345]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=131184, delays=131171/12/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta30.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 07:20:30 signal2 postfix/error[29898]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=147394, delays=147371/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta37.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 11:50:23 signal2 postfix/error[25103]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=163587, delays=163571/17/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta13.emeryville.ca.mail.comcast.net comcast Try again later) Oct 2 16:20:22 signal2 postfix/error[20394]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=179787, delays=179771/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.COMCAST.NET[68.87.26.147] refused to talk to me: 421 imta38.westchester.pa.mail.comcast.net comcast Try again later) Oct 2 20:50:21 signal2 postfix/error[15742]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=195986, delays=195971/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta15.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 01:20:22 signal2 postfix/error[10582]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=212186, delays=212171/15/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta20.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 05:50:22 signal2 postfix/error[5603]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=228386, delays=228370/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta24.emeryville.ca.mail.comcast.net comcast Try again later) Oct 3 10:20:31 signal2 postfix/error[832]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=244595, delays=244572/23/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta15.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 14:50:28 signal2 postfix/error[28274]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=260792, delays=260773/19/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta23.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 19:20:24 signal2 postfix/error[23125]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=276989, delays=276974/14/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later) Oct 3 23:50:26 signal2 postfix/error[18230]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=293191, delays=293174/16/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.40.147] refused to talk to me: 421 imta03.emeryville.ca.mail.comcast.net comcast Try again later) Oct 4 04:20:30 signal2 postfix/error[12972]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=309394, delays=309376/18/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta01.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 08:50:36 signal2 postfix/error[8163]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=325600, delays=325579/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta16.westchester.pa.mail.comcast.net comcast Try again later) Oct 4 13:20:35 signal2 postfix/error[2929]: 27EEE748EEF: to=<REDACTED@comcast.net>, relay=none, delay=341800, delays=341778/22/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx1.comcast.net[68.87.26.147] refused to talk to me: 421 imta24.westchester.pa.mail.comcast.net comcast Try again later)