Hmmm, for some reason I need to "Reply All" in Gmail to reply to the list. Try two.
"You have no logs, and provide little to no detail." Correct, and if it wasn’t a problem I wouldn’t even see the issue. I only have a few message headers to go off of because the sender is experiencing the “temporary” error. However the header doesn’t lie. Especially when comparing the header to what is known outside the header log. When the header agrees with experiential data it is a convincing argument. "You tried to contact with those organizations, but you were fruitless. It's almost impossible to figure out what happens to people on this mailing list. I would suggest a couple of strategies: First, you disclose the actual domain and provide a couple of test mailboxes, so that people here that may be willing to have a look to *your* problem can at least check if from their side the dns is ok, if your primary MX is broken, if their clients provide the same abnormal behavior when mailing those mails, etc." I did not provide all of that information previously because I didn’t think of a good way to do that and limit future spam. Thankyou for this wise suggestion. I have created two test aliases per domain we operate. I did it this way since we commonly see the problem when an email is sent to two recipients simultaneously, although users are keyed to the issue and now it seems to be noticed at other crucial times. slowmailtest...@ccbox.com slowmailtest...@ccbox.com slowmailtest...@p-r-c.com slowmailtest...@p-r-c.com "Second option. You involve your customer on this investigation. - The email issue caused a damage to your customer. - Your customer is not using "gmail", but a business version of it. - From your point of view, it is gmail's fault, since it didn't deliver the email to you until 19 hours later (although we can guess that the real problem will be somewhere in your setup, since it's not just gmail failing to properly deliver on time). - Thus you get your customer to open a ticket with gmail on why they took 19 hours to deliver their email. This is the same question you wanted gmail to answer you, but asked by a paying gmail customer that suffered its consequences. I expect that Google will be able to provide ample justification on *why* their systems were unable to deliver it earlier (e.g. they tried to connect from a dozen ip address, but were unable since -after you investigate- your firewall was any dropping packets from most of their outgoing servers). Once you get the actual view of the delay from their side, you should be able to progress towards fixing it." Yes, I agree this is the preferred strategy. My experience thus far has been either the organization was too large to properly care. A clear and present problem in today’s corporate America. Or the organization is too small (which was the case this week) to figure out how to do anything about it. As I keep working through the problem I will eventually come to the right combination and bear some fruit from my efforts. This is also why I posted this here. Thanks, Job Cacka On Thu, Jul 9, 2020, 6:13 PM Ángel via mailop <mailop@mailop.org> wrote: > On 2020-07-09 at 12:46 -0700, Job Cacka wrote: > > If you work with one of these relays and can shed light on the delay I > > would love to know how to get it fixed. > > > You have no logs, and provide little to no detail. You tried to contact > with those organizations, but you were fruitless. It's almost impossible > to figure out what happens to people on this mailing list. > > I would suggest a couple of strategies: > > First, you disclose the actual domain and provide a couple of test > mailboxes, so that people here that may be willing to have a look to > *your* problem can at least check if from their side the dns is ok, if > your primary MX is broken, if their clients provide the same abnormal > behavior when mailing those mails, etc. > > > Second option. You involve your customer on this investigation. > > - The email issue caused a damage to your customer. > - Your customer is not using "gmail", but a business version of it. > - From your point of view, it is gmail's fault, since it didn't deliver > the email to you until 19 hours later (although we can guess that the > real problem will be somewhere in your setup, since it's not just gmail > failing to properly deliver on time). > - Thus you get your customer to open a ticket with gmail on why they > took 19 hours to deliver their email. This is the same question you > wanted gmail to answer you, but asked by a paying gmail customer that > suffered its consequences. > I expect that Google will be able to provide ample justification on > *why* their systems were unable to deliver it earlier (e.g. they tried > to connect from a dozen ip address, but were unable since -after you > investigate- your firewall was any dropping packets from most of their > outgoing servers). > > Once you get the actual view of the delay from their side, you should be > able to progress towards fixing it. > > Best regards > > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
