Hello
my current domain (bitfox.ddns.net) can set neither txt records nor
cname records.
So I can't setup dkim/spf for this domain.
So, by default I can't send email to gmail etc which requires either spf
or dkim.
but when I send email with this domain through fastmail's server,
fastmail wi
Hello,
AFAIK you can't use the "doma.in" DKIM Key for signing "sub.doma.in" eMails.
You need to add a separate key in the DNS file - which in this case you can't.
my current domain (bitfox.ddns.net) can set neither txt records nor cname
records.
So I can't setup dkim/spf for this domain.
So,
Hello,
Our customer has an old scanner/printer seems to support TLS1.2, but only a
few weak ciphers that are forbidden in out postfix configuration, according
to old discussion in this list:
smtpd_tls_exclude_ciphers =
MD5,SRP,PSK,aDSS,kECDH,kDH,SEED,IDEA,RC2,RC5,RC4,3DES
According to wire
thanks
>> # cat /etc/postfix/milter_header_checks
>> /^X-Spam.*YES/ FILTER local:/var/mail/spam
> - man 5 transport
> - man 8 local
fwiw, i have read those a number of times. one drowns in detail, and as
i am new here, i need structure as much as, or maybe before, detail.
> I
# cat /etc/postfix/milter_header_checks
/^X-Spam.*YES/ FILTER local:/var/mail/spam
- man 5 transport
- man 8 local
fwiw, i have read those a number of times. one drowns in detail, and as
i am new here, i need structure as much as, or maybe before, detail.
I don't think tha
It appears that Florian Piekert via Postfix-users said:
>AFAIK you can't use the "doma.in" DKIM Key for signing "sub.doma.in" eMails.
>You need to add a separate key in the DNS file
>- which in this case you can't.
Sorry, that's just wrong. You can put a DKIM signature with any d= domain on any
On 2024-11-22 at 07:09:06 UTC-0500 (Fri, 22 Nov 2024 13:09:06 +0100)
Matus UHLAR - fantomas via Postfix-users
is rumored to have said:
IIUC, as CBC ciphers are unsafe,
On 22.11.24 13:01, Bill Cole via Postfix-users wrote:
What is your basis for understanding that, in regards to SMTP?
Nothi
On 2024-11-22 at 13:24:33 UTC-0500 (Fri, 22 Nov 2024 19:24:33 +0100)
Matus UHLAR - fantomas via Postfix-users
is rumored to have said:
[...]
Thanks.
Now I'm searching for the proper smtpd_tls_exclude_ciphers setting to
get at least some, possibly most secure ciphers of those provided in
my fi
On Fri, Nov 22, 2024 at 05:54:31AM -0800, Randy Bush via Postfix-users wrote:
> > I don't think that using local(8) as a content filter is a good idea,
> > perhaps you meant to instead use "REDIRECT" or "HOLD".
>
> /^X-Spam.*YES/ REDIRECT s...@m0.rg.net
>
> did the trick, along with a speci
On Fri, Nov 22, 2024 at 7:51 AM Matthew McGehrin via Postfix-users
wrote:
>
> Hello
>
> Perhaps just a secondary port without TLS for legacy devices. TLS isn't
> required for SMTP.
And maybe a separate vlan for printers or legacy devices.
> See also:
>
> https://ciphersuite.info/
>
> For
Hello
Perhaps just a secondary port without TLS for legacy devices. TLS isn't
required for SMTP.
See also:
https://ciphersuite.info/
For looking up various cipher suites.
On 11/22/2024 6:09 AM, Matus UHLAR - fantomas via Postfix-users wrote:
> Hello,
> Our customer has an old scanner/printer
On 2024-11-22 at 07:09:06 UTC-0500 (Fri, 22 Nov 2024 13:09:06 +0100)
Matus UHLAR - fantomas via Postfix-users
is rumored to have said:
IIUC, as CBC ciphers are unsafe,
What is your basis for understanding that, in regards to SMTP?
The HTTP-relevant attacks (e.g. BEAST) I am aware of on CBC c
On Fri, Nov 22, 2024 at 01:09:06PM +0100, Matus UHLAR - fantomas via
Postfix-users wrote:
> Our customer has an old scanner/printer seems to support TLS1.2, but only a
> few weak ciphers that are forbidden in out postfix configuration, according
> to old discussion in this list:
TLS 1.2 is accep
13 matches
Mail list logo
