Thanks again, Mark!
My responses below.
> On 1/4/20 5:47 PM, Allan Hansen wrote:
>>
>> a. The server was set up with the wrong domain name (our fault), so I had to
>> add the ‘correct’ one. I had seen the command ‘Add Domain’ in
>> the UI and thought that would do it, but Brian kindly sent me a
Thanks for the update, Bruce!
Bruce Johnson writes:
> This was the actual bounce error from one of the offending messages:
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>
> [redact
Hi,
I've seen this exact error before with various ISPs. I believe one of
them is Centurytel. I assume what's happened is that several ISPs use a
certain spam filtering service or app, and that filter is rejecting the
messages for some unknown reason. If that's the case, the particular ISP
in
I was the off-list person...
This was the actual bounce error from one of the offending messages:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[redacted]@alaskan.com
host
inbound.gci.net
[6
On Sun, Jan 5, 2020 at 12:56 AM Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:
> Jim Dory writes:
>
>
> > Sometimes I do get this: host mx1.arandomserver.com [198.252.100.64]
> > SMTP error from remote mail server after end of data:
> > 550 Headers contain illegal BOM
Jim Dory writes:
> I have one problem that when a particular user (the city) sends an
> announcement, it tends to bounce hundreds of mainly one ISP's users.. that
> ISP being Alaska's GCI.com .
I assume you mean that the attempt to deliver to users at GCI bounce
back to you?
What we would lik
