The discussion revolves around issues with reply by email. sok777 has set up the feature following instructions, but emails sent to the forum are not being received, rejected, or bounced back. pfaffman suggests checking the email logs and docker logs mail-receiver, but sok777 finds nothing. pfaffman suspects an issue with the MX record or incoming port 25 being blocked. sok777 confirms the MX record is configured and wonders if a test mail should have bounced back if port 25 was blocked. sok777 suspects the issue is indeed with port 25 on Google Cloud and is looking for a workaround. pfaffman suggests fixing Google Cloud, reconfiguring other mail servers, or moving the mail server elsewhere.
We’ve set up reply by email with a new container as instructed, as well as the API and the DNS.
Settings on the frontend side has been set as well.
Trying to send an email to our forum isn’t received or shown under ‘rejected’ or ‘received’ but the email isn’t bounced back as well.
any thoughts?
Set it up how? With a mailbox or Straightforward direct-delivery incoming mail?
hey Jay @pfaffman
I followed the link you mentioned here exactly yesterday.
The container is set up, as well as the DNS and the settings on the actual forum. Still don’t see any emails in my log when trying to mail in.
Thanks in advance!
So you don’t see anything in admin/email/rejected or admin/email/received?
Next you’d
docker logs mail-receiver
I think
There’s nothing there either. @pfaffman
The only thing showing is daemon started
Then you probably haven’t configured your MX record or incoming port 25 is blocked.
the MX record is configured. And I assume if there was such issue a test mail sent to the forum’s mail should’ve bounced back..(?)
Sorry for the double post - I think it might actually be the issue with port 25 on Google cloud. Is there a workaround?
I believe that your options are to fix Google Cloud or reconfigure every other mail server on the Internet to use another Port. Or put the mail server somewhere else?