Wietse:
> Postfix does not XFORWARD the information that it has received
> with XFORWARD. It XFORWARDs the information that it has used for
> its own smtpd_mumble_restrictions.
Pedro David Marco:
> Thanks Wietse, sometimes we want to stretch Postifx like gum beyond limits...
> Thanks again, Mr!
Thanks Wietse, sometimes we want to stretch Postifx like gum beyond limits...
Thanks again, Mr!
Pete.
On Thursday, October 12, 2023 at 02:32:11 PM GMT+2, Wietse Venema via
Postfix-users wrote:
Pedro David Marco via Postfix-users:
> Hi,
> Postfix documentation states clearly that XFORDWA
On 2023-10-12 at 08:26:40 UTC-0400 (Thu, 12 Oct 2023 23:26:40 +1100)
Matthew J Black via Postfix-users
is rumored to have said:
On 12/10/2023 23:19, Wietse Venema via Postfix-users wrote:
If the 'find' command cannot enumerate mode 755 directories, then
this is no longer a problem that receive
Matthew J Black via Postfix-users:
> On 12/10/2023 23:19, Wietse Venema via Postfix-users wrote:
> > If the 'find' command cannot enumerate mode 755 directories, then
> > this is no longer a problem that receives Postfix support.
> >
> > Turning off SeLinux is easy.
>
> Thanks for getting back to
Pedro David Marco via Postfix-users:
> Hi,
> Postfix documentation states clearly that XFORDWARD is intended for scenarios
> like this:
> Client -> MTA1-> Content_filter -> MTA2
> And then Content_filter is able to get the IP of Client. Works great!
Only if the filter understands XFORWARD command
On 12/10/2023 23:19, Wietse Venema via Postfix-users wrote:
If the 'find' command cannot enumerate mode 755 directories, then
this is no longer a problem that receives Postfix support.
Turning off SeLinux is easy.
Wietse
Thanks for getting back to me.
Yes, turning off SELinux is eas
duluxoz via Postfix-users:
> (Sorry, can't remember if I should be top-posting or bottom-posting :-)? )
>
> The answer for both queries:
>
> * The root folder is 555 root:root
> * All other folders are 755 root:root
> * The certs themselves are 600 root:root (I think I mentioned this one
>
Microsoft incident EX680695 (sorry if i recall wrongly).
Solved now!
Pete.
On Wednesday, October 11, 2023 at 03:24:03 PM GMT+2, Matus UHLAR - fantomas
via Postfix-users wrote:
On 11.10.23 15:06, Ralf Hildebrandt via Postfix-users wrote:
>Since this morning, various MX hosts in *.mail.pr
On 12.10.23 00:56, wesley--- via Postfix-users wrote:
How can I setup username based transport?
for incoming messages, such as use...@foo.com will be delivered to host a.
use...@foo.com will be delivered to host b.
transport_maps support username@domain notation:
http://www.postfix.org/transp
Hi,
Postfix documentation states clearly that XFORDWARD is intended for scenarios
like this:
Client -> MTA1-> Content_filter -> MTA2
And then Content_filter is able to get the IP of Client. Works great!
But i was wondering... what i chain more MTAs?
Client -> MTA1 - > MTA2 -> Content_filter ->
10 matches
Mail list logo
