Markus Neteler via gdal-dev writes:
> Am 29.05.25 um 7:55 PM schrieb Greg Troxel via gdal-dev:
>> The way to debug this is to look at the logs at the computer that
>> receives your mail from lists.osgeo.org, and to see if it is
>> implementing greylisting.
>
> Yes, greylisting is in place on list
Am 29.05.25 um 7:55 PM schrieb Greg Troxel via gdal-dev:
The way to debug this is to look at the logs at the computer that
receives your mail from lists.osgeo.org, and to see if it is
implementing greylisting.
Yes, greylisting is in place on lists.osgeo.org.
Markus
--
Markus Neteler, PhD
http
Thank Evan!
I am planning on being read-only for now.
My program is interactive and potentially long-lived, and the user interface
can be used to open layers at different times. If I miss closing a Dataset will
the garbage collector eventually take care of this? Or is it important to
always
My program is interactive and potentially long-lived, and the user
interface can be used to open layers at different times. If I miss
closing a Dataset will the garbage collector eventually take care of this?
If it is no longer referenced by a Java variable, yes it should in
theory (depend
PS: "New" doesn't mean new, it means "hasn't written in a while", so my own
message got delayed.
This strategy might have worked a long time ago, when spammers would just
connect to the SMTP server of the destination, i.e. mail.osgeo.org. They'd get
an error and their script would move on to an
Barry DeZonia via gdal-dev writes:
> For the record it is not just this user experiencing issues. I
> received the java bindings Original email 11 minutes after the Reply
> to that email.came through. However, I am accessing mail via gmail.com
> too.
Please open a support ticket to have the logs
I experience the same with GDAL and other OSGeo mailing lists. The
delay in receiving a message can be as much as two days, and messages
often arrive out-of-sequence. Other times things happen more or less
instantaneously.
Folks spent some time investigating the issue with the geos-devel list
but
For the record it is not just this user experiencing issues. I
received the java bindings Original email 11 minutes after the Reply
to that email.came through. However, I am accessing mail via gmail.com
too.
On Thu, May 29, 2025 at 12:58 PM Laurențiu Nicola via gdal-dev
wrote:
>
> PS: "New" doesn
Daniel Evans via gdal-dev writes:
> Tom's initial email was delayed by 48 minutes, arriving at 1715 UTC:
> - Originally sent by the mailing list at 1627 UTC
> - After a few internal hops, received by lists.osgeo.org at 1636 UTC (with
> a header stating X-Greylist: delayed by 473 seconds)
> - Rece
Hi Seth,
My mine finally engaged on mapserver logs. Here are the results of the
query request:
https://map51.saltwatercentral.com/cgi-bin/mapserv?map=/maps/wms/hycom_2d_1.map&mode=query&type=mlt&layers=query&mapxy=-67+37
[Thu May 29 12:38:19.457606 2025] [cgi:error] [pid 848556] [client
98.9
Hi,
I think it's at least in part an anti-spam measure. We reject messages from new
users and their server will try later. Spammers are less likely to retry
delivery of their messages.
I'm personally not a fan of this, but..
Laurentiu
On Thu, May 29, 2025, at 20:29, Daniel Evans via gdal-dev
Hi all,
Over the last couple of months, I've been receiving emails from the
gdal-dev list with a significant delay, with emails from threads sometimes
arriving out of order.
For example, in the recent thread on Java bindings, the email headers show
the following;
Tom's initial email was delayed
Hi,
In particular I would like to know more about object life cycles and
memory management:
What kind of object management is the client program responsible for?
Normally none, but you may want to explicitly call .Close() on datasets
to ensure the underlying file is closed at the appropriat
Hi
I am new to using gdal/ogr in Java via the swig bindings and I am trying to
figure things out by googling around. I have looked at the API documentation,
tutorials and sample programs, but I still have a few questions.
In particular I would like to know more about object life cycles and mem
Looks like an issue with your package manager (or your use of it) where
the QGIS version links to an older version of GDAL (libgdal.so.36 is
GDAL 3.10.x) than the one you've installed. Definitely not a upstream
GDAL or QGIS issue. Sorry for not being more helpful: I'm not familiar
at all with M
RPi 5
KDE Plasma Version 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version 6.9.0
Kernel Version 6.6.56-1-MANJARO-RPI5 (64-bit)
Graphics Platform Wayland
So this is an aarch64 v8 version of Manjaro. Before the last system
upgrade I was using QGIS and it appeared to be performing flawlessly.
Not s
16 matches
Mail list logo
