Hi
I have working setup without greylisting
I try run greylisting (via mtpolicyd) but only in some domain
I thinking something concept like:
main.cf:
...
smtpd_recipient_restrictions =
check_recipient_access hash:/etc/postfix/special_domains,
master.cf:
...
mtp
On Wed, Nov 13, 2024 at 12:46:10PM +0100, natan via Postfix-users wrote:
>
> main.cf:
> ...
> smtpd_recipient_restrictions =
>
> check_recipient_access hash:/etc/postfix/special_domains,
>
Add:
smtpd_restriction_classes = greylist
greylist = check_polic
Good morning,
That was not very useful.
Next experiment:
- Build Postfix like you built it before we started messing with debuggers.
- But this time don't add -DUSE_TLSRPT in the CFLAGS.
- As usual: make upgrade, postfix reload.
If this build also crashes, then the problem is at your end.
Florian Piekert via Postfix-users:
> Program received signal SIGSEGV, Segmentation fault.
> 0x57c3e4e44c6a in tlsp_eval_tls_error (state=state@entry=0x57c3e60647d0,
> err=6) at tlsproxy.c:741
> 741 if (state->client_start_props->tlsrpt
> (gdb) #0 0x57c3e4e44c6a in tlsp_eva
Given:
On Tue, Nov 12, 2024 at 08:48:38PM +0100, Florian Piekert via Postfix-users
wrote:
> Nov 12 11:29:09 sonne postfix/tlsproxy[3242552]: warning: TLS library
> problem: error:0A000102:SSL routines::unsupported
> protocol:../ssl/statem/statem_srvr.c:1657:
> Nov 12 11:29:09 sonne postfix/mas
Hi
Thenx for replay but im doing something wrong
smtpd_restriction_classes=lpolicyd, greylist
lpolicyd=check_policy_service { unix:private/policyd-lemat3, timeout=4s,
default_action=DUNNO }
greylist=check_policy_service { inet:127.0.0.1:12345, timeout=4s,
default_action=DUNNO }
smtpd_recipie
Hi
Thanx for reply problem solved :) This is exactly what I've come to
W dniu 13.11.2024 o 15:11, Wietse Venema via Postfix-users pisze:
natan via Postfix-users:
Hi
Thenx for replay but im doing something wrong
smtpd_restriction_classes=lpolicyd, greylist
lpolicyd=check_policy_service { unix:p
natan via Postfix-users:
> Hi
> Thenx for replay but im doing something wrong
>
> smtpd_restriction_classes=lpolicyd, greylist
> lpolicyd=check_policy_service { unix:private/policyd-lemat3, timeout=4s,
> default_action=DUNNO }
> greylist=check_policy_service { inet:127.0.0.1:12345, timeout=4s,
>
jeff--- via Postfix-users wrote in
<27de030dcf942f5ad58dc8fc753ac4d28644f...@lilo.org>:
|November 13, 2024 at 10:11 PM, "Wietse Venema via Postfix-users" mailto:postfix-users@postfix.org?to=%22Wietse%20Vene\
|ma%20via%20Postfix-users%22%20%3Cpostfix-users%40postfix.org%3E > wrote:
...
|> That
Coincidentally I'm writing a blog post about this (not ready yet).
* Domain Takeover
* Infrastructure Takeover
* Sending vs receiving
If somebody takes over your domain they can change host addresses as well
as MX hosts and SPF.
Most of our efforts are focused on receiving mail, but it's wort
Fred Morris via Postfix-users wrote in
:
|On Thu, 14 Nov 2024, Steffen Nurpmeso via Postfix-users wrote:
|>
|> I have a somewhat hard time understanding why greylisting shall be
|> useful for known domains, unless (maybe) these are somewhat
|> top-level ones?
|Coincidentally I'm writing a b
November 13, 2024 at 10:11 PM, "Wietse Venema via Postfix-users"
mailto:postfix-users@postfix.org?to=%22Wietse%20Venema%20via%20Postfix-users%22%20%3Cpostfix-users%40postfix.org%3E
> wrote:
>
> natan via Postfix-users:
>
> >
> > Hi
> > Thenx for replay but im doing something wrong
> >
> >
12 matches
Mail list logo
