• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved I can't receive certain emails from Amazon

stevland

Basic Pleskian
CentOS Linux 7.9.2009 (Core)
Plesk Obsidian Version 18.0.40 Update #1, last updated on Jan 6, 2022 08:04 AM
QMail psa-qmail 1.03-2.centos.7+p18.0.41.0+t211130.1601

I host websites. I also host my own web site. I am having an issue with my own account.

I go to Amazon. I try to change my email to one that I host.

Amazon says: We've sent a One Time Password (OTP) to your email address. Please enter it below.

But I never receive it.

I go to Tools & Settings > Server-wide mail settings > Mail Queue

There's the message:

Subject
Verify your new Amazon account

Sender
[email protected]


I click it

Message 14/3294442 not found in the queue!

All of my emails are forwarded to my Gmail (free, not Workspace) account. So I check my Gmail Inbox and Spam folders, no message.

I check /var/log/maillog

Jan 6 19:22:30 rede qmail-queue[16908]: 3285866: from=<[email protected]> to=<[email protected]> Jan 6 19:22:30 rede qmail-queue[16908]: 3285866: grey: stderr: SKIP Jan 6 19:22:30 rede qmail-queue[16908]: 3285866: py-limit-out: stderr: INFO:__main__:No SMTP AUTH and not running in sendmail context (incoming or unrestricted outgoing mail). SKIP message. Jan 6 19:22:30 rede qmail-queue[16908]: 3285866: py-limit-out: stderr: SKIP

Unfortunately, I am way out of my depth at this point and spinning my wheels.
 
Happily this seems to have been resolved by updating /etc/sysconfig/network-scripts/eth0 and /etc/resolv.conf
 
Back
Top