On Wed, Sep 02, 2020 at 01:16:43PM +0100, Nick wrote:
> > If you want to prevent bounces from leaking out to forged sender
> > addresses you need to accept and discard messages, rather than reject
> > them.
>
> instead of this -
>
> -o { smtpd_sender_restrictions =
> check_sender_acce
On 2020-09-02 01:02 BST, Viktor Dukhovni wrote:
> No, I am not talking about mail not being delivered, I am talking
> about Postfix no longer working properly.
Thanks. Could you please expand on (from your earlier mail) how to do
this -
> If you want to prevent bounces from leaking out to forged
On Tue, Sep 01, 2020 at 05:22:30PM -0400, Wietse Venema wrote:
> > FWIW, the following is not explained as clearly in the Postfix
> > documentation as one might wish, and it would be good to have better
> > coverage of this topic in the docs (in the appropriate places):
> >
> > - What is a de
On Tue, Sep 01, 2020 at 08:59:19PM +0100, Nick wrote:
> > See above, this does not work.
>
> (I've since removed '-o bounce_service_name=...', it doesn't seem to
> matter here.) Again, it works well enough for me - a mail with a forged
> header-from goes into the hold queue and nowhere else.
It
Viktor Dukhovni:
> On Tue, Sep 01, 2020 at 02:45:50PM -0400, Viktor Dukhovni wrote:
>
> > > smtp-sndmail
> > > unix - - y - - smtp
> > >-o { inet_interfaces = }
> > >-o { myhostname = smtp-sndmail }
> > >-o { bounce_service_name = bounce-discard
On 2020-09-01 19:45 BST, Viktor Dukhovni wrote:
> I hope you also saw my note re various legitimate use-cases for
> "unexpected" "From:" addresses in local submission.
I did, thank you. I don't think those cases apply to me (no vacation
replies and no forwarding here).
> > smtp-sndmail
> >
On Tue, Sep 01, 2020 at 02:45:50PM -0400, Viktor Dukhovni wrote:
> > smtp-sndmail
> > unix - - y - - smtp
> >-o { inet_interfaces = }
> >-o { myhostname = smtp-sndmail }
> >-o { bounce_service_name = bounce-discard }
>
> Setting the bounce servi
On Tue, Sep 01, 2020 at 12:28:33PM +0100, Nick wrote:
> On 2020-08-30 22:33 BST, Wietse Venema wrote:
> > Well almost: it needs a custom SMTP client to avoid loop detection.
> >
> > /etc/postfix/master.cf:
> > pickup unix .. .. .. .. .. pickup
> > -o { content_filter = local-smtp:[lo
On 2020-08-30 22:33 BST, Wietse Venema wrote:
> Well almost: it needs a custom SMTP client to avoid loop detection.
>
> /etc/postfix/master.cf:
> pickup unix .. .. .. .. .. pickup
> -o { content_filter = local-smtp:[localhost]:25 }
>
> local-smtp unix .. .. .. .. .. smtp
>
On Sun, Aug 30, 2020 at 05:33:51PM -0400, Wietse Venema wrote:
> Well almost: it needs a custom SMTP client to avoid loop detection.
>
> /etc/postfix/master.cf:
> pickup unix .. .. .. .. .. pickup
> -o { content_filter = local-smtp:[localhost]:25 }
>
> local-smtp unix .. .. ..
Wietse Venema:
> Wietse Venema:
> > Nick:
> > > On 2020-08-30 21:30 BST, Wietse Venema wrote:
> > > > Nick:
> > > > > I would like to have a postconf(5) parameter such as
> > > > > "local_via_submission = yes" which changes that path to something like
> > > > >
> > > > > sendmail(1) -> postdrop(
Wietse Venema:
> Nick:
> > On 2020-08-30 21:30 BST, Wietse Venema wrote:
> > > Nick:
> > > > I would like to have a postconf(5) parameter such as
> > > > "local_via_submission = yes" which changes that path to something like
> > > >
> > > > sendmail(1) -> postdrop(1) -> maildrop -> pickup(8) ->
On Sun, Aug 30, 2020 at 05:58:01PM +0100, Nick wrote:
> I would like to have a postconf(5) parameter such as
> "local_via_submission = yes" which changes that path to something like
>
> sendmail(1) -> postdrop(1) -> maildrop -> pickup(8) -> smtpd(8) ->
> cleanup(8) -> incoming
Sorry, that's
On 2020-08-30 21:55 BST, Wietse Venema wrote:
> An SMTP client in the pickup daemon? How shall the pickup daemon send
> a non-delivery notification to the sender?
It looks like we're one objection down! Can I make it two...
The pickup daemon doesn't, the mail goes into the hold queue. It's then
On 31/08/20 4:58 am, Nick wrote:
On 2020-08-09 21:52 BST, Ansgar Wiechers wrote:
On 2020-08-09 Nick wrote:
For mail sent via submission it's possible to prevent a forged
mail-from, by using options on the submission service in master.cf.
It's also possible to prevent a forged header-from, by u
Nick:
> On 2020-08-30 21:30 BST, Wietse Venema wrote:
> > Nick:
> > > I would like to have a postconf(5) parameter such as
> > > "local_via_submission = yes" which changes that path to something like
> > >
> > > sendmail(1) -> postdrop(1) -> maildrop -> pickup(8) -> smtpd(8) ->
> > > cleanup(8
On 2020-08-30 21:30 BST, Wietse Venema wrote:
> Nick:
> > I would like to have a postconf(5) parameter such as
> > "local_via_submission = yes" which changes that path to something like
> >
> > sendmail(1) -> postdrop(1) -> maildrop -> pickup(8) -> smtpd(8) ->
> > cleanup(8) -> incoming
>
> A
Nick:
> I would like to have a postconf(5) parameter such as
> "local_via_submission = yes" which changes that path to something like
>
> sendmail(1) -> postdrop(1) -> maildrop -> pickup(8) -> smtpd(8) ->
> cleanup(8) -> incoming
And HOW THE HELL is that supposed to work when Postfix is not u
On 2020-08-09 21:52 BST, Ansgar Wiechers wrote:
> On 2020-08-09 Nick wrote:
> > For mail sent via submission it's possible to prevent a forged
> > mail-from, by using options on the submission service in master.cf.
> >
> > It's also possible to prevent a forged header-from, by using a
> > submissi
On 2020-08-09 Nick wrote:
> For mail sent via submission it's possible to prevent a forged
> mail-from, by using options on the submission service in master.cf.
>
> It's also possible to prevent a forged header-from, by using a
> submission-specific cleanup service, as in the BUILTIN_FILTER_README
For mail sent via submission it's possible to prevent a forged
mail-from, by using options on the submission service in master.cf.
It's also possible to prevent a forged header-from, by using a
submission-specific cleanup service, as in the BUILTIN_FILTER_README.
But these don't work for mail ori
21 matches
Mail list logo
