Wietse Venema:
> This means that GLIBC (or whatever your equivalent is) has problems
> not POSTFIX.
Nikolaos Milas:
> Thank you Wietse and Victor for the diagnosis.
>
> As in RHEL / Rocky 8 we are at glibc v2.28 and it's really difficult to
> switch to a new server (e.g. RHEL / Rocky 9 with glib
On 14/2/2025 3:09 μ.μ., Wietse Venema wrote:
This means that GLIBC (or whatever your equivalent is) has problems
not POSTFIX.
Thank you Wietse and Victor for the diagnosis.
As in RHEL / Rocky 8 we are at glibc v2.28 and it's really difficult to
switch to a new server (e.g. RHEL / Rocky 9 with
Viktor Dukhovni via Postfix-users wrote in
:
|On Fri, Feb 14, 2025 at 06:13:51PM +, Matt Selsky via Postfix-users \
|wrote:
|>> Email with:
|>> From: "whatever" ,
|>
|> Exchange rejects this.
|
|But it is valid RFC5322 syntax.
|
|https://datatracker.ietf.org/doc/html/rfc532
On Fri, Feb 14, 2025 at 06:13:51PM +, Matt Selsky via Postfix-users wrote:
> > Email with:
> > From: "whatever" ,
>
> Exchange rejects this.
But it is valid RFC5322 syntax.
https://datatracker.ietf.org/doc/html/rfc5322#section-3.4
mailbox-list= (mailbox *("," mailbox
On Thu, Feb 13, 2025 at 06:51:26PM -0500, Wietse Venema via Postfix-users wrote:
> Maybe. First you need to be clear about what you
> mean with multiple From addresses:
>
> Email with:
> From: "f...@example.com"
Exchange accepts this.
> Email with:
> From: "whatever"
Exchange accep
Wietse Venema via Postfix-users:
> Pedro David Marco via Postfix-users:
> > Hi everybody...
> > is there anyway to make smtpd and/or qmgr be slighty more verbose?
> > i would like to have more info pero line about "from" and "to", something
> > like this:
> > Feb 13 12:34:56 mailserver postfix/smt
natan via Postfix-users:
[restriction class with check_policy lookup, plus a lookup table]
[to decide what domains this restriction will apply to]
> Theoreticly its ok.
>
> But I have some questions
> Is there any other - more sensible approach to the topic? Or how to
> optimize it even more?
> O
Nikolaos Milas via Postfix-users:
[dig commands dowk]
> Nevertheless, the warning does gets logged by postfix.
This means that GLIBC (or whatever your equivalent is) has problems
not POSTFIX.
The suspected sequence of events is as follows:
1 - Client connects
2 - Postfix asks GLIBC to look up t
Hi
For test i run setup with postgrey like:
...
smtpd_restriction_classes=greylist
greylist=check_policy_service { inet:127.0.0.1:12345, timeout=4s,
default_action=DUNNO }
smtpd_recipient_restrictions =
check_recipient_access inline:{{foo.bar.ltd=greylist}},
...
It works ok - but for one/two
On 14/2/2025 11:41 π.μ., Florian Piekert wrote:
...
could
reject_unknown_reverse_client_hostname
in the smtpd_recipient_restrictions be responsible, since there are
dns resolution issues for the hostname.
...
Thanks Florian for the reply.
Interestingly, dns reverse record query does work o
Pedro David Marco via Postfix-users:
> Hi everybody...
> is there anyway to make smtpd and/or qmgr be slighty more verbose?
> i would like to have more info pero line about "from" and "to", something
> like this:
> Feb 13 12:34:56 mailserver postfix/smtpd[12345]: 6F84B1A241:
> client=mail.example
Hi everybody...
is there anyway to make smtpd and/or qmgr be slighty more verbose?
i would like to have more info pero line about "from" and "to", something like
this:
Feb 13 12:34:56 mailserver postfix/smtpd[12345]: 6F84B1A241:
client=mail.example.com[192.168.0.1], from=,
to=, size=1234, nrcpt=
On Fri, Feb 14, 2025 at 11:30:53AM +0200, Nikolaos Milas via Postfix-users
wrote:
> Jan 14 10:37:12 mailgw1 postfix/smtpd[1125361]: warning: hostname
> smtpfra7.fortimailcloud.com does not resolve to address 154.52.2.249: Name
> or service not known
This host seems to have ~46 A records:
$
Hello,
could
reject_unknown_reverse_client_hostname
in the smtpd_recipient_restrictions be responsible, since there are dns
resolution issues for the hostname.
Florian
Am 14.02.2025 um 10:30 schrieb Nikolaos Milas via Postfix-users:
Hello,
The two mail gateway servers (MX 10 mailgw1.noa.gr
Hello,
The two mail gateway servers (MX 10 mailgw1.noa.gr and ΜΧ 20
mailgw3.noa.gr) of our org (noa.gr), running Rocky 8 and Postfix 3.9.1,
are working fine (for a long time - thanks Wietse), but we are having
issues with fortimailcloud servers.
These servers seem to be trying to connect but
15 matches
Mail list logo