On 29/12/2021 03:50, Jaroslaw Rafa via mailop wrote:
It is Roundcube that is actually connecting to Dovecot/Postfix and
receiving/sending mail, not the user's browser, so the connecting IP
that
Dovecot/Postfix gets is technically correct. No need to change it. On
the
other hand, user's browser is talking HTTP to Roundcube, and Roundcube
knows
it's IP address, so Roundcube is the point where restrictions should be
enforced, not Dovecot/Postfix.
Agreed, dovecot doesnt know - nor care - if its kmail, evolution,
thunderbird, outlook, RC, imapproxy, or some other client, it's not its
job to care.
RC has rcguard which works well, and as mentioned by another poster
there is always fail2ban.
Frankly, I don't see any problem that needs addressing, and I guess
neither do the RC team if this is as is claimed a "long standing" issue
for a small minority.
As to the anti privacy brigade, suck it up, we are network operators, if
we want to know who they are, we can, just means we have to multitask
looking at two logs, i mean FFS, how hard is that, you already do this
tracking local spammers actions and then looking them up in CRM or
radius, or some other database.
get over it.
--
Regards,
Noel Butler
This Email, including attachments, may contain legally privileged
information, therefore at all times remains confidential and subject to
copyright protected under international law. You may not disseminate
this message without the authors express written authority to do so.
If you are not the intended recipient, please notify the sender then
delete all copies of this message including attachments immediately.
Confidentiality, copyright, and legal privilege are not waived or lost
by reason of the mistaken delivery of this message._______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
