* Tom Reed via Postfix-users :
>
> Dear lists,
>
> I in fact use rarely this mailbox: t...@dkinbox.com
> But today I found both my domain "dkinbox.com" and the mailserver IP:
> 38.45.66.54 are listed into spamhaus "css" and "dbl" blacklists.
Checking
Am 06.07.23 um 21:39 schrieb Viktor Dukhovni via Postfix-users:
So the service provider advertises, but fails to implement "PLAIN", that
sounds like a bad idea. Open a bug report. They should not do that.
I did have one open. More for cram-md5 than plain, of course. The issue
is: For
Hi all...
Currently Postfix do not show in log the Recipient of emails that exceed
Meesage_size_limit becasue MAIL FROM comes before RCPTO TO... butis there any
nice way of forcing Postfix to reject that email after the RCPTO TO?
I have considered to make a body check like this:
/.{10-}/
On 7/6/2023 5:12 PM, Noel Jones via Postfix-users wrote:
On Jul 6, 2023, at 2:55 PM, joe a via Postfix-users
wrote:
On 7/6/2023 12:56 PM, joe a via Postfix-users wrote:
On 7/6/2023 8:53 AM, Viktor Dukhovni via Postfix-users wrote:
On Thu, Jul 06, 2023 at 08:32:42AM -0400, joe a via
Dnia 7.07.2023 o godz. 10:27:38 joe a via Postfix-users pisze:
> seems to me that having all possible mail recipients as system users
> is not practical on even systems of moderate user count.
My previous job was administering servers at an university. Our main
Internet server (that was used for
On Fri, Jul 07, 2023 at 11:47:35AM -0400, postfix--- via Postfix-users wrote:
> > Currently Postfix do not show in log the Recipient of emails that
> > exceed Meesage_size_limit becasue MAIL FROM comes before RCPTO TO...
> > but is there any nice way of forcing Postfix to reject that email
> >
Currently Postfix do not show in log the Recipient of emails that exceed
Meesage_size_limit becasue MAIL FROM comes before RCPTO TO... but
is there any nice way of forcing Postfix to reject that email after the RCPTO
TO?
http://www.postfix.org/postconf.5.html#smtpd_delay_reject
On Fri, Jul 07, 2023 at 10:27:38AM -0400, joe a via Postfix-users wrote:
> >> local_recipient_maps =
> >
> > This is the wrong solution. With this setting, postfix will accept
> > mail to any user address, and you will eventually have a queue full
> > of undeliverable bounces, plus get listed
On Fri, Jul 07, 2023 at 05:24:45PM +0200, Jaroslaw Rafa via Postfix-users wrote:
> > seems to me that having all possible mail recipients as system users
> > is not practical on even systems of moderate user count.
>
> My previous job was administering servers at an university. Our main
>
On Fri, Jul 07, 2023 at 11:54:44AM -0400, Viktor Dukhovni via Postfix-users
wrote:
> If the client uses PIPELINING, the pipelined "RCPT TO" after the rejected
> "MAIL FROM" will presumably be logged.
Turns out that's not the case. Postfix does not log client "syntax"
errors and sending "RCPT
On 7/7/2023 11:07 AM, Viktor Dukhovni via Postfix-users wrote:
On Fri, Jul 07, 2023 at 11:54:44AM -0400, Viktor Dukhovni via Postfix-users
wrote:
If the client uses PIPELINING, the pipelined "RCPT TO" after the rejected
"MAIL FROM" will presumably be logged.
Turns out that's not the case.
One hesitates to post this.
Found some oddness when changing a destination in transport_maps
(transport_maps = lmdb:/etc/postfix/transport).
Seems related to pattern matching.
The file /etc/postfix/transport contains entries of this form:
somename-xyz.comnoauth:ipaddress_1
On 7/7/2023 3:46 PM, joe a via Postfix-users wrote:
One hesitates to post this.
Found some oddness when changing a destination in transport_maps
(transport_maps = lmdb:/etc/postfix/transport).
Seems related to pattern matching.
The file /etc/postfix/transport contains entries of this form:
If no-one else posts one, I can post a solution that:
- relies on smtpd_delay_reject=yes to postpone check_policy lookup
until RCPT TO.
- disables the SIZE announcement in EHLO
- diusables the SIZE check in MAIL FROM
- calls check_policy to let postfwd (etc.) reject mail, but that
only works
joe a via Postfix-users:
> On 7/7/2023 3:46 PM, joe a via Postfix-users wrote:
> > One hesitates to post this.
> >
> > Found some oddness when changing a destination in transport_maps
> > (transport_maps = lmdb:/etc/postfix/transport).
> >
> > Seems related to pattern matching.
> >
> > The
On 7/7/2023 5:12 PM, Wietse Venema via Postfix-users wrote:
joe a via Postfix-users:
On 7/7/2023 3:46 PM, joe a via Postfix-users wrote:
One hesitates to post this.
Found some oddness when changing a destination in transport_maps
(transport_maps = lmdb:/etc/postfix/transport).
Seems related
16 matches
Mail list logo
