From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Patchwork issues
Date: Mon, 26 Sep 2022 21:28:38 +0200
Message-ID: <97659423-4bc3-525c-c004-e36b0f2b89e0@rothenpieler.org> (raw)
In-Reply-To: <20220926142645.z6n24ak3ntsifrd2@jackie>
On 26.09.2022 16:26, Andriy Gelman wrote:
> On Mon, 26. Sep 14:46, Marvin Scholz wrote:
>> As I am not sure who else to email about this, I'll just post it here.
>>
>> I tried to register for Patchwork, however I got an error when registering.
>> I tried again and was told the account already exists, I tried to reset the
>> password for the account but did not get any email for that, so it seems
>> something is broken about Patchwork right now.
>
> I've been using outlook/gmail for sending emails, but unfortunately the accounts
> keep on getting flagged. So registration and password reset are not working
> at the moment.
>
> I need to set up a mail server. Suggestions for software are welcome. Maybe
> postfix?
Getting a mailserver up and running is sadly not an easy feat these days.
Microsoft, Google and a bunch of other "big players" do their utmost to
turn it into a closely walled garden.
I had to go through quite some trouble to be able to send mail to GMail
and Microsoft, and didn't bother with T-Online or GMX, so I can't send
mails there.
You'll want a setup of postfix+opendkim at the very least, and make sure
to properly set up SPF and DMARC while at it, otherwise your mail got no
chance from the get to go to get accepted anywhere.
You also cannot host those at any common hoster. DigitalOcean, AWS and
Google Cloud are usually blacklisted from sending mail.
Hetzner still seems to work, but the IP you get might have been sending
spam before and you will have a hard time fixing its reputation.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-09-26 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 12:46 Marvin Scholz
2022-09-26 12:53 ` Martin Storsjö
2022-09-26 14:26 ` Andriy Gelman
2022-09-26 18:35 ` Michael Niedermayer
2022-09-26 19:28 ` Timo Rothenpieler [this message]
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=97659423-4bc3-525c-c004-e36b0f2b89e0@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git