Date: prev next · Thread: first prev next last
2023 Archives by date, by thread · List index


Hi Budge,

I suspected (and still suspect) that the mail configuration for alarmaxjag@gmail.com is at least 
partly implicated in the problem, because the list probably (almost surely?) has other gmail users 
(the list admin could confirm that), none of which bounce posts. IAC, (a) I have no problem sending 
mail for the account I'm currently using to my gmail account, which (b) has /no/ handling by an 
outlook.com server.

I also suspected that the list SMTP server might be implicated, because and my direct mail to 
alarmaxjag@gmail.com seemed to be received normally (as I expected from my own gmail account).  
However, 10 hours(!) after sending that, I also got a bounce response to my direct mail, so the 
problem is not limited to list mail. Moreover, the long delay on my DM bounce adds to the 
strangeness: what kind of mail server takes so long to issue a bounce error message? - curiouser 
and curiouser - again, though, it was not a /gmail/ bounce. IAC, I forwarded that bounce to my ISP 
for response and, like you, will post the results.

Kind regards,
John


On 2023-07-08 14:15, Budge wrote:
Hi John,
I checked out the Google link on authentication and it seems that the problem probably lies with my 
ISP.  I have asked him to check the headers to find out if the problem is with him or further away. 
Will let you know what I learn.
Regards,
Budge.

On 07/07/2023 17:45, John Kaufmann wrote:
Your email has not been hacked. All of my (and presumably others') posts to the list in the last 
few days have returned that bounce from alarmaxjag@gmail.com - probably a list subscriber. The 
first obvious curiosity about this is that it's a gmail address, but the bounce comes from 
postmaster@outlook.com, so it's not gmail bouncing the message; likely there's an interesting mail 
configuration issue -- and on the list side as well, since the bounce is returned to the poster 
rather than to the list.

As alarmaxjag@gmail.com is the only list subscriber bouncing list mail, I wrote directly, to see if 
there is a response from my email address. It did NOT bounce, so the problem presumably lies in a 
list configuration interaction with that user's mail configuration. If there is a reply, I will of 
course report it.

jk

On 2023-07-06 11:02, Budge wrote:

... something strange happened in the background when I first asked how to renew.
I had from postmaster@outlook.com the following message:-

*mx.google.com rejected your message to the following email addresses:*

alarmaxjag@gmail.com
Your message wasn't delivered because the recipient's email provider rejected it.

*mx.google.com gave this error:
This mail is unauthenticated, which poses a security risk to the sender and Gmail users, and has 
been blocked. The sender must authenticate with at least one of SPF or DKIM. For this message, DKIM 
checks did not pass and SPF check for [errichel.co.uk] did not pass with ip: 
[2a01:111:f400:7e8b::207]. The sender should visit 
https://support.google.com/mail/answer/81126#authentication for instructions on setting up 
authentication. p13-20020a056402074d00b0051bfa6da365si551974edy.585 - gsmtp
*

No idea why or what.  Whoever uses Outlook anyway but does it mean my mail has been hacked?





--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.