CocoaPods / cocoapods-trunk

CocoaPods plugin for trunk

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Trunk register verification email not sent

leonardlabat opened this issue · comments

Report

What did you do?

$ pod trunk register rnd-pubsdk@criteo.com "PubSdk team"
Ran pod trunk register but did not receive verification link in email.

What did you expect to happen?

Receive a verification email

What happened instead?

No email came in.
While re-running the command in verbose mode, I get the following output (I've truncated some private infos)

`opening connection to trunk.cocoapods.org:443...

opened

starting SSL for trunk.cocoapods.org:443...

SSL established, protocol: TLSv1.3, cipher: TLS_AES_128_GCM_SHA256

<- "POST /api/v1/sessions HTTP/1.1\r\nContent-Type: application/json; charset=utf-8\r\nAccept: application/json; charset=utf-8\r\nUser-Agent: CocoaPods/1.11.3\r\nAccept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3\r\nHost: trunk.cocoapods.org\r\nContent-Length: 73\r\n\r\n"

<- "{"email":"rnd-pubsdk@criteo.com","name":"PubSdk team","description":null}"

-> "HTTP/1.1 201 Created\r\n"

-> "Date: Wed, 01 Feb 2023 13:59:04 GMT\r\n"

-> "Connection: keep-alive\r\n"

-> "Strict-Transport-Security: max-age=31536000\r\n"

-> "Content-Type: application/json\r\n"

-> "Content-Length: 192\r\n"

-> "X-Content-Type-Options: nosniff\r\n"

-> "Server: thin\r\n"

-> "Via: 1.1 vegur\r\n"

-> "\r\n"

reading 192 bytes...

-> "{"created_at":"2023-02-01 13:59:04 UTC","valid_until":"2023-06-09 13:59:04 UTC","verified":false,"created_from_ip":"90.105.XX.XX","description":null,"token":"f2e283a744fca0XXXXXXXXXX"}"

read 192 bytes

Conn keep-alive`

Could it be that the address rnd-pubsdk@criteo.com is blacklisted on your side? I've tried with other @criteo.com addresses and it worked fine. But unfortunately, the pod we need to update is owned by rnd-pubsdk@criteo.com

Thanks in advance for your help

Hello @orta
Sorry for pinging you but are you able to help us here?
Many thanks

Yep, it was blocke don our side after the email bounced twice - should be good to go through now!

Confirming the issue is fixed, thanks a lot for your help!