: "{reject"
Changing this to static:reject works well enough for my purposes here, so
that's excellent. Thanks again.
On Thu, 4 Jun 2020 at 14:36, Wietse Venema wrote:
> Jonathan Engbrecht:
> > I route mail for a number of relay_domains - recipient addresses
I route mail for a number of relay_domains - recipient addresses are
validated using verify via address_verify_transport
For *one* of these domains, I'd like to validate addresses using an ldap
map configured with relay_recipient_maps rather than smtp lookahead.
I have the ldap connection working
Jones wrote:
> On 12/4/2019 1:55 PM, Jonathan Engbrecht wrote:
> > thanks all. Looks like I can mostly do this with restriction
> > classes, though the drop ends up being a 5xx reject rather than a
> > silent drop, which is a bit too bad.
> >
> >
e would be great, but doesn't appear to be
possible
On Tue, 3 Dec 2019 at 17:38, Ralph Seichter wrote:
> * Jonathan Engbrecht:
>
> > If From: f...@example.com
> > AND NOT To: (bar|baz|quux)@mydomain.com
> > DISCARD
>
> Milter-regex (https://www.benzedrine.ch/mi
Can I make a header_check rule (or equivalent) somehow that does the
following:
If From: f...@example.com
AND NOT To: (bar|baz|quux)@mydomain.com
DISCARD
at 05:26:02PM -0400,
> >Jonathan Engbrecht wrote:
> > > postfix 2.3.3
> >
> > Note that Viktor's suggestion of multiple instances assumes a
> > slightly less ancient Postfix version; postmulti(1) began with
> > Postfix 2.6. Time to upgrade?
>
> I was not sug
I'm working on a generic postfix configuration for servers. I want
messages to have a From: address of @, but an
envelope-sender/bounce address that's different.
in main.cf:
canonical_maps=hash:/etc/postfix/canonical
canonical_classes = envelope_sender
in canonical:
@
Messages sent from
> On Aug 14, 2013, at 1:37 PM, Jonathan Engbrecht
> wrote:
>
> there is no mailHost attribute in ldap (or *any* attribute that is the
> "next hop" dns name). I need to map an attribute in ldap to something that
> *isn't* in ldap.
>
> (yes, this could be done
can't do it without).
On Wed, Aug 14, 2013 at 12:34 PM, jeffrey j donovan
wrote:
>
> On Aug 14, 2013, at 11:29 AM, Jonathan Engbrecht
> wrote:
>
> We have an attribute in our ldap that I'd like to use to determine the
> "next hop" for mail transport. Th
We have an attribute in our ldap that I'd like to use to determine the
"next hop" for mail transport. The attribute is not itself the name of the
next transport.
Is there a way to set up a mapping for this?
ie:
dn: xxx...
routingattribute: foo
route messages with this attribute to smtp:bar.c
10 matches
Mail list logo
