Hi Bubu,
After sending an email to that address, I immediately received an email with the subject [REJECTED]<subject_written>. The body of the email said something like, we couldn’t work out what you were saying try logging in and creating a ticket.
Regardless, I was able to login at the time (4 days ago) but not able to login all day today.
Four days ago I was also able to use my access token to use the API but mysteriously that ability has been removed also. I now constantly get a {“message”:“401 Unauthorized”}. I’m going to keep trying but I’m really struggling to see the point of using Gitlab, if they have become so dependent on Goo.
Tonight I tried replying to the [REJECTED] email from gitlab. To my surprise I received a bounce-back email from “Mail Delivery Subsystem” <mailer-daemon@googlemail.com>.
** Address not found **
Your message wasn't delivered to noreply@gitlab.com (this was not the email that I actually sent to) because the address couldn't be found, or is unable to receive mail.
Learn more here: https://support.google.com/mail/answer/6596
The response was:
The email account that you tried to reach does not exist. Please try double-checking the recipient's email address for typos or unnecessary spaces. Learn more at
https://support.google.com/mail/answer/6596
So Gitlab not only require it’s user to pass through a Googate, but the email system at Gitlab is run by Goo. Ugh. Not very encouraging. This combined with their attempt at injecting “analytics” last year… ugh.
EDIT: I have a system that will keep trying to use the API, until it works.
EDIT: @hans @hotlittlewhitedog This is the branch I’m trying to create a MR for Files · NoAppsShouldAppearInBothLists · Deano / Jekyll Plugin · GitLab