Re: sysutils/nut maintainer mail rejection
- Reply: Cy Schubert : "Re: sysutils/nut maintainer mail rejection"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 26 Jan 2024 00:45:00 UTC
Sorry for the noise folks, I'll keep this brief. My original ports question is at the bottom. On 2024-01-25 15:37, Cy Schubert wrote: In message <CAOaF7tMr=uALOofsk-0d9QXGVMOTN=8CCeiDf5VF+OMu=ara1w@mail.gmail.c om> [snip] Testing email from gmail.com directly to my infrastructure and throughmx2.freebsd.org work. There may be something in your subject line or body that either postfix doesn't agree with, in header_checks, or the Bayesian filter flagged something. Direct replie to cschubert.com from protonmail.com and gmail.com bounced too. Here's what I got from gmail: ---------------------------------------------- message/delivery-status ---------------------------------------------- Reporting-MTA: dns; googlemail.com Arrival-Date: Thu, 25 Jan 2024 16:26:13 -0800 (PST) X-Original-Message-ID: <CAOaF7tMmb7P8ANwao+pD+4Ltr3rWAAeFD+nJK8v3Nw5-XDJBJg@mail.gmail.com> Final-Recipient: rfc822; Cy.Schubert@cschubert.com Action: failed Status: 5.7.1 Remote-MTA: dns; spqr.komquats.com. (70.66.152.170, the server for the domain cschubert.com.) Diagnostic-Code: smtp; 554 5.7.1 <tom.b.rushworth@gmail.com>: Sender address rejected: Rejected Last-Attempt-Date: Thu, 25 Jan 2024 16:26:14 -0800 (PST) ---------------------------------------------- message/rfc822 ---------------------------------------------- [snip - rest of bounce deleted] The gmail address is the one I'm using to send to this list, and it seems to work there. I don't get it, but we probably shouldn't spend too much time on it. The ports question that started all this: I'm hoping you are the right person for this question. You're listed as the maintainer on both ports mentioned in the subject above. I've got an experimental NUT driver for an Alpha Technologies CFR1500RM UPS. I doubt there are many of these old UPSes in use, but I was planning to offer it to the NUT community anyways. I started the driver directly from the NUT sources and only afterwards realized there was a port (or ports). Since it still needs some work I'd like to set it up as a patch I can apply to the ports tree locally so I can work on it in sync with the FreeBSD ports system. Which port should I use - sysutils/nut or sysutils/nut-devel ? So far the only changes needed are to drivers/Makefile.am and the actual new driver source.