public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with no longer getting email from IPFire Community
Date: Wed, 16 Dec 2020 16:38:58 +0100	[thread overview]
Message-ID: <99793E2B-219E-421D-B412-583D62FEC973@ipfire.org> (raw)
In-Reply-To: <8e6534f4-71f5-67a0-5f4d-3fcb894974af@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2631 bytes --]

Hi,

I am sorry to hear this and I would like to get to the bottom of this assuming that other people have the same problem.

I checked the mail server log, and it looks like all emails to your email address have been successfully sent. It could have been that Google has bounced them - maybe that has something to do with the outage that also affected Gmail.

I cannot see anything suspicious in the logs. Maybe Peter can have a look to be sure.

The process is as follows: Discourse has its own email service which simply is horrible. We have a local Postfix instance that only accepts emails from Discourse and relays them to our main email server which only accepts connections if they present a client certificate and we only allow TLSv1.3 internally, and of course we have DANE switched on, too.

Those emails are then sent out to Gmail (in your case) from our main email relay. If Gmail was unavailable for some reason, Postfix would try  again for a while. The main relay is also handling all emails coming from and going to the list.

If you like, I can set up an email inbox on our servers for you with an @ipfire.org address. But of course I would like to know first why Gmail didn’t work for you.

Best,
-Michael 

> On 16 Dec 2020, at 13:03, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
> 
> Hi all,
> 
> 14 hours ago I got a system message online from IPFire Community. It said that that the last few emails to my Community email address had been bounced back as undeliverable.
> 
> I checked the email address and it is still entered as the correct one that has been running for the last year with IPFire Community. I have gmail set with no filters at all. I have checked and there are no emails from IPFire Community in my gmail boxes any more after 14 hours ago.
> 
> I am still getting emails from other lists and newsletters to the same email address but since 14 hours ago I have received nothing more from IPFire Community. There have been 7 postings that I would have normally received. I have also sent test emails to the email address and they are received.
> 
> Will the community email system start trying to send emails again or is that email address now permanently blocked. If the latter, then how can I change the IPFire Community email address. There is a change button for the email address I am using but if I enter another one then the system says that I can't carry that operation out.
> 
> I am still receiving the emails from this list as I used a different gmail address for this list.
> 
> 
> Thanks for any help that any one can give me.
> 
> Adolf
> 


  reply	other threads:[~2020-12-16 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 12:03 Adolf Belka
2020-12-16 15:38 ` Michael Tremer [this message]
2020-12-16 16:41   ` Adolf Belka
     [not found] <B77ABF15-64F6-4E2D-A751-360FCA220F1A@gmail.com>
2020-12-23  9:52 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=99793E2B-219E-421D-B412-583D62FEC973@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox