On 9.03.2019 03:50, Viktor Dukhovni wrote:
On Fri, Mar 08, 2019 at 08:00:47PM +0300, sse450 wrote:
Hoping to solve this problem, I wanted to block all the sender emails
not defined in sender_relay table. I will do what you advised here. But,
I know that this will also block apache sender even
On Fri, Mar 08, 2019 at 08:00:47PM +0300, sse450 wrote:
> Hoping to solve this problem, I wanted to block all the sender emails
> not defined in sender_relay table. I will do what you advised here. But,
> I know that this will also block apache sender eventually. In this case,
> I will have ano
On Mar 8, 2019, at 10:00, sse450 wrote:
> This mails originates from Apache through (I think) php mail. Obviously, my
> server is compromised.
Not obvious at all, no. But the php script to sent mail to users may not be
properly configured for your new settings. It should be setup to use submiss
* sse:
> Obviously, my server is compromised.
Are you really certain of that? If you are, I suggest you do a full wipe
of your server. Meddling with the Postfix configuration to prevent email
being sent does nothing to address a compromised server.
-Ralph
On 8.03.2019 19:15, Viktor Dukhovni wrote:
On Mar 8, 2019, at 11:02 AM, Wietse Venema wrote:
Perhaps sender_dependent_default_transport_maps uses the same
null-sender lookup mechanism as other mappings. For example the
transport map has this note:
Note 1: the null recipient address is looked u
> On Mar 8, 2019, at 11:02 AM, Wietse Venema wrote:
>
> Perhaps sender_dependent_default_transport_maps uses the same
> null-sender lookup mechanism as other mappings. For example the
> transport map has this note:
>
> Note 1: the null recipient address is looked up as
> $empty_address_recipient
Viktor Dukhovni:
>
> > That's easy enough, use sender_dependent_default_transport_maps,
> > and a default transport that returns mail as undeliverable.
> >
> > /etc/postfix/main.cf:
> > sender_dependent_default_transport_maps = hash:/etc/postfix/sender_relay
> > default_transport = error:
> That's easy enough, use sender_dependent_default_transport_maps,
> and a default transport that returns mail as undeliverable.
>
> /etc/postfix/main.cf:
> sender_dependent_default_transport_maps = hash:/etc/postfix/sender_relay
> default_transport = error:5.7.1 sender is not authorized
On 8.03.2019 18:01, Wietse Venema wrote:
Ozy Mate:
Dear Friends,
I have signed up with a 3rd party smtp server as relay host. This server
needs the following lines in the main.cf of our server instead of relayhost
direction:
smtp_sender_dependent_authentication = yes
sender_dependent_relayhost
I haven't taken any step to prevent this as I don't know what to do.
Hence, I am asking about it.
I would appreciate if you direct me in the right direction to prevent
all the others not listed in sender_dependent_relayhost_maps.
On 8.03.2019 15:41, @lbutlr wrote:
On 7 Mar 2019, at 20:52,
Ozy Mate:
> Dear Friends,
>
> I have signed up with a 3rd party smtp server as relay host. This server
> needs the following lines in the main.cf of our server instead of relayhost
> direction:
>
> smtp_sender_dependent_authentication = yes
> sender_dependent_relayhost_maps = hash:/etc/postfix/se
> On 7 Mar 2019, at 20:52, Ozy Mate wrote:
>
> Dear Friends,
>
> I have signed up with a 3rd party smtp server as relay host. This server
> needs the following lines in the main.cf of our server instead of relayhost
> direction:
>
> smtp_sender_dependent_authentication = yes
> sender_depen
Dear Friends,
I have signed up with a 3rd party smtp server as relay host. This server
needs the following lines in the main.cf of our server instead of relayhost
direction:
smtp_sender_dependent_authentication = yes
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relay
smtp_sasl_auth_
13 matches
Mail list logo
