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
--
^고맙습니다 _地平天成_ 감사합니다_^))//
__
ether what I think I'm hearing is that transport_map
> > overrides everything
>
> The transport(5) table has the highest priority for the components of
> the (transport, nexthop) pair that it specifies. All the other sources
> are fallback sources when either or both of the
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
rt(5) table has the highest priority for the components of
the (transport, nexthop) pair that it specifies. All the other sources
are fallback sources when either or both of the transport or nexthop are
not specified in transport(5).
> So does sender_dependent_relayhost_maps contain
drew 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 compo
estination for remote delivery to domains
listed with $relay_domains. In order of decreasing precedence, the nexthop
destination is taken from $relay_transport,
$sender_dependent_relayhost_maps, $relayhost, or from the recipient domain.
This information can be overruled with the transport(5) table." If a us
o be composite).
> But "sender_dependent_relayhost_maps" indicates that it can be overruled by
> "sender_dependent_default_transport_maps"
Bottom line "relayhost" and its sender-dependent versions provide a
non-default nexthop to override the recipient domain, but may in t
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 &qu
ble to get sender_dependent_relayhost_maps to actually change the relayhost
for mails from a particular domain.
1. I created the following /etc/postfix/relayhost_maps file:
@arrl.net [smtp.pobox.com]:587
2. I added the following to main.cf:
sender_dependent_relayhost_maps = hash:/e
D. R. Evans:
> I must be doing something particularly obviously stupid, because doing my best
> to follow the advice from Wietse in the thread "different treatment for
> different From: domains", I have tried everything I can think of, and am
> unable to get sender_depen
I must be doing something particularly obviously stupid, because doing my best
to follow the advice from Wietse in the thread "different treatment for
different From: domains", I have tried everything I can think of, and am
unable to get sender_dependent_relayhost_maps to actually
ng issues with getting sender_dependent_relayhost_maps to work
> (Rocky Linux 8, postfix v3.5.8). No matter what I try, it seems that
> the sender_dependent_relayhost_maps is being ignored.
>
> Here's my main.cf:
>
> alias_database = hash:/etc/aliases
> alias_maps = h
Hi there,
I'm having issues with getting sender_dependent_relayhost_maps to work
(Rocky Linux 8, postfix v3.5.8). No matter what I try, it seems that
the sender_dependent_relayhost_maps is being ignored.
Here's my main.cf:
alias_database = hash:/etc/aliases
alias_maps = hash:/e
>> > On 21.04.22 17:51, Matus UHLAR - fantomas wrote:
>> > >I'm trying to implement SRS using postsrsd. Since it always rewrites
>> > >non-local sender (even for incoming mail) I'm trying to restrict it
>> > >only for outgoing mail.
>Wietse Venema:
>> SRS sender rewriting is in scope for email th
Matus UHLAR - fantomas:
> >> > On 21.04.22 17:51, Matus UHLAR - fantomas wrote:
> >> > >I'm trying to implement SRS using postsrsd. Since it always rewrites
> >> > >non-local sender (even for incoming mail) I'm trying to restrict it
> >> > >only for outgoing mail.
>
> >Wietse Venema:
> >> SRS send
> On 21.04.22 17:51, Matus UHLAR - fantomas wrote:
> >I'm trying to implement SRS using postsrsd. Since it always rewrites
> >non-local sender (even for incoming mail) I'm trying to restrict it
> >only for outgoing mail.
Wietse Venema:
SRS sender rewriting is in scope for email that is forward
Wietse Venema:
> Matus UHLAR - fantomas:
> > bumping if anyone has a better idea.
> >
> > On 21.04.22 17:51, Matus UHLAR - fantomas wrote:
> > >I'm trying to implement SRS using postsrsd. Since it always rewrites
> > >non-local sender (even for incoming mail) I'm trying to restrict it
> > >only
Matus UHLAR - fantomas:
> bumping if anyone has a better idea.
>
> On 21.04.22 17:51, Matus UHLAR - fantomas wrote:
> >I'm trying to implement SRS using postsrsd. Since it always rewrites
> >non-local sender (even for incoming mail) I'm trying to restrict it
> >only for outgoing mail.
SRS sende
MTP server (alternative port) that
rewrites sender using canonical_maps, but:
I would like only to send mail from non-local senders using
sender_dependent_relayhost_maps:
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relayhost
% cat /etc/postfix/sender_relayhost
fantomas.sk
On 2022-04-21 17:51, Matus UHLAR - fantomas wrote:
I'm trying to keep configuration and mail flow as simple as possible.
On 22.04.22 01:44, Benny Pedersen wrote:
so dont use SRS ?
SRS is crucial to implement some functionalities our customers require.
Especially since google started refusi
On 2022-04-21 17:51, Matus UHLAR - fantomas wrote:
I'm trying to keep configuration and mail flow as simple as possible.
so dont use SRS ?
would like only to send mail from non-local senders using
sender_dependent_relayhost_maps:
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relayhost
% cat /etc/postfix/sender_relayhost
fantomas.sk DUNNO
* smtp:[localhost]:10027
however, t
Emanuel Gonzalez:
> Hello,
>
> I have a mail server with one domain and two servers i use to send email
> transactional.
>
> My question is, it's possible configure the parameter
> sender_dependent_relayhost_maps with round robin?
Generally, Postfix does not support n
Hello,
I have a mail server with one domain and two servers i use to send email
transactional.
My question is, it's possible configure the parameter
sender_dependent_relayhost_maps with round robin?
sender_dependent_default_transport_maps =
hash:/etc/po
On 29 Jul 2019, at 0:56, Viktor Dukhovni wrote:
> On Sun, Jul 28, 2019 at 08:14:38PM +, Bjoern A. Zeeb wrote:
>
>> Now sometimes the same email comes back to MX-E via an *alias* (no From:
>> changes) on MX-3. MX-E will receive the looped back email from MX-3
>> and then decides by its transp
On Sun, Jul 28, 2019 at 08:14:38PM +, Bjoern A. Zeeb wrote:
> Now sometimes the same email comes back to MX-E via an *alias* (no From:
> changes) on MX-3. MX-E will receive the looped back email from MX-3
> and then decides by its transport rules that it should send it to MX-I.
>
> Here’s
emails.
So I thought adding sender_dependent_relayhost_maps on MX-E would do the
trick (I cannot do it for the entire domain/destination MX); and it
partly does, and leads to another problem.
On MX-E:
main.cf:
sender_dependent_relayhost_maps =
hash:$config_directory
> On Nov 22, 2018, at 4:32 AM, Stefan Bauer wrote:
>
> Found it. Was required to modify smtp_auth to
>
> customer1.de user1:password
> customer2.de user2:password.
Nope:
http://www.postfix.org/SASL_README.html#client_sasl_sender
Generally, with Postfix lookups by email address, the lookup k
m 20:47 Uhr schrieb Wietse Venema <
> wie...@porcupine.org>:
>
>> Stefan Bauer:
>> > Hi,
>> >
>> > i have:
>> > sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
>> > smtp_sasl_password_maps = hash:/etc/postfix/sm
ietse Venema <
wie...@porcupine.org>:
> Stefan Bauer:
> > Hi,
> >
> > i have:
> > sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
> > smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth
> >
> > more /etc/postfix/relayhost_maps
>
Thank you!
Am Montag, 5. November 2018 schrieb Wietse Venema :
> Stefan Bauer:
>> Hi,
>>
>> i have:
>> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
>> smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth
>>
>> more /etc/postfix/
Stefan Bauer:
> Hi,
>
> i have:
> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
> smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth
>
> more /etc/postfix/relayhost_maps
> @mydomain.de[smtp.1und1.de]:587
> @my2domain.de [smtp.1und1.de]
Hi,
i have:
sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth
more /etc/postfix/relayhost_maps
@mydomain.de[smtp.1und1.de]:587
@my2domain.de [smtp.1und1.de]:587
more /etc/postfix/smtp_auth
[smtp.1und1.de]:587
KSB:
> Hi,
> Is it possible to configure sender_dependent_relayhost_maps with
> failover hosts, probably with priorities?
Use smtp_fallback_relay for the safety net.
Wietse
Hi,
Is it possible to configure sender_dependent_relayhost_maps with
failover hosts, probably with priorities?
--
KSB
tory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES
sample_directory = /usr/share/doc/postfix-2.6.6/samples
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relay
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtp_sasl_password_maps = hash
Under 'Configuring Sender-Dependent SASL authentication', it says:
Likewise, the Postfix trivial-rewrite(8) daemon will search the
per-sender relayhost file, and use the default relayhost setting only
as a final resort.
Would it be clearer to say "per-sender sender_dependent_rela
Thanks alot Viktor! I will try to patch the 2.11 and try it out.
/Henning
--
View this message in context:
http://postfix.1071664.n5.nabble.com/sender-dependent-relayhost-maps-does-not-default-to-relayhost-tp75756p75795.html
Sent from the Postfix Users mailing list archive at Nabble.com.
On Wed, Mar 18, 2015 at 02:30:36AM -0700, ebberup wrote:
> I found the possibility in the Postfix configuration
> parameters:*sender_dependent_relayhost_maps (default: empty)
Oops, my mistake, sorry! The documentation indeed promises that
DUNNO behaves as you expect, and this is
I found the possibility in the Postfix configuration
parameters:*sender_dependent_relayhost_maps (default: empty)*A
sender-dependent override for the global relayhost parameter setting. The
tables are searched by the envelope sender address and @domain. /A lookup
result of DUNNO terminates the
On Wed, Mar 18, 2015 at 12:59:29AM -0700, ebberup wrote:
> I can't make sender_dependent_relayhost_maps default to relayhost when
> trivial-rewrite result is DUNNO.
That's because "DUNNO" is an access(5) keyword, and not a generic
"nothing here" result for al
Hi,
I can't make sender_dependent_relayhost_maps default to relayhost when
trivial-rewrite result is DUNNO.
extract from postconf:
mail_version = 2.11.1
mydestination = $myhostname, localhost.$mydomain, localhost
sender_dependent_relayhost_maps =
proxy:pgsql:${config_dire
On 20/01/2015 23:03, Noel Jones wrote:
On 1/20/2015 2:08 PM, Chris Robinson wrote:
On 20/01/2015 19:48, Wietse Venema wrote:
To answer the question:
man 5 postconf
sender_dependent_relayhost_maps (default: empty)
...
This information is overruled with relay_transport
On 1/20/2015 2:08 PM, Chris Robinson wrote:
>
> On 20/01/2015 19:48, Wietse Venema wrote:
>> To answer the question:
>>
>> man 5 postconf
>> sender_dependent_relayhost_maps (default: empty)
>> ...
>> This inf
On 20/01/2015 19:48, Wietse Venema wrote:
To answer the question:
man 5 postconf
sender_dependent_relayhost_maps (default: empty)
...
This information is overruled with relay_transport,
sender_dependent_default_transport_maps, default_transport and
with the transport(5
To answer the question:
man 5 postconf
sender_dependent_relayhost_maps (default: empty)
...
This information is overruled with relay_transport,
sender_dependent_default_transport_maps, default_transport and
with the transport(5) table.
So that is no good. But there is a solution
I use Amazon SES service as a relay. I control which sasl clients send through
amazon with:
main.cf:
sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relay_host
A typical entry is:
@example.com email-smtp.eu-west-1.amazonaws.com:25
master.cf:
smtp inet n
Using the parameter "sender_dependent_default_transport_maps" leads to the
same result as using the paramter "sender_dependent_relayhost_maps". I
think this is the case cause the recipient domain is also part of the
internal domains. Therefore the relay entry defined in the
Sebastian Fehrenbacher:
> sender_dependent_relayhost_maps work great when the rcpt to addresses
> domain is not part of the relay_domains. However when both domains - mail
> from and rcpt to - are part of the relay_domains the parameter
> sender_dependent_relayhost_maps is not takin
sender_dependent_relayhost_maps work great when the rcpt to addresses
domain is not part of the relay_domains. However when both domains - mail
from and rcpt to - are part of the relay_domains the parameter
sender_dependent_relayhost_maps is not taking effect. In this case the
relayhost parameter
>
> Perhaps you're looking for this:
>
> http://www.postfix.org/postconf.5.html#smtp_sender_dependent_authentication
>
> http://www.postfix.org/postconf.5.html#smtp_sasl_password_maps
>
Hey nice, so I can actually put senders in sasl_mmaps instead of just
relays. That is indeed what I need. Th
On 8/13/2014 6:44 AM, Erik Logtenberg wrote:
> Hi, any chance someone could comment on this?
>
> Thanks!
>
>
> Original Message
> Subject: Combining sender_dependent_relayhost_maps and
> smtp_sasl_password_maps
> Date: Fri, 08 Aug 2014 11:11:20 +0
Hi, any chance someone could comment on this?
Thanks!
Original Message
Subject: Combining sender_dependent_relayhost_maps and
smtp_sasl_password_maps
Date: Fri, 08 Aug 2014 11:11:20 +0200
From: Erik Logtenberg
To: postfix-users@postfix.org
Hi,
I am trying to use the
Hi,
I am trying to use the functionality of sender_dependent_relayhost_maps
and smtp_sasl_password_maps, but I run into an issue.
With sender_dependent_relayhost_maps I can configure postfix to use the
right relayhosts for different senders. I use this because I have many
email accounts, but I
documentation which address needs to be in the
relay maps file, the local address vs. the translated
address. Can some please clarify? Thanks.
what additional mapping?
we are using "sender_dependent_relayhost_maps" to allow specific
senders which are not hosted on our server and rely t
;>>> However, I am also using generic mapping and again it is not
>>>> explained in the documentation which address needs to be in the
>>>> relay maps file, the local address vs. the translated
>>>> address. Can some please clarify? Thanks.
>>> wha
. the translated
address. Can some please clarify? Thanks.
what additional mapping?
we are using "sender_dependent_relayhost_maps" to allow specific
senders which are not hosted on our server and rely them to
the customers MTA with the users login/password without
rewrite anything
Than
relay maps file, the local address vs. the translated
>> address. Can some please clarify? Thanks.
> what additional mapping?
>
> we are using "sender_dependent_relayhost_maps" to allow specific
> senders which are not hosted on our server and rely them to
> the cu
Reindl Harald:
> Am 19.04.2013 14:25, schrieb awingnut:
> > I have a series of user names that need to be relayed through a server
> > other then the default. It is not clear from the documentation if wild
> > cards are allowed but it appears they are not
>
> no and wildchars in case of mail are g
e clarify? Thanks.
what additional mapping?
we are using "sender_dependent_relayhost_maps" to allow specific
senders which are not hosted on our server and rely them to
the customers MTA with the users login/password without
rewrite anything
signature.asc
Description: OpenPGP digital signature
I have a series of user names that need to be relayed through a server
other then the default. It is not clear from the documentation if wild
cards are allowed but it appears they are not. If that is true then I
need to list each one individually. However, I am also using generic
mapping and again
o large authorized
> mailings that tend to bury the barracuda. These exceptions should
> be delivered directly by the outgoing mail server,
> smtp.lightlink.com
>
> I have
>
> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost
>
Instead use:
Homer Wilson Smith:
> #relayhost =
>
> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost
>
> relayhost file says
>
> * [barracuda.lightlink.com]:25
> frien...@spammer.com :
I don't know what "*" or ":&q
directly
by the outgoing mail server, smtp.lightlink.com
I have
#relayhost =
sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost
relayhost file says
* [barracuda.lightlink.com]:25
frien...@spammer.com :
the first line alone doesn't work, the second
transport.5.html
> >> Now I have the following entry in /etc/postfix/main.cf:
> >>
> >> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
> >
> > Not surprisingly, when you set the relay host to a transport:nexthop
> > it does not wo
icated
>> transport as described here:
>> http://www.postfix.org/SASL_README.html#client_sasl_sender
>> http://www.postfix.org/transport.5.html
>> Now I have the following entry in /etc/postfix/main.cf:
>>
>> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_m
r
> http://www.postfix.org/transport.5.html
> Now I have the following entry in /etc/postfix/main.cf:
>
> sender_dependent_relayhost_maps = hash:/etc/postfix/relayhost_maps
Not surprisingly, when you set the relay host to a transport:nexthop
it does not wor
ng currently on port 25.
I tried to use sender dependent authentication with a dedicated
transport as described here:
http://www.postfix.org/SASL_README.html#client_sasl_sender
http://www.postfix.org/transport.5.html
Now I have the following entry in /etc/postfix/main.cf:
sender_dependent_relayh
On 2012-05-31 8:12 AM, Wietse Venema wrote:
I recall that transport_maps was introduced in 1998, and
per-recipient transport map support in 2002. All precedences of
relayhost etc. are documented in postconf(5).
Well, yes, but some of us have a hard time comprehending the myriad of
options ava
Charles Marcus:
> On 2012-05-31 7:29 AM, Wietse Venema wrote:
> > If you need a recipient-dependent override for outbound delivery,
> > consider using a transport map, and use relayhost for the remainder.
>
> I guess you didn't bother reading my entire email (no worries, I tend to
> ramble)... ;
On 2012-05-31 7:29 AM, Wietse Venema wrote:
If you need a recipient-dependent override for outbound delivery,
consider using a transport map, and use relayhost for the remainder.
I guess you didn't bother reading my entire email (no worries, I tend to
ramble)... ;)
At the end, I asked about
Charles Marcus:
> On 2012-05-31 6:00 AM, Wietse Venema wrote:
> > If this alias is a mailing list, you set the envelope sender
> > accordingly (like any mailing list).
>
> No, these are simply aliases I have set up in my virtual alias maps.
> There are two different uses for these aliases...
>
On 2012-05-31 6:00 AM, Wietse Venema wrote:
If this alias is a mailing list, you set the envelope sender
accordingly (like any mailing list).
No, these are simply aliases I have set up in my virtual alias maps.
There are two different uses for these aliases...
1. We have (currently) 3 accou
Charles Marcus:
> Hello,
>
> I'm still looking for a reliable workaround to my alias >
> external_address problem using postini for outbound relay...
>
> I just realized that if there were a simple way to do the same as
> sender_dependent_relayhost
Hello,
I'm still looking for a reliable workaround to my alias >
external_address problem using postini for outbound relay...
I just realized that if there were a simple way to do the same as
sender_dependent_relayhost_maps, but for recipients (ie,
recipient_dependent_relayhost_map
Hi, Neil,
My confusion lies in the fact that the email client campaign software is
actually initiating a connection to the virtual domain, and sending the
mail to it -- all on the same server, mind you -- then IT sends it out
through the interface with it's virtualized IP address.
I don't se
On 5/23/2011 10:19 AM, Jeffs wrote:
On 5/23/2011 11:06 AM, Noel Jones wrote:
The Received: header is added by the receiving system, not
by your server, and always shows the IP of the connection.
If you want each client to have their own identity, each
client will need its own IP. You can't virt
the same server.
Postfix uses sender_dependent_relayhost_maps to channel
xyz.com messages to interface eth0:1 and def.com messages
to the the eth0:2 interface.
Those virtual interfaces are mapped to IP addresses that
are registered addresses for xyc.com and def.com respectively.
Here is the
sender_dependent_relayhost_maps to channel
xyz.com messages to interface eth0:1 and def.com messages
to the the eth0:2 interface.
Those virtual interfaces are mapped to IP addresses that
are registered addresses for xyc.com and def.com respectively.
Here is the question:
Will the received from headers in
client from def.com logins to
Many_Companies.com, accesses their email campaign software running on
Many_Companies.com and sends out newsletters.
They both access the same software just have user accounts that are
different on the same server.
Postfix uses sender_dependent_relayhost_maps to
Many_Companies.com,
accesses their email campaign software running on Many_Companies.com
and sends out newsletters.
They both access the same software just have user accounts that are
different on the same server.
Postfix uses sender_dependent_relayhost_maps to channel xyz.com
messages to interface eth0:1
software running on Many_Companies.com and
sends out newsletters.
They both access the same software just have user accounts that are
different on the same server.
Postfix uses sender_dependent_relayhost_maps to channel xyz.com messages
to interface eth0:1 and def.com messages to the the eth0:2
nderstand correctly, when I use
>> sender_dependent_relayhost_maps transport and relayhost need to be
>> empty
>
> GB GB put forth on 2/8/2011 4:10 PM:
>> here is the outputthe current version of postfix is 2.3.19
>>
>> mail_release_date = 20040915
>> mail
GB GB put forth on 2/8/2011 4:52 PM:
> so if I understand correctly, when I use
> sender_dependent_relayhost_maps transport and relayhost need to be
> empty
GB GB put forth on 2/8/2011 4:10 PM:
> here is the outputthe current version of postfix is 2.3.19
>
> mail_relea
$relay_recipient_maps $relay_domains
$canonical_maps $sender_canonical_maps $recipient_canonical_maps
$relocated_maps $transport_maps $mynetworks
relayhost = myrelay.$mydomain
sender_dependent_relayhost_maps = regexp:/etc/postfix-hd/sender_relayhost
transport_maps = dbm:/etc/postfix-hd/transport
so if I
GB GB:
> postconf -n -c /etc/postfix-hd will render the output I sent in the
> earlier mail
I don't have time for people with hundreds of parameters
in their main.cf file.
You can find out for yourself if the requirements for
sender_dependent_relayhost_maps are met: no transpo
On 2/8/2011 5:39 PM, GB GB wrote:
postconf -n -c /etc/postfix-hd will render the output I sent in the
earlier mail
regards,
On Tue, Feb 8, 2011 at 5:20 PM, Wietse Venema wrote:
GB GB:
here is the outputthe current version of postfix is 2.3.19
I asked for "postconf -n" output.
I di
postconf -n -c /etc/postfix-hd will render the output I sent in the
earlier mail
regards,
On Tue, Feb 8, 2011 at 5:20 PM, Wietse Venema wrote:
> GB GB:
>> here is the outputthe current version of postfix is 2.3.19
>>
>
> I asked for "postconf -n" output.
>
> I did not ask for hundreds of
GB GB:
> here is the outputthe current version of postfix is 2.3.19
>
I asked for "postconf -n" output.
I did not ask for hundreds of parameter settings.
Wietse
relay_recipient_maps =
relay_transport = relay
relayhost = smtp11.$mydomain
relocated_maps =
require_home_directory = no
resolve_dequoted_address = yes
resolve_null_domain = no
rewrite_service_name = rewrite
sample_directory = /etc/postfix
sender_bcc_maps =
sender_canonical_maps =
sender_dependent_relayhost_maps
gbcy...@gmail.com:
> My apologies, the sender_relay contains
> /r...@ltest01.domain.com/ [1.2.3.4]
>
> Regxp is what I will use for this map
Please show COMPLETE postconf -n output. As documented at
http://www.postfix.org/postconf.5.html#sender_dependent_relayho
My apologies, the sender_relay contains
/r...@ltest01.domain.com/ [1.2.3.4]
Regxp is what I will use for this map
Regards,
On 2011-02-08, at 3:48 PM, Jeroen Geilman wrote:
> On 02/08/2011 08:47 PM, GB GB wrote:
>> Hello,
>>
>> I noticed after configuring sender_dep
On 02/08/2011 08:47 PM, GB GB wrote:
Hello,
I noticed after configuring sender_dependent_relayhost_maps and
expecting it to forward mail to my listed destination does not work as
expected.
I need sender_dependent_relayhost_maps to forward mail depending what
the the source is.
Our team has
Hello,
I noticed after configuring sender_dependent_relayhost_maps and
expecting it to forward mail to my listed destination does not work as
expected.
I need sender_dependent_relayhost_maps to forward mail depending what
the the source is.
Our team has split into 2 so since we have 2 relays I
On Thu, Mar 25, 2010 at 7:45:14PM -0400, /dev/rob0 wrote:
> On Thu, Mar 25, 2010 at 12:48:33PM -0400, Damon Miller wrote:
> > Hello. I've configured Postfix to relay mail from a specific
> > address to a remote MTA through 'sender_dependent_relayhost_maps'
> >
On Thu, Mar 25, 2010 at 12:48:33PM -0400, Damon Miller wrote:
> Hello. I've configured Postfix to relay mail from a specific
> address to a remote MTA through 'sender_dependent_relayhost_maps'
> and that works fine. I now want to BCC an address for messages
> sent b
Hello. I've configured Postfix to relay mail from a specific address to a
remote MTA through 'sender_dependent_relayhost_maps' and that works fine. I
now want to BCC an address for messages sent by this same user. The most
obvious option seemed 'recipient_bcc_maps',
Yes,
i solved problem using how result_attribute a single-valued attribute.
Thanks
Victor Duchovni wrote:
> On Thu, Dec 03, 2009 at 01:57:07AM +0100, Giovanni Mancuso wrote:
>
>
>> result_attribute = domains
>> result_format = [127.0.0.1]:2501
>> expansion_limit = 1
>>
>> But i have:
>> postfi
1 - 100 of 140 matches
Mail list logo
