More email trouble

[David Schultz]

I had an email bounced this week and all the error message said was that
it spent too much time in the queue:

Error:

* Your message was not delivered after reaching its max age in queue.



The email was sent to a listserver that is working because I received
emails from it today. I tried sending it again but my message hasn't
appeared in the list archives so I expect another undeliverable message
in two days.

Customer service was its usual PITA. Finally claiming that there was an
outage. (Not mentioned on the network status web page of course.) An
oddly specific outage as emails to other addresses worked fine.

Another fine service of vadesecure.

--
http://davesrocketworks.com
David Schultz

[Ant]

Yup. I got a few. What about incoming? I seem to be missing some.

Slammy times! 2021 is repeating 2020. :( Please get your vaccine shot(s) if you haven't done so! :)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

[David Schultz]

On 8/11/21 7:12 PM, Ant wrote:
> Yup. I got a few. What about incoming? I seem to be missing some.
>
>

Very difficult to tell about incoming. Email from groups.io seems OK, or
at least I am seeing some.

Vadesecure claims that all is well:

https://status.vadesecure.com/

> David Schultz <david....@earthlink.net> wrote:
>> I had an email bounced this week and all the error message said was that
>> it spent too much time in the queue:
>
>> Error:
>
>> * Your message was not delivered after reaching its max age in queue.
>
>
>
>> The email was sent to a listserver that is working because I received
>> emails from it today. I tried sending it again but my message hasn't
>> appeared in the list archives so I expect another undeliverable message
>> in two days.
>
>> Customer service was its usual PITA. Finally claiming that there was an
>> outage. (Not mentioned on the network status web page of course.) An
>> oddly specific outage as emails to other addresses worked fine.
>
>> Another fine service of vadesecure.
>
>


--

http://davesrocketworks.com
David Schultz

[David Schultz]

On 8/11/21 5:27 PM, David Schultz wrote:
> I had an email bounced this week and all the error message said was that
> it spent too much time in the queue:
>

I received the failure message from Wednesday's attempt. I immediately
attempted to send it again with the result that the listserver archive
didn't get it. So another interaction with Earthlink customer service.

This time the chat system didn't die from lack of attention but
responses were very slow. After the usual futzing around I was told to
send it again and all should work fine. So I explain carefully how I
already had.

So now it has been "escalated" for whatever good that will do. A visit
to the Vadesecure web site shows that for the most part you need to have
an account with them to file a complaint. Although it does say to send a
message to ab...@vadesecure.com if you think they blocking emails they
shouldn't. Not the normal use for that address but what the hell, I
tried it anyway.


Also, email notifications from e2e.ti.com seem to have ended. I can't
find any way (as with groups.io) to see which end the problem is at. A
quick check at groups.io did show a recent 130 error from Vadesecure but
for some stupid reason their page for decoding error numbers doesn't
include that one.

I hate Vadesecure.

[David Schultz]

No progress and another useless attempt to talk to customer support. I
ended up speaking to two different persons.

The first tried to convince me that email being routed through
vadesecure's servers was the fault of my email client. This was obvious
bullshit:

$ ping smtpauth.earthlink.net
PING smtpauth.earthlink.net (51.81.229.171) 56(84) bytes of data.
64 bytes from smtp03.oxsus-vadesecure.net (51.81.229.171): icmp_seq=1
ttl=47 time=65.8 ms



Earthlink no longer has an SMTP server for customers. At least not one
they are telling us about.

I was also told that sending the email using the webmail system would
work. It didn't. The second person I spoke with tried to convince me the
problem was due to too many people being subscribed to the list. Also
obvious bullshit. How the hell would they know? In any case, a test
email sent to the LTSpice list (43K subscribers) went through without a
hitch.

I suspect that the only way to cure this problem is to use an email
service that doesn't use the idiots at vadesecure.

[Ant]

Yeah. Also, their webmail is broken:
1. "Not spam" automatically adds to my ELN's webmail's addressbook which I
told it not to. It used to work fine.
2. Using domain suffix (e.g.,, .in) to block in ELN's webmail's spamBlocker
does not work.

BTW, you can e-mail earth...@earthlink.net about your issues too.
It's better than their regular customer support, but not great.

Dang life, bugs (both digital and biological), issues, etc. 2021 is repeating 2020. :( Please get your vaccine shot(s) if you haven't done so! :)

[pyotr filipivich]

Adding to the conversation : Earthlink apparently has never heard of
the concept of filtering on subject lines.

I get a lot of spam with a common element in the subject line. But
I can't filter on that so ... I just forward them to abuse.

a...@zimage.comANT (Ant) on Thu, 19 Aug 2021 02:13:57 -0500 typed in
alt.provider.earthlink the following:

>Yeah. Also, their webmail is broken:
>1. "Not spam" automatically adds to my ELN's webmail's addressbook which I
> told it not to. It used to work fine.
>2. Using domain suffix (e.g.,, .in) to block in ELN's webmail's spamBlocker
> does not work.
>
>BTW, you can e-mail earth...@earthlink.net about your issues too.
>It's better than their regular customer support, but not great.
>
>
>David Schultz <david....@earthlink.net> wrote:
>
>> No progress and another useless attempt to talk to customer support. I
>> ended up speaking to two different persons.
>
>> The first tried to convince me that email being routed through
>> vadesecure's servers was the fault of my email client. This was obvious
>> bullshit:
>
>> $ ping smtpauth.earthlink.net
>> PING smtpauth.earthlink.net (51.81.229.171) 56(84) bytes of data.
>> 64 bytes from smtp03.oxsus-vadesecure.net (51.81.229.171): icmp_seq=1
>> ttl=47 time=65.8 ms
>

--
pyotr filipivich
This Week's Panel: Us & Them - Eliminating Them.
Next Month's Panel: Having eliminated the old Them(tm)
Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)