On 12/05/2016 08:52 PM, Alex wrote:
> Hi,
>
> I have a postfix-3.0.5 system with a few hundred users. They have
> access to submission, webmail, and dovecot to send and receive mail.
>
> On occasion, user's local desktop are compromised, and with it their
> account on this system. This leads to t
On 2016/11/27 13:15, li...@lazygranch.com wrote:
I hate to bug the list for what is probably a dumb question, but is there any situation
where an unauthorized user needs to connect to port 587? I'm wondering if there is some
oddball "edge" case.
My thought is to use my ipfw table of known tro
This depends on how the accounts are compromised.
First of, you should enforce so the MAIL FROM is locked to their account, eg
they cannot use another MAIL FROM than they are authorized to use.
Second, it then depends on how the accounts are compromised.
You say "their local desktop using the sub
On 2016-12-05 16:45, wie...@porcupine.org wrote:
MRob:
On 2016-12-05 16:27, wie...@porcupine.org wrote:
> MRob:
>> I was recently surprised to see .forward file in user's home dir being
>> honoured in a context where mail is set to be delivered via LMTP to
>> dovecot for final delivery. A respon
Hi,
I have a postfix-3.0.5 system with a few hundred users. They have
access to submission, webmail, and dovecot to send and receive mail.
On occasion, user's local desktop are compromised, and with it their
account on this system. This leads to their local desktop using the
submission service to
On 06/12/16 13:33, MRob wrote:
>> See http://www.postfix.org/ADDRESS_REWRITING_README.html
>
> This says .forward is only used by local(8).
Correct.
> So in my case, dovecot LMTP seems to be responsible for this?
No, local(8) is. Delivery of *all* mail to recipient domains listed in
the local
MRob:
> On 2016-12-05 16:27, wie...@porcupine.org wrote:
> > MRob:
> >> I was recently surprised to see .forward file in user's home dir being
> >> honoured in a context where mail is set to be delivered via LMTP to
> >> dovecot for final delivery. A response I got on the dovecot list
> >> implied
On 2016-12-05 16:27, wie...@porcupine.org wrote:
MRob:
I was recently surprised to see .forward file in user's home dir being
honoured in a context where mail is set to be delivered via LMTP to
dovecot for final delivery. A response I got on the dovecot list
implied
that the MTA is responsible
MRob:
> I was recently surprised to see .forward file in user's home dir being
> honoured in a context where mail is set to be delivered via LMTP to
> dovecot for final delivery. A response I got on the dovecot list implied
> that the MTA is responsible for this.
>
> Does Postfix handle .forwar
I was recently surprised to see .forward file in user's home dir being
honoured in a context where mail is set to be delivered via LMTP to
dovecot for final delivery. A response I got on the dovecot list implied
that the MTA is responsible for this.
Does Postfix handle .forward just before it
> On Dec 5, 2016, at 4:40 AM, Zalezny Niezalezny
> wrote:
>
> Problem is generated by one of our Ironport systems which is trying to
> establish TLS connection.
> In Postfix server I already configured it:
>
> smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3
> smtpd_tls_protocols = !SSLv2,!SSLv3
Problem is generated by one of our Ironport systems which is trying to
establish TLS connection.
In Postfix server I already configured it:
smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3
smtpd_tls_protocols = !SSLv2,!SSLv3
smtp_tls_protocols = !SSLv2,!SSLv3
I suspect that TLS client is not properl
12 matches
Mail list logo
