Andrew Athan via Postfix-users:
> Thanks Viktor:
>
> > welcome to the internet
>
> Yeah :) I've been here for 30 years.
>
> > unlikely to be productive
>
> I simply want to help others avoid my points of confusion, in the belief I
> am not a uniquirely incapable or unintelligent reader.
>
> I
Matus UHLAR - fantomas via Postfix-users
writes:
> (...)
> for envelope from, simple access map should be enough:
> http://www.postfix.org/access.5.html
>
> and use DISCARD
Ok. Thanks for the heads-up, Matus!
Sincerely, Byung-Hee
--
^고맙습니다 _地平天成_ 감사합니다_^))//
__
Thanks Viktor:
> welcome to the internet
Yeah :) I've been here for 30 years.
> unlikely to be productive
I simply want to help others avoid my points of confusion, in the belief I
am not a uniquirely incapable or unintelligent reader.
I will say this: Irrespective of how well you understand p
On 23.04.23 13:43, Byung-Hee HWANG via Postfix-users wrote:
Andrew Athan via Postfix-users writes:
(...)
My goal is to silently discard all inbound mail from a certain
domain. Or actually, I may wish to redirect all of that mail either to
a flat file (similar to the proposed blackhole transpor
Andrew Athan via Postfix-users writes:
> (...)
> My goal is to silently discard all inbound mail from a certain
> domain. Or actually, I may wish to redirect all of that mail either to
> a flat file (similar to the proposed blackhole transport) or (...)
Go with easy way. See header_checks. `man
On Sat, Apr 22, 2023 at 07:58:25PM -0700, Andrew Athan wrote:
> If I understand it well enough I'll write and submit a doc PR.
This is unlikely to be productive.
> If I put all this together what I think I'm hearing is that transport_map
> overrides everything
The transport(5) table has the hig
Oh, sorry, one last (lol) thing ... since it doesn't seem like "@" is ever
part of searches do you think it might be wise to change the docs so that
instead of saying " sender-dependent override for the global relayhost
parameter setting. The tables are searched by the envelope sender address
and @
I hope the message quoting/formatting in my response works as expected. If
not let me know and I will rely less on gmail's formatter.
>
> "This information is overruled with... the transport(5) table."
>
> In other words, "transport_maps", a logical dictionary built from
> a list of component tabl
On Sat, Apr 22, 2023 at 05:56:12PM -0700, Andrew Athan via Postfix-users wrote:
> "This information is overruled with... the transport(5) table."
In other words, "transport_maps", a logical dictionary built from
a list of component tables (some of which may also be composite).
> But "sender_depe
I have read and re-read the documentation regarding transport(5) here:
https://www.postfix.org/transport.5.html
First, the docs for things like say "sender_dependent_relayhost_maps" say:
"This information is overruled with... the transport(5) table."
but what the heck is "the transport(5) table"
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 i
and create an LDAP entry containing a
> valid mail address I will be able to receive mail for that domain.
> Maybe this is the problem here?
>
> Am Fr., 3. März 2023 um 14:04 Uhr schrieb Wietse Venema <
> wie...@porcupine.org>:
>
>> 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
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.
>
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 lookup at all for sender
W dniu 24.01.2023 o 13:03, Wietse Venema pisze:
natan:
W dniu 24.01.2023 o?12:05, Wietse Venema pisze:
natan:
Hi
For test i runnig gallera claster + haproxy
haproxy:
.
listen galera-test
bind 10.10.10.10:3307
balance leastconn
mode tcp
option tcplog
option tcpka
option httpchk
server sql
natan:
> W dniu 24.01.2023 o?12:05, Wietse Venema pisze:
> > natan:
> >> Hi
> >> For test i runnig gallera claster + haproxy
> >>
> >> haproxy:
> >> .
> >> listen galera-test
> >> bind 10.10.10.10:3307
> >> balance leastconn
> >> mode tcp
> >> option tcplog
> >> option tcpka
> >> option httpchk
W dniu 24.01.2023 o 12:05, Wietse Venema pisze:
natan:
Hi
For test i runnig gallera claster + haproxy
haproxy:
.
listen galera-test
bind 10.10.10.10:3307
balance leastconn
mode tcp
option tcplog
option tcpka
option httpchk
server sql1 10.10.10.11:3306 check port 9200 inter 12000 rise 2 fal
natan:
> Hi
> For test i runnig gallera claster + haproxy
>
> haproxy:
> .
> listen galera-test
> bind 10.10.10.10:3307
> balance leastconn
> mode tcp
> option tcplog
> option tcpka
> option httpchk
>
> server sql1 10.10.10.11:3306 check port 9200 inter 12000 rise 2 fall 2
> server sql2 10.10
ct itself - after some times all works fine
And I would like to eliminate it and I dont have idea where i must find
"problem"
I use everywhere proxy:mysql:/etc/postfix/mysql_maps.
W dniu 20.01.2023 o 18:43, Wietse Venema pisze:
natan:
W dniu 20.01.2023 o?15:04, Wietse Venema pi
natan:
> W dniu 20.01.2023 o?15:04, Wietse Venema pisze:
> > natan:
> >> Hi
> >> I try to run "backup" transport maps like:
> >>
> >> smtpd_sender_login_maps =
> >> #first-main database
> >> proxy:mysql:/etc/postfix/
W dniu 20.01.2023 o 15:04, Wietse Venema pisze:
natan:
Hi
I try to run "backup" transport maps like:
smtpd_sender_login_maps =
#first-main database
proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf
#second-backup
proxy:mysql:/etc/postfix/mysql_sender_login_maps-backu
natan:
> Hi
> I try to run "backup" transport maps like:
>
> smtpd_sender_login_maps =
> #first-main database
> proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf
> #second-backup
> proxy:mysql:/etc/postfix/mysql_sender_login_maps-backup.cf
>
>
Hi
I try to run "backup" transport maps like:
smtpd_sender_login_maps =
#first-main database
proxy:mysql:/etc/postfix/mysql_sender_login_maps.cf
#second-backup
proxy:mysql:/etc/postfix/mysql_sender_login_maps-backup.cf
Both databases are the same because they are synchroniz
Alex:
> Hi,
>
> Is it possible to specify multiple relay hosts in a transport map for load
> balancing/fault tolerance?
>
> example.com smtp:server1.com
> example.com smtp:server2.com
You can't have two entries with the same key.
As of a few years you can specify
example.com
Hi,
Is it possible to specify multiple relay hosts in a transport map for load
balancing/fault tolerance?
example.com smtp:server1.com
example.com smtp:server2.com
I have a relay server set up as an MX for example.com. After mail is
processed, I'd like to forward it on to either
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 -
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 -q list2@localhost mysql:/etc/postfix/mysql_transport_maps.cf
mailman:
my
s both tables for example.com
(domain only) in the order given in main.cf.
> So the question is, how can we set up the transport maps in a hash
> file so that all mail for users in the example.com domain gets sent to
> smtp:[a.host.somwhere] instead of the default entry which is below
xample.com smtp:[a.host.somwhere]
So the question is, how can we set up the transport maps in a hash
file so that all mail for users in the example.com domain gets sent to
smtp:[a.host.somwhere] instead of the default entry which is below in
the hash file.
I have the feeling that Postfi
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
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://map-path" it returns "smtp:[other.
Wietse Venema:
> Banyasz Botond:
> > i have a transport_maps: transport_maps=tcp:[localhost]:1515
> > postmap -q text@example tcp:[localhost]:1515gives: retry:4.0.0
> > internal temp defer
>
> For the past 10+ years, Postfix has always blocked mail that resolves
> to the 'error' transport. D
Banyasz Botond:
> i have a transport_maps: transport_maps=tcp:[localhost]:1515
> postmap -q text@example tcp:[localhost]:1515gives: retry:4.0.0
> internal temp defer
For the past 10+ years, Postfix has always blocked mail that resolves
to the 'error' transport. Doing the same for the 'retry'
Banyasz Botond:
> Hello,
>
> Recently i upgraded to postfix 3.1 and i have an issue with the
> transport maps.
>
> i have a tcp loockup table in the transport maps and in some condition
> i make a retry destination.
>
> in postfix 2.11 if the loockup table give
Hello,
Recently i upgraded to postfix 3.1 and i have an issue with the
transport maps.
i have a tcp loockup table in the transport maps and in some condition
i make a retry destination.
in postfix 2.11 if the loockup table gives retry then the message is
accepted from the client and
Pedro David Marco:
> Ops!!
>
> Thanks! I gladly do it, Wietse...
>
> The problem is this:
>
> i actually have a transport file like this:
>
> DomainA.comsmtp:[10.10.10.1]:25
> DomainB.comsmtp:[10.10.10.2]:25
> DomainC.comsmtp:[10.10.10.3]:25
How many? 10? 100? 1000? It it's 10, ju
??? (without using DNS
"tricks if possible please, just Postfix)
thanks in advance again!
Pedro.
On Tue, 1/12/16, Wietse Venema wrote:
Subject: Re: smtp_fallback_relay in transport maps...
To: "Postfix users"
Date: Tuesday, January 12
Pedro David Marco:
> Thanks a lot Wietse for your quick answer...
>
> but then... does this mean that i cannot use smtp_fallback_relays
> in transport_map file??
Perhaps you can explain what problem you are trying to solve.
I.e explain the problem instead of the solution, because
there may be a b
Thanks a lot Wietse for your quick answer...
but then... does this mean that i cannot use smtp_fallback_relays in
transport_map file??
Thanks again!
Pedro.
On Tue, 1/12/16, Wietse Venema wrote:
Subject: Re: smtp_fallback_relay in transport maps
Pedro David Marco:
> Hello everybody!!!
>
> I am trying to set smtp_fallback_relays per domain in the transport map file.
>
> According to the documentation this is possible:
> "In transport maps, specify "relay:nexthop..." as the right-hand side for
>
Hello everybody!!!
I am trying to set smtp_fallback_relays per domain in the transport map file.
According to the documentation this is possible:
"In transport maps, specify "relay:nexthop..." as the right-hand side for
backup or primary MX domain entries."
i have tried:
Michael Peter:
[ Charset ISO-8859-1 converted... ]
> Hi,
>
> I have question about transport maps and content filter
>
> In main.cf
>
> content_filter = trans:localhost:10025
>
> so all emails has the next-hop to localhost:10025 and the transport agent
> is trans
Hi,
I have question about transport maps and content filter
In main.cf
content_filter = trans:localhost:10025
so all emails has the next-hop to localhost:10025 and the transport agent
is trans.
But also we included in main.cf
transport_maps = hash:/etc/postfix/transport
will all the email
On 7/3/15 5:20 PM, Noel Jones wrote:
On 7/3/2015 9:56 AM, John Gateley wrote:
...
...
But if you're sending to the same IP as published in DNS, no real
reason to use a transport entry.
Thanks for the confirmation
Note secondary MX servers are no longer considered a benefit. ...
This i
On 7/3/2015 9:56 AM, John Gateley wrote:
> Hi,
>
> I've found several websites for configuring backup MX servers
> that recommend setting the transport_maps for the primary domains.
> This seems wrong to me: the DNS MX record already has this info.
> Is there another reason to set the transport_ma
Hi,
I've found several websites for configuring backup MX servers
that recommend setting the transport_maps for the primary domains.
This seems wrong to me: the DNS MX record already has this info.
Is there another reason to set the transport_maps for the backup config?
Thanks
John
http://www.
Viktor Dukhovni wrote on 11/05/2015 19:39:
This advice is bad. Any problems with RBLs manifest *after* the
destination relay has accepted your mail. Therefore adding a
failback does no good. All the mail goes to the primary anyway.
I know... But the IT guy of my customer asked for it.
Glad
On Mon, May 11, 2015 at 04:32:31PM +0200, Luigi Rosa wrote:
> Given a mail server with latest Postfix and a transport map like this for
> some domains that routes the delivery thru ISP MTA:
>
> domain1.com relay:[isp.mta.com]
> domain2.com relay:[isp.mta.com]
> domain3.com relay:[isp.mta.com]
Given a mail server with latest Postfix and a transport map like this for some
domains that routes the delivery thru ISP MTA:
domain1.com relay:[isp.mta.com]
domain2.com relay:[isp.mta.com]
domain3.com relay:[isp.mta.com]
ISP (is a big one) says that since sometimes his MTA is listed in some
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
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 configured a few of the rate_d
On 21.12.2014 18:21, Viktor Dukhovni wrote:
On Sun, Dec 21, 2014 at 08:57:52AM -0500, Wietse Venema wrote:
Istvan Prosinger:
Hello,
Is it possibble to make Postfix relay to some specific domain using a
specific relay, and relay all the other domains by default rules (put
the mail to an inbox
Works like a charm, thank you all!!
On 21.12.2014 14:42, Jose Borges Ferreira wrote:
You allmost got it.
Transport_map is used to override the default transport and the ones you
don't want to override just left out.
Just take the * and that should work as you intended.
José Borges Ferreira
On
On Sun, Dec 21, 2014 at 08:57:52AM -0500, Wietse Venema wrote:
> Istvan Prosinger:
> > Hello,
> >
> > Is it possibble to make Postfix relay to some specific domain using a
> > specific relay, and relay all the other domains by default rules (put
> > the mail to an inbox if local or relay outboun
Istvan Prosinger:
> Hello,
>
> Is it possibble to make Postfix relay to some specific domain using a
> specific relay, and relay all the other domains by default rules (put
> the mail to an inbox if local or relay outbound by the given
> restrictions etc)?
>
> I guess it'd involve a transport_
You allmost got it.
Transport_map is used to override the default transport and the ones you
don't want to override just left out.
Just take the * and that should work as you intended.
José Borges Ferreira
On Dec 21, 2014 12:55 PM, "Istvan Prosinger" wrote:
> Hello,
>
> Is it possibble to make P
Am 21.12.2014 um 13:53 schrieb Istvan Prosinger:
Is it possibble to make Postfix relay to some specific domain using a
specific relay, and relay all the other domains by default rules (put
the mail to an inbox if local or relay outbound by the given
restrictions etc)?
I guess it'd involve a tra
Hello,
Is it possibble to make Postfix relay to some specific domain using a
specific relay, and relay all the other domains by default rules (put
the mail to an inbox if local or relay outbound by the given
restrictions etc)?
I guess it'd involve a transport_maps pointer in the main.cf to a
Hi,
>> I have a postfix-2.9.5 install on fc16 which manages mail for a few
>> domains. The server just relays mail for a few domains and doesn't
>> deliver any mail locally.
>>
>> The question I have is regarding precedence. Is the
>> smtpd_recipient_restrictions consulted before transport_maps?
>
Am 09.03.2013 23:41, schrieb Alex:
> Hi,
>
> I have a postfix-2.9.5 install on fc16 which manages mail for a few
> domains. The server just relays mail for a few domains and doesn't
> deliver any mail locally.
>
> The question I have is regarding precedence. Is the
> smtpd_recipient_restriction
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
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?
>>
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 tab
Hi people,
Simple question:
I s safe use mysql to get the transport maps information? if the connection
with database drops ? is there cache?
BR,
Junix
looking for something similar too.
For example in my case I use the transport maps via TCP lookup to
retrieve in round robin fashion (given by a script listening the GET
) between available outgoing "transport" lines.
I'd like to expand the simple round robin to something which wou
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.
> -
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 - is it somehow possible to
have all the information provided similar to the check_policy_service ?
E.g. The transport destination should be querie
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
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:
transport_maps = type:A, type:B
Would postfix
- Original Message -
From: "/dev/rob0"
To:
Sent: Sunday, June 17, 2012 1:46 PM
Subject: Re: individual user transport maps
On Sun, Jun 17, 2012 at 01:29:53PM +0200, Jeroen Geilman wrote:
On 06/17/2012 12:21 PM, Andreas.B wrote:
>I was messing with transport maps a wh
On Sun, Jun 17, 2012 at 01:29:53PM +0200, Jeroen Geilman wrote:
> On 06/17/2012 12:21 PM, Andreas.B wrote:
> >I was messing with transport maps a while ago, what i remeber
> >it was only possible to put domains in transport maps.
Your memory might be incorrect. Per-addresss tran
On 06/17/2012 12:21 PM, Andreas.B wrote:
Hi Wietse
I was messing with transport maps a while ago, what i remeber it was
only possible to put domains in transport maps. This is however good
to know, would you please post an example how this would look like
thank you.
Andreas.B
http
Hi Wietse
I was messing with transport maps a while ago, what i remeber it was only
possible to put domains in transport maps. This is however good to know,
would you please post an example how this would look like
thank you.
Andreas.B
* Jacopo Cappelli :
> Hi, can i have multiple entries on transport maps of same domain?
> Example:
>
> /etc/postfix/transport
> example.com smtp:[1.1.1.1]
> example.com smtp:[2.2.2.2]
> example.com smtp:[3.3.3.3]
No.
> If one serve
Hi, can i have multiple entries on transport maps of same domain?
Example:
/etc/postfix/transport
example.com smtp:[1.1.1.1]
example.com smtp:[2.2.2.2]
example.com smtp:[3.3.3.3]
If one server go down i want to send with other mail server.
It's pos
- Original Message
> From: Ralf Hildebrandt
> To: postfix-users@postfix.org
> Sent: Mon, April 4, 2011 2:12:02 PM
> Subject: Re: Multiple transport maps in master.cf?
>
> * email builder :
> > Hello,
> >
> > I've found that in main.cf,
email builder:
> > > > > Can I override default_transport?
>
> > > >
> > > > As documented:
> > > >
> > > > http://www.postfix.org/postconf.5.html#default_transport
> > >
> > > Right, but from what I can tell (testing it), it's like transport_maps,
> > > in that I can't change it willy-ni
> > > > Can I override default_transport?
> > >
> > > As documented:
> > >
> > > http://www.postfix.org/postconf.5.html#default_transport
> >
> > Right, but from what I can tell (testing it), it's like transport_maps,
> > in that I can't change it willy-nilly in my smtpd process with a
>
On 04/05/2011 12:09 AM, Victor Duchovni wrote:
On Mon, Apr 04, 2011 at 11:51:40PM +0200, Jeroen Geilman wrote:
The only Postfix service that consults the transport table is
trivial-rewrite(8), which in turn is consulted by smtpd(8), cleanup(8),
qmgr(8), ... with the main routing decision ma
On Mon, Apr 04, 2011 at 11:51:40PM +0200, Jeroen Geilman wrote:
>> The only Postfix service that consults the transport table is
>> trivial-rewrite(8), which in turn is consulted by smtpd(8), cleanup(8),
>> qmgr(8), ... with the main routing decision made in qmgr(8).
>>
>> Postfix parameter settin
email builder:
> > > Can I override default_transport?
> >
> > As documented:
> >
> > http://www.postfix.org/postconf.5.html#default_transport
>
> Right, but from what I can tell (testing it), it's like transport_maps,
> in that I can't change it willy-nilly in my smtpd process with a
> -o lin
On 04/04/2011 11:55 PM, email builder wrote:
- Original Message
From: Wietse Venema
To: Postfix users
Sent: Mon, April 4, 2011 2:34:00 PM
Subject: Re: Multiple transport maps in master.cf?
email builder:
I've found that in main.cf, this works
- Original Message
> From: Wietse Venema
> To: Postfix users
> Sent: Mon, April 4, 2011 2:34:00 PM
> Subject: Re: Multiple transport maps in master.cf?
>
> email builder:
> > > > > I've found that in main.cf, this works fine:
> > >
On 04/04/2011 11:26 PM, Victor Duchovni wrote:
On Mon, Apr 04, 2011 at 02:02:17PM -0700, email builder wrote:
Hello,
I've found that in main.cf, this works fine:
transport_maps = hash:/etc/postfix/transport1 hash:/etc/postfix/transport2
But not in master.cf (under a smtpd process definit
email builder:
> > > > I've found that in main.cf, this works fine:
> >
> > > >
> > > > transport_maps = hash:/etc/postfix/transport1
> >hash:/etc/postfix/transport2
> > > >
> > > > But not in master.cf (under a smtpd process definition):
> > > >
> > > > -o transport_maps=hash:/etc/p
- Original Message
> From: email builder
> To: postfix-users@postfix.org
> Sent: Mon, April 4, 2011 2:18:01 PM
> Subject: Re: Multiple transport maps in master.cf?
>
> > > I've found that in main.cf, this works fine:
>
> > >
> > &
On Mon, Apr 04, 2011 at 02:02:17PM -0700, email builder wrote:
> Hello,
>
> I've found that in main.cf, this works fine:
>
> transport_maps = hash:/etc/postfix/transport1 hash:/etc/postfix/transport2
>
> But not in master.cf (under a smtpd process definition):
>
> -o transport_maps=hash:/etc
> > I've found that in main.cf, this works fine:
> >
> > transport_maps = hash:/etc/postfix/transport1 hash:/etc/postfix/transport2
> >
> > But not in master.cf (under a smtpd process definition):
> >
> > -o transport_maps=hash:/etc/postfix/transport1
>hash:/etc/postfix/transport2
>
>
1 - 100 of 166 matches
Mail list logo
