liquid cooled:
> Thanks for the quick response,
>
> 2) $ postconf -n | grep ldap
> transport_maps = hash:/etc/postfix/lookup/transport, ldap:/etc/postfix/
> mailtransport.cf
In that case, Postfix will always want to look up user@domain,
domain, and parent domains, because that is how transport ma
I got it now found the "domain" setting in
https://www.postfix.org/ldap_table.5.html
Thanks you very much Wietse! And thanks for your time!
Am Fr., 3. März 2023 um 15:44 Uhr schrieb liquid cooled :
> Thanks for the quick response,
>
> 2) $ postconf -n | grep ldap
> transport_maps = hash:/etc/pos
Thanks for the quick response,
2) $ postconf -n | grep ldap
transport_maps = hash:/etc/postfix/lookup/transport, ldap:/etc/postfix/
mailtransport.cf
1) by "those domains" you are talking about the sender domains? Because
these domains are unknown to my mailsystem as these are mails from external
liquid cooled:
> Hello,
>
> I found out that my postfix does a lot of useless (LDAP) requests (in my
> opinion) when transport maps are enabled and in place.
> I use transport maps to map incoming mails to different destination hosts,
> based on destination mail address.
> So there should be no l
Hello Viktor,
Indeed, your are right again. I had '%d' in a complex query, changed it
to '%s' and extracted the substring for the domain. That did it! There
are three select statements in a UNION with the others referencing '%s'
already. Too bad there wasn't a switch to make it so '%d' doe
On Thu, Mar 18, 2021 at 05:17:58PM -0700, David Koski wrote:
> Postfix is only mapping email addresses and not FQDNs. Mapping works
> for u...@mydomain.com but not mydomain.com, .mydomain.com or @mydomain.com.
>
> # postmap -q localhost mysql:/etc/postfix/mysql_transport_maps.cf
>
> # postmap -
Lists Nethead:
>
> postfix-3.2.2
>
> Case in question:
>
> transport_maps = hash:/usr/local/etc/postfix/transport,
> ldap:/usr/local/etc/postfix/ldap-transport.cf
>
> I had the (possibly erroneous) belief that Postfix searches the tables
> in the order given in main.cf and that the domain p
Adam Tauno Williams:
> I have a Postfix server which receives mail for EXAMPLE.COM
> (bogasified); for for specific addresses I need to send that mail to
> another SMTP server. So transform_maps!
>
> I have "transport_maps = hash://map-path" and If I "postmap -q
> u...@example.com hash://ma
Alex Regan:
> Hi,
>
> I have a fedora20 server with postfix-2.10.5 I'm trying to configure
> rate limiting for outbound mail to google, yahoo, etc, in hopes of not
> only building a better reputation with these systems, but also to
> prevent my outbound pipe from being saturated.
>
> I've conf
On 3/7/2013 2:17 PM, Alfredo Saldanha wrote:
>> The transport table is a critical table used by pretty much every
>>part of postfix (by way of the trivial_rewrite service). If the
>>mysql database is unavailable, no mail will flow. If the lookups
>>are slow, all postfix performance will suffer.
>
Sorry, this was my email client.
Thank you for answers.
- Mensagem original -
De: "Reindl Harald"
Para: postfix-users@postfix.org
Enviadas: Quinta-feira, 7 de Março de 2013 17:22:36
Assunto: Re: Transport maps in MySQL
DO NOT POST HTML-MESSAGES
Am 07.03.2013 21:1
DO NOT POST HTML-MESSAGES
Am 07.03.2013 21:17, schrieb Alfredo Saldanha:
> In line...
> On 3/7/2013 1:37 PM, Alfredo Saldanha wrote:
>>> Hi people,
>>>
>>> Simple question:
>>>
>>> Is safe use mysql to get the transport maps information? if the
>>> connection with database drops ? is there cache?
In line...
De: "Noel Jones"
Para: postfix-users@postfix.org
Enviadas: Quinta-feira, 7 de Março de 2013 17:01:45
Assunto: Re: Transport maps in MySQL
On 3/7/2013 1:37 PM, Alfredo Saldanha wrote:
>> Hi people,
>>
>> Simple question:
>>
>> Is
Am 07.03.2013 21:01, schrieb Noel Jones:
> On 3/7/2013 1:37 PM, Alfredo Saldanha wrote:
>> Hi people,
>>
>> Simple question:
>>
>> Is safe use mysql to get the transport maps information? if the
>> connection with database drops ? is there cache?
>>
>> BR,
>>
>> Junix
>>
>
> The transport tab
On 3/7/2013 1:37 PM, Alfredo Saldanha wrote:
> Hi people,
>
> Simple question:
>
> Is safe use mysql to get the transport maps information? if the
> connection with database drops ? is there cache?
>
> BR,
>
> Junix
>
The transport table is a critical table used by pretty much every
part of
On 15/08/2012 22:14, Noel Jones wrote:
On 8/15/2012 1:28 PM, Harakiri wrote:
Is there an alternative way to have a custom TCP service answer to postfix
requests to where a mail should be relayed too - when postfix supplies all the
transport information (sender,recipient, sending IP) ? Postfix
On 8/15/2012 1:28 PM, Harakiri wrote:
>
> Is there an alternative way to have a custom TCP service answer to postfix
> requests to where a mail should be relayed too - when postfix supplies all
> the transport information (sender,recipient, sending IP) ? Postfix already
> has nice table lookup
--- On Wed, 8/15/12, Noel Jones wrote:
> From: Noel Jones
> Subject: Re: Transport Maps and TCP Table -> How to realize that postfix
> queries for recipient AND sender ?
> To: postfix-users@postfix.org
> Date: Wednesday, August 15, 2012, 12:26 PM
> On 8/15/2012 10:53
On 8/15/2012 10:53 AM, Harakiri wrote:
> Ive implemented a TCP table which will tell postfix which destination IP
> should be used for internal relay.
>
> A TCP Table lookup only works with GET
Correct. The lookup key for transport_maps is the recipient address
regardless of table type.
> -
On 22/06/2012 11:31, Ralf Hildebrandt wrote:
* post...@netorbit.it :
Hi,
Postfix 2.7.1 box.
done some extra test, with same setup and encountered different
behavior between
1) transport_maps = hash:/etc/postfix/transport, tcp:[127.0.0.1]:
and
2) transport_maps = hash:/etc/postfix/transpo
* post...@netorbit.it :
> Hi,
>
> Postfix 2.7.1 box.
> done some extra test, with same setup and encountered different
> behavior between
>
> 1) transport_maps = hash:/etc/postfix/transport, tcp:[127.0.0.1]:
>
> and
>
> 2) transport_maps = hash:/etc/postfix/transport alone
>
> when tr
Hi,
Postfix 2.7.1 box.
done some extra test, with same setup and encountered different behavior
between
1) transport_maps = hash:/etc/postfix/transport, tcp:[127.0.0.1]:
and
2) transport_maps = hash:/etc/postfix/transport alone
when trying to send an email to the netorbit.it domain
On 21/06/2012 16:25, Wietse Venema wrote:
post...@netorbit.it:
Hi,
just a quick question regarding transport_maps.
I've read documentation on
http://www.postfix.org/postconf.5.html#transport_maps, but cannot
understand what actually happens during postfix lookups, when
transport_maps is being
On 21/06/2012 16:25, Wietse Venema wrote:
transport_maps is being specified as:
transport_maps = type:A, type:B
Would postfix query first table A and if not getting a match, moves to
query table B ?
Yes. Table B is queried only if the query of table A produces "not found".
If the transport g
post...@netorbit.it:
> Hi,
>
> just a quick question regarding transport_maps.
>
> I've read documentation on
> http://www.postfix.org/postconf.5.html#transport_maps, but cannot
> understand what actually happens during postfix lookups, when
> transport_maps is being specified as:
>
> transpo
On Mon, Jan 10, 2011 at 06:35:23PM -0200, Lauro Costa G. Borges wrote:
>>> Mail arrives to b...@domain1.org (and b...@domain1.org has an alias to
>>> bla...@domain2.org).
>>
>> What do you mean by "has an alias"?
>
>I'll try to explain with an example:
>
>
> I have these 2 domains:
>
>
Citando Victor Duchovni :
Make sure you have a robust, low-latency LDAP infrastructure. The
trivial-rewrite service will query LDAP to determine the address class of
each domain, and qmgr(8) uses trivial-rewrite to resolve every recipient,
so LDAP becomes performance critical.
Suppose I relay
On Mon, Dec 20, 2010 at 04:17:08PM -0200, Lauro Costa G. Borges wrote:
> I'm using Postfix 2.7.0.
Good, this is a reasonably recent release. You may want to consider
updating to 2.7.2:
20100515
Bugfix (introduced Postfix 2.6): the Postfix SMTP client
XFORWARD implement
Le 09/10/2010 13:32, Olivier BONHOMME a écrit :
Le 08/10/2010 21:30, Victor Duchovni a écrit :
On Fri, Oct 08, 2010 at 05:38:21PM +0200, Olivier BONHOMME wrote:
I am writing here because I have an issue trying to use
transport_maps with
a domain which is declared as VIRTUAL.
You fail to di
Le 08/10/2010 21:30, Victor Duchovni a écrit :
On Fri, Oct 08, 2010 at 05:38:21PM +0200, Olivier BONHOMME wrote:
I am writing here because I have an issue trying to use transport_maps with
a domain which is declared as VIRTUAL.
You fail to distinguish between virtual_alias_domains and
virtual
On Fri, Oct 08, 2010 at 05:38:21PM +0200, Olivier BONHOMME wrote:
> I am writing here because I have an issue trying to use transport_maps with
> a domain which is declared as VIRTUAL.
You fail to distinguish between virtual_alias_domains and
virtual_mailbox_domains. Which is it?
> Now i would
On Tue, 2009-12-08 at 00:43 -0500, Sahil Tandon wrote:
> On Mon, 07 Dec 2009, osm...@oc.quimefa.cu wrote:
>
> > Hi I am trying to make postfix to relay all mail except for the ones
> > going to a specific domain. For example I want to be able to make
> > postfix relay all mail except for dom
On Mon, 07 Dec 2009, osm...@oc.quimefa.cu wrote:
> Hi I am trying to make postfix to relay all mail except for the ones
> going to a specific domain. For example I want to be able to make
> postfix relay all mail except for domain .ca I was wondering if
> something like this is possible or
work.
I will investigate the SASL/sender_relay thing.
Etienne
-Original Message-
From: Noel Jones [mailto:njo...@megan.vbhcs.org]
Sent: July 24, 2009 12:19 PM
To: Kenneth Marshall
Cc: Etienne Simard; postfix-users@postfix.org
Subject: Re: transport maps using "from" address field fi
Etienne Simard:
> Hi,
>
> I must have been searching at the wrong place or using the wrong
> keywords as I have been trying to find how to correctly transport to a
> particular smtp relay or have postfix do a MX query based on the "from"
> address field. I did look at the postfix doc, in se's and
Kenneth Marshall wrote:
On Fri, Jul 24, 2009 at 11:50:19AM -0400, Etienne Simard wrote:
Hi,
I must have been searching at the wrong place or using the wrong
keywords as I have been trying to find how to correctly transport to a
particular smtp relay or have postfix do a MX query based on the "f
On Fri, Jul 24, 2009 at 11:50:19AM -0400, Etienne Simard wrote:
> Hi,
>
> I must have been searching at the wrong place or using the wrong
> keywords as I have been trying to find how to correctly transport to a
> particular smtp relay or have postfix do a MX query based on the "from"
> address fi
On Tue, 2009-07-21 at 12:21 -0400, Linux Addict wrote:
> I tried digging, I get the MX servers on the ANSWER section. I manage
> DNS as well, so I know its resolving correctly.
Just one thing Sir and a shot in the water. Restart Postfix (not
reload). I was having a problem where it kept looking up
On Tue, Jul 21, 2009 at 12:37 PM, Linux Addict wrote:
>
>
> On Tue, Jul 21, 2009 at 12:24 PM, Jaroslaw Grzabel wrote:
>
>> Linux Addict wrote:
>>
>>> I tried digging, I get the MX servers on the ANSWER section. I manage DNS
>>> as well, so I know its resolving correctly.
>>>
>> What is in the log
On Tue, Jul 21, 2009 at 12:24 PM, Jaroslaw Grzabel wrote:
> Linux Addict wrote:
>
>> I tried digging, I get the MX servers on the ANSWER section. I manage DNS
>> as well, so I know its resolving correctly.
>>
> What is in the log files then when you're trying to relay your messages ?
>
> Regards,
Linux Addict wrote:
I tried digging, I get the MX servers on the ANSWER section. I manage
DNS as well, so I know its resolving correctly.
What is in the log files then when you're trying to relay your messages ?
Regards,
Jarek
I tried digging, I get the MX servers on the ANSWER section. I manage DNS as
well, so I know its resolving correctly.
On Tue, Jul 21, 2009 at 12:20 PM, Jaroslaw Grzabel wrote:
> Linux Addict wrote:
>
>>
>> Simon, I already tried that. Its not doing MX lookup I guess.
>>
>> Maybe it works but yo
Linux Addict wrote:
Simon, I already tried that. Its not doing MX lookup I guess.
Maybe it works but you're using your local DNS which doesn't know MX
record for that remote domain you want to relay your messages through.
Try locally run dig domainname.com MX and see the result. If it's empty
On Tue, 2009-07-21 at 17:10 +0100, Clunk Werclick wrote:
> On Tue, 2009-07-21 at 12:05 -0400, Linux Addict wrote:
> >
> >
> > On Tue, Jul 21, 2009 at 12:00 PM, Ralf Hildebrandt
> > wrote:
> > * Ralf Hildebrandt :
> >
> > > > In simple, When I send a mail to @example.com,
On Tue, Jul 21, 2009 at 12:03 PM, Simon Waters wrote:
> On Tuesday 21 July 2009 16:53:52 Linux Addict wrote:
> >
> > I tried using transport maps, "example.com :[smtp1.example.com]"
> > and " example.com smtp:[smtp1.example.com], but of them didn't use
> > smtp.example.com.
>
> Not clear
On Tue, 2009-07-21 at 12:05 -0400, Linux Addict wrote:
>
>
> On Tue, Jul 21, 2009 at 12:00 PM, Ralf Hildebrandt
> wrote:
> * Ralf Hildebrandt :
>
> > > In simple, When I send a mail to @example.com, postfix
> must send the mail
> > > to the MX records of
On Tue, Jul 21, 2009 at 12:00 PM, Ralf Hildebrandt <
ralf.hildebra...@charite.de> wrote:
> * Ralf Hildebrandt :
>
> > > In simple, When I send a mail to @example.com, postfix must send the
> mail
> > > to the MX records of smtp.example.com.
>
> > example.com smtp.example.com
>
> OK, not too
On Tuesday 21 July 2009 16:53:52 Linux Addict wrote:
>
> I tried using transport maps, "example.com :[smtp1.example.com]"
> and " example.com smtp:[smtp1.example.com], but of them didn't use
> smtp.example.com.
Not clear what you mean here.
Documentation of "transport" (man transport)
* Ralf Hildebrandt :
> > In simple, When I send a mail to @example.com, postfix must send the mail
> > to the MX records of smtp.example.com.
> example.com smtp.example.com
OK, not too sure if Postfix will perform an MX lookup for the RHS
(smtp.example.com in this example). Please try
--
* Linux Addict :
> I have a postfix MTA server running. I was asked to setup relay mail to a
> specific domain thru MX record.
> Domain - Example.com
> An A record smtp.example.com
> MX Records smtp.example.com - smtp1.example.com and smtp2.example.com.
>
> In simple, When I send a mail to @exampl
On Wed, 20 May 2009, none none wrote:
> We are running postfix 2.3.3. on a Redhat ES 5.1
> We are receiving mail for two domains:
> a) domain.com
> b) customers.domain.com
>
> Recently a company that we cooperate with, asked us to
> forward all the e-mails sent to them (for "security" reasons)
On Mon May 11 2009 14:45:14 Eric Cunningham wrote:
> This may be of use in my situation. Can you point me to the docs
> that explain how to configure wildcard subdomains?
postconf.5.html#parent_domain_matches_subdomains ... one way
pcre_table.5.html ... another way
regexp_table.5.html ... another
Noel Jones wrote:
Eric Cunningham wrote:
I want e...@sanguine.whoi.edu to continue delivery to my imap
account. In fact, that happened perfectly in my previous postfix
configuration.
... it worked previously due to a bug in permit_mx_backup. That bug has
been corrected.
Ahh...finally, s
Eric Cunningham wrote:
I want e...@sanguine.whoi.edu to continue
delivery to my imap account. In fact, that happened perfectly in my
previous postfix configuration.
... it worked previously due to a bug in permit_mx_backup.
That bug has been corrected.
Since upgrading postfix, in order f
Eric Cunningham:
> that to continue working, I'm now hearing that I must specifically list
> sanguine.whoi.edu "somewhere" in my postfix configs. That's not
> unreasonable, but let's now extend this example to another 250 hosts
> that are in a similar situation. I must now specifically find, l
Noel Jones wrote:
Apparently, sanguine.whoi.edu not listed in any of the postfix address classes.
Which address class do you expect this to be? Then you'll know where the
domain must be listed.
This is one document you need to understand:
http://www.postfix.org/ADDRESS_CLASS_README.html
On Mon May 11 2009 12:08:02 Magnus Bäck wrote:
> On Monday, May 11, 2009 at 18:59 CEST,
> /dev/rob0 wrote:
>
> [...]
>
> > BTW, I always use complete paths for lookups. I think "ldap:vldap"
> > defaults to "ldap:$config_directory/vldap", but it never hurts to
> > be specific, so you know what
Eric Cunningham wrote:
May 11 12:24:19 obtest postfix/postfix-script[4849]: warning:
/var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ
Fix the above error. Probably not directly related to your
problem, but might cause unexpected behavior. The fix is
probably just:
# cp /et
...
virtual_alias_domains = $virtual_alias_maps
virtual_alias_maps = hash:/etc/postfix/virtual, ldap:vldap
These are all your address class definitions. We can't see into your
virtual_alias_maps to know what domains might be listed there. You can
show us "postmap -q sanguine.whoi.edu hash:/et
On Monday, May 11, 2009 at 18:59 CEST,
/dev/rob0 wrote:
[...]
> BTW, I always use complete paths for lookups. I think "ldap:vldap"
> defaults to "ldap:$config_directory/vldap", but it never hurts to
> be specific, so you know what you're getting.
ldap:vldap is the legacy configuration meth
On Mon May 11 2009 11:33:37 Eric Cunningham wrote:
> I guess I'm still missing something so here's my 'postfix -n' output
> and logfile showing the rejection.
> >>> for postfix to accept mail for a domain (from anywhere), the
> >>> domain needs to be found in one (and only one of):
> >>> - mydesti
I guess I'm still missing something so here's my 'postfix -n' output and
logfile showing the rejection.
-Eric
for postfix to accept mail for a domain (from anywhere), the domain
needs to be found in one (and only one of):
- mydestination (this is for mail delivered to a unix a
Eric Cunningham a écrit :
> Thanks mouss. I removed $mynetworks from relay_domains and added the
> domains found in the transport map to relay_domains (while also keeping
> them in the transport map). Relaying to those specific domains now works.
>
> However, MX'd machines still suffer "relay a
Thanks mouss. I removed $mynetworks from relay_domains and added the
domains found in the transport map to relay_domains (while also keeping
them in the transport map). Relaying to those specific domains now works.
However, MX'd machines still suffer "relay access denied." I introduced
"re
Eric Cunningham a écrit :
> Thanks Victor. Ok, so I:
>
> - removed .$mydomain from $mydestination
> - have set relay_domains = $mydestination, $mynetworks
do not do that. mydestination is for domains that should be delivered
locally. mynetworks have nothing to do with reception domains.
Thanks Victor. Ok, so I:
- removed .$mydomain from $mydestination
- have set relay_domains = $mydestination, $mynetworks
- have set parent_domain_matches_subdomains to it's default
- have added permit_mx_backup to smtpd_recipient_restrictions
- set permit_
On Fri, May 01, 2009 at 01:54:03PM -0400, Eric Cunningham wrote:
> I think I've found a/the fix for re-enabling the original behavior of my
> transport maps and MX relaying. I added .$mydomain to mydestination in
> main.cf. This is in addition to $mydomain which was already in
> mydestination
I think I've found a/the fix for re-enabling the original behavior of my
transport maps and MX relaying. I added .$mydomain to mydestination in
main.cf. This is in addition to $mydomain which was already in
mydestination.
$mydomain vs. .$mydomain is subtle but apparently important.
Eric Cunningham:
> > transport_maps simply routes accepted messages by overriding DNS.
>
> That's what I want to continue to do, as had occurred happily before the
> postfix upgrade.
>
> > To accept mail, the envelope recipient *must* be in mydestination,
> > relay_domains, virtual_alias_domains
transport_maps simply routes accepted messages by overriding DNS.
That's what I want to continue to do, as had occurred happily before the
postfix upgrade.
To accept mail, the envelope recipient *must* be in mydestination,
relay_domains, virtual_alias_domains or virtual_mailbox_domains.
All
Eric Cunningham:
[ Charset ISO-8859-1 unsupported, converting... ]
> > Why don't you simply restore the old working main.cf and master.cf
> > files, and then execute as root:
> >
> > # postfix upgrade-configuration
> >
> > This is easier that trying to figure out how to rebuild the old
> > co
Why don't you simply restore the old working main.cf and master.cf
files, and then execute as root:
# postfix upgrade-configuration
This is easier that trying to figure out how to rebuild the old
configuration from scratch.
PS If the recipient domains are not local, then they must be listed
Eric Cunningham:
> I just upgraded to postfix 2.5.5 from 2.3. Now, it seems my previously
> working transport maps are ignored as are hosts that are MX'ed to the
> machine running postfix. In both cases, email are rejected with "Relay
> access denied."
Why don't you simply restore the old wor
Eric Cunningham wrote:
> I just upgraded to postfix 2.5.5 from 2.3. Now, it seems my
> previously working transport maps are ignored as are hosts that are
> MX'ed to the machine running postfix. In both cases, email are
> rejected with "Relay access denied."
> Sorry, thank you for the clarificati
Sorry, thank you for the clarification, Brian. 'postconf -n' output is
now attached. I've already run 'postmap transport' and 'postfix reload'
but that didn't help.
I did find a quasi-workaround to this by adding the subdomains from
transport to relay_domains but that will be clumsy at best
Eric Cunningham wrote:
> I just upgraded to postfix 2.5.5 from 2.3. Now, it seems my
> previously working transport maps are ignored as are hosts that are
> MX'ed to the machine running postfix. In both cases, email are
> rejected with "Relay access denied."
>
> I note in the attached 'postconf -
76 matches
Mail list logo
