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
mail
to the MX records of smtp.example.com.
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.
Please help me set this one up.
~LA
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 if there is anything like this: transport_maps.cf *.*
10.25.x
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
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 -
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
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
Good Afternoon and excuse my poor english.
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)
from dom
When I send a mail to @example.com, postfix must send the mail
> to the MX records of smtp.example.com.
>
> I tried using transport maps, "example.com :[smtp1.example.com]" and
> " example.com smtp:[smtp1.example.com], but of them didn't use
> smtp.exa
* 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
--
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.
Documentati
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 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: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'
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,
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
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:
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
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,
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, 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 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
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
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 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
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
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
* 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
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
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
>
>
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:
> 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/
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:
> 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
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:
> 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 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
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:
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.
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
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)
I'm using Postfix 2.7.0.
I use LDAP do manage/list domains that I relay for.
My problem is, when mail arrives to a domain I make relay for, and
this account has an alias to another domain I also relay for, the
transport to the second e-mail is not found.
Suppose I relay for both dom
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
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
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
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
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
>
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:
> 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
??? (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:
> 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
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
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
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
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 -d' o
er directly and also to continue processing
mail for lists.example.org locally and passing it to mailman. I think I can
do this with transport maps? Will transit maps override the relayhost
settings when appropriate? I have the O'Reilly Postfix book, but wasn't
able to determine thi
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
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, 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:
>
>
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/postfix/transport1 hash:/etc/postfix/transport2
Postfix complains:
fatal: unex
* 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
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
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
- 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 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
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?
>>
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
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
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
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.
>
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
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
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_
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
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 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
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
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
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
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'
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
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 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."
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&#
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:
[ 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
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:
> > 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
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.
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
a fresh postconf -n for a more detailed & updated
picture.
Regards,
-Eric
Victor Duchovni wrote:
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.
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 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 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
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
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
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
...
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 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
1 - 100 of 166 matches
Mail list logo
