Josh Cason a écrit :
postfix, relayhost, and dynamic ip range though it is static
So after fighting with rdns and sorbs issues. Well mostly sorb issues. I
decided to route through our isp server. I think this fixed sorbs for
complaints about it thinking it is a dynamic ip. I'll find out more
On Thu, Apr 29, 2010 at 5:34 PM, Brian Evans - Postfix List
grkni...@scent-team.com wrote:
This is because of your setting in main.cf:
smtp_sasl_password_maps = static:login:userpasswd
This will send the same user and password to every server that supports
authentication.
Suggest
Israel Garcia:
[ Charset UTF-8 unsupported, converting... ]
On Thu, Apr 29, 2010 at 5:34 PM, Brian Evans - Postfix List
grkni...@scent-team.com wrote:
This is because of your setting in main.cf:
smtp_sasl_password_maps = static:login:userpasswd
This will send the same user and
myhostname = server.domain
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost = [relayhost]:587
smtp_host_lookup = native,dns
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
Hi,
I'm sending all emails to a relayhost with a TLS connection , but I
want to send mail to specific domain using another hosts. I mean:
* -- [smtp.tls.host]:587 (TLS)
and
*...@domain1 smtp:[host1]
*...@domain2 smtp:[host2]
This is postconf -n output:
alias_database = hash:/etc/aliases
Israel Garcia:
Hi,
I'm sending all emails to a relayhost with a TLS connection , but I
want to send mail to specific domain using another hosts. I mean:
As documented, the transport_maps setting overrides the relayhost
setting, so you are on the right track:
relayhost = [smtp.tls.host
On Thu, Apr 29, 2010 at 2:22 PM, Wietse Venema wie...@porcupine.org wrote:
�...@domain1 smtp:[host1]
�...@domain2 smtp:[host2]
The syntax for transport maps is documented: man 5 transport. Please
take a minute to read the docs.
:-) working now..
but I'm getting this error when try to
Israel Garcia:
On Thu, Apr 29, 2010 at 2:22 PM, Wietse Venema wie...@porcupine.org wrote:
?...@domain1 smtp:[host1]
?...@domain2 smtp:[host2]
The syntax for transport maps is documented: man 5 transport. Please
take a minute to read the docs.
:-) working now..
but I'm getting
, but it should not authenticate with this server.
In my scenario, all email is sent to the relayhost using TLS without
problem. The problem comes when I send email to a non-authenticated
server (a server on transport_maps). It seems my main.cf is setup to
send mail ONLY using TLS. I need to be able to sent mail
with the
wrong username or password.
Yes, but it should not authenticate with this server.
In my scenario, all email is sent to the relayhost using TLS without
problem. The problem comes when I send email to a non-authenticated
server (a server on transport_maps). It seems my main.cf is setup
My relay sends as follows:
90% - relayhost
10% - other hosts in transport (these go directly out)
This works well.
my question:
When the primary relayhost is unavailable what would be
the best way to *send* the 90% out.. ?
(not about load balancing)
Thx
Charles
On 4/19/2010 9:34 AM, CT wrote:
My relay sends as follows:
90% - relayhost
10% - other hosts in transport (these go directly out)
This works well.
my question:
When the primary relayhost is unavailable what would be
the best way to *send* the 90% out.. ?
(not about load balancing)
If your
Hello,
Relevant config parameters:
parent_domain_matches_subdomains =
relay_domains = hash:some_relay_domains_map
relay_relayhost = [a.b.c.d]
some_relay_domains_map contain:
xxx.comx
yyy.comx
aaa.xxx.comx
bbb.yyy.comx
symptom:
messages for xxx.com and yyy.com are correctly
Emmanuel Fust?:
relay_relayhost = [a.b.c.d]
As always, use postconf -n output when reporting a problem. This
would have revealed immediately that relay_relayhost is a mistake.
Wietse
a supported syntax ?
I double check and you're right: the main domains are working by
accident (MX=relayhost gateway).
Yes I know that postconf -n did not report relay_relayhost =
[a.b.c.d] but I was fooled by my half working setup.
Could I achieve my goal with modifying the relay line
-parameter is no longer a supported syntax ?
This has never been supported for relayhost.
Wietse
I double check and you're right: the main domains are working by
accident (MX=relayhost gateway).
Yes I know that postconf -n did not report relay_relayhost =
[a.b.c.d] but I was fooled
On Thu, Apr 01, 2010 at 03:50:17PM +0200, Emmanuel Fust?? wrote:
Could I achieve my goal with modifying the relay line in the master.cf
like:
relay unix - - - - - smtp
-o smtp_fallback_relay=
-o relayhost= [a.b.c.d]
No.
Or should I
Hi,
Our smtp server has some issues when talking to some remote mx's. This
results in a timeout and the message not being delivered (this was
discussed on this mailinglist but there doesn't seem to be a real
solution available now). When we relay the message through another
server the remote mx
Martijn de Munnik:
Hi,
Our smtp server has some issues when talking to some remote mx's. This
results in a timeout and the message not being delivered (this was
discussed on this mailinglist but there doesn't seem to be a real
solution available now). When we relay the message through
On Wed, 24 Mar 2010 09:45:55 -0400 (EDT), Wietse Venema
wie...@porcupine.org wrote:
Martijn de Munnik:
Hi,
Our smtp server has some issues when talking to some remote mx's. This
results in a timeout and the message not being delivered (this was
discussed on this mailinglist but there
Am 24.03.2010 14:31, schrieb Martijn de Munnik:
Hi,
Our smtp server has some issues when talking to some remote mx's. This
results in a timeout and the message not being delivered (this was
discussed on this mailinglist but there doesn't seem to be a real
solution available now). When we
but use the relayhost to deliver to the ISP because this users
use laptops and need to download their mail directly from the ISP server.
These users does not have a virtual local account. I have tried transport
maps but it seems that is not the correct way to do it. Can anyone please
point me
, us...@domain.com and us...@domain.com that I do not want to
deliver local but use the relayhost to deliver to the ISP because this users
use laptops and need to download their mail directly from the ISP server.
These users does not have a virtual local account. I have tried transport
maps
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
us...@postfix.org] On Behalf Of Victor Duchovni
Sent: 24 March 2010 20:02
To: postfix-users@postfix.org
Subject: Re: Forward local mailbox to relayhost
On Wed, Mar 24, 2010 at 04:51:33PM +0200, Isak
I have a situation with hosting.com, trying to setup
a friends postfix config. Since I knew nothing about
them I asked him to find out what their smtp server
was. They said that we cannot use it and gave us a link
to setup postfix, however they show no relayhost (smtp)
server in the config!
My
no relayhost (smtp)
server in the config!
My question is, who can I use as an smtp relayhost
if the local host doesnt have one?
If your ISP won't let you use their SMTP server, you'll need to
configure your own or find someone who will let you use theirs. At
this point your best bet
they show no relayhost (smtp)
server in the config!
My question is, who can I use as an smtp relayhost
if the local host doesnt have one?
Typically in a hosting or colocation situation you send smtp directly to the
recipient domains' MX'en. You don't typically use an smtp relay in this
scenario
If you set mylocaldomain in mydestination or virtual_mailbox_domains of
your main.cf then Postfix should not relay the mail.
I want the mail to be sent.
If you want that
Postfix smtp client sends emails based on sender to different relay
servers then http://www.postfix.org/SASL_README.html
(as it
will come as u...@system.example.com).
Don't specify relayhost in main.cf.
However, if external users connect to send mail through this Postfix
server, they need to be relayed through a different host.
This requires Postfix version 2.6 or later.
Use sender_dependent_relayhost_maps
, or is DUNNO only supported as of
Postfix 2.6?
You pasted a link to the documentation but did not actually read it? It
is quite clear:
A lookup result of DUNNO terminates the search without overriding the
global relayhost parameter setting (Postfix 2.6 and later).
--
Sahil Tandon sa...@tandon.net
directly, without any relays (as it
will come as u...@system.example.com).
Don't specify relayhost in main.cf.
However, if external users connect to send mail through this Postfix
server, they need to be relayed through a different host.
This requires Postfix version 2.6 or later
If I add a relayhost to main.cf:
relayhost = relayhost.example.com
all main will be delivered through relayhost.example.com.
Now, I would like to deliver mail i.e. for @mylocaldomain directly, not
through relayhost - how should I do it?
I tried sender_dependent_relayhost_maps, but I'm
Am 19.12.2009 00:07, schrieb Dasza Seyda:
If I add a relayhost to main.cf:
relayhost = relayhost.example.com
all main will be delivered through relayhost.example.com.
Now, I would like to deliver mail i.e. for @mylocaldomain directly,
not through relayhost - how should I do it?
I tried
/main.cf
virtual_alias_domains = mydomain.com
virtual_alias_maps = hash:/etc/postfix/virtual
transport_maps = hash:/etc/postfix/transport
relayhost = [mail.authsmtp.com]:2525
smtp_connection_cache_destinations = mail.authsmtp.com
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps
:/etc/postfix/transport
relayhost = [mail.authsmtp.com]:2525
Try removing this relayhost definition; it is redundant since you are
already using a wildcard in your transport_maps to route mail to
authsmtp.com.
--
Sahil Tandon sa...@tandon.net
Hi,
I am looking for a solution where i would be able to configure one postfix
instance in such a way that it rotates multiple relayhosts and acts as a
host that relays emails to multiple hosts. For eg. we currently have the
option of entering just one relayhost = xx.xx.xx.xx. However i need
one relayhost = xx.xx.xx.xx. However i need a
solution where i shuld be able to map multiple relayhosts and make postfix
relay via those list of hosts.
P.S. The ports also might be different in some cases.
You can use iptables for that or make dns round robin entry and point
relayhost
Chatpar dchat...@gmail.com:
Hi,
I am looking for a solution where i would be able to configure one postfix
instance in such a way that it rotates multiple relayhosts and acts as a
host that relays emails to multiple hosts. For eg. we currently have the
option of entering just one relayhost
Quoting Dhiraj Chatpar dchat...@gmail.com:
can you please give me a tutorial to achieve this?
See the:
http://cormander.com/blog/2008/05/round-robin-balancing-with-iptables/
and http://www.zytrax.com/books/dns/ch9/rr.html
--
Eero
I believe there is an option within postfix too to achieve this?
Ogden Nash http://www.brainyquote.com/quotes/authors/o/ogden_nash.html -
The trouble with a kitten is that when it grows up, it's always a cat.
On Wed, Nov 18, 2009 at 18:50, Eero Volotinen eero.voloti...@iki.fi wrote:
Quoting
Quoting Dhiraj Chatpar dchat...@gmail.com:
I believe there is an option within postfix too to achieve this?
As far as I known, postfix only supports one relayhost plus backup host.
--
Eero
2009/11/19 Dhiraj Chatpar dchat...@gmail.com:
I believe there is an option within postfix too to achieve this?
I'm fairly sure there's not. If you don't like the idea of using
iptables, the alternative would be a customised DNS entry for your
relayhost.
Create a virtual relayhost A-record (eg
:
2009/11/19 Dhiraj Chatpar dchat...@gmail.com:
I believe there is an option within postfix too to achieve this?
I'm fairly sure there's not. If you don't like the idea of using
iptables, the alternative would be a customised DNS entry for your
relayhost.
Create a virtual relayhost A-record (eg
currently have the
option of entering just one relayhost = xx.xx.xx.xx. However i need a
solution where i shuld be able to map multiple relayhosts and make
postfix
relay via those list of hosts.
What problem are you trying to solve? State the problem, not
the solution of multiple
Dhiraj Chatpar:
We have 5 different servers.. all of them are mailing servers for our main
company domain, I wish to Balance the mails across these 5 servers.
Isn't that what the DNS was invented for? You specify the domain
and its servers, and then all standards-compliant mail systems
will
Yes the DNS is a good idea..
However what will i achieve if i implement the following?
# Changes in /etc/postfix2/main.cf
sender_based_routing = yes
relay unix - - n - - smtp
-o fallback_relay=
smtp_act1 unix - - n
Dhiraj Chatpar:
Yes the DNS is a good idea..
However what will i achieve if i implement the following?
The solution is to have multiple MX records in the DNS.
All standards-compliant MTAs will spread the load WITHOUT
ANY SENDER SIDE CONFIGURATION.
Wietse
Wietse Venema put forth on 11/18/2009 9:25 AM:
Dhiraj Chatpar:
Yes the DNS is a good idea..
However what will i achieve if i implement the following?
The solution is to have multiple MX records in the DNS.
All standards-compliant MTAs will spread the load WITHOUT
ANY SENDER SIDE
On 11/18/2009 11:47 AM, Dhiraj Chatpar wrote:
Well sir its our friend yahoo which is going to get me kicked off my job
as an administrator. I had an issue where a email sent to a yahoo email
address from My CEO didnt end up delivering. Ever since i have been
wondering for solutions.
You're
if the relay host has got a username and password how can i specify these in
the main.cf
a google on this showed me the following:
relayhost = smtp.example.com:25
smtp_sasl_auth_enable=yes
smtp_sasl_password_maps=hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options=
/etc/postfix
On Tue, 15 Sep 2009 16:06:54 +0200
K bharathan kbhara...@gmail.com wrote:
if the relay host has got a username and password how can i specify
these in the main.cf
a google on this showed me the following:
relayhost = smtp.example.com:25
smtp_sasl_auth_enable=yes
K bharathan put forth on 9/15/2009 9:06 AM:
if the relay host has got a username and password how can i specify
these in the main.cf http://main.cf
a google on this showed me the following:
relayhost = smtp.example.com:25 http://smtp.example.com:25
smtp_sasl_auth_enable=yes
On 2009-09-15 K bharathan wrote:
if the relay host has got a username and password how can i specify
these in the main.cf
a google on this showed me the following:
relayhost = smtp.example.com:25
smtp_sasl_auth_enable=yes
smtp_sasl_password_maps=hash:/etc/postfix/sasl_passwd
Hello,
In our office we have a Postfix server which takes care of delivering email
inside and outside the office. For Internet mail it relays mail through the
ISP SMTP server. For this the relayhost parameter has been set to
relayhost=smtp.isp.tld.
We have a redundant Internet connection
svoop a écrit :
Hi
My mailserver (mail.bitcetera.com) is behind a router that gets a dynamic IP
(87.221.120.44) from the ISP. In order to prevent outgoing mail from being
considered spam due to the dynamic IP, I've configured the ISP's mailserver as
relayhost.
Unfortunately, Yahoo still
Hi
My mailserver (mail.bitcetera.com) is behind a router that gets a dynamic IP
(87.221.120.44) from the ISP. In order to prevent outgoing mail from being
considered spam due to the dynamic IP, I've configured the ISP's mailserver as
relayhost.
Unfortunately, Yahoo still throws my mails
http://www.postfix.org/ADDRESS_VERIFICATION_README.html#probe_routing
that did it, thanks
Len
__
IMGate OpenSource Mail Firewall www.IMGate.net
host (setting up
relayhost=smart.host.tld).
How could I do? Is it possible to change the relayhost postfix
parameter on the fly? Or what?
Why not use transport_maps?
--
Ralf Hildebrandt (ralf.hildebra...@charite.de) snick...@charite.de
Postfix - Einrichtung, Betrieb und Wartung
generated by my
mail application should be sent trhough a smart host (setting up
relayhost=smart.host.tld).
How could I do? Is it possible to change the relayhost postfix
parameter on the fly? Or what?
Why not use transport_maps?
Ugh, discard my answer :)
--
Ralf Hildebrandt
of destination
domain
an
forward it to the correct destination.
Now I have the problem, that indeed I need that some messages have
to
be
forwarded directly to the destination, while the ones generated by
my
mail application should be sent trhough a smart host (setting up
relayhost
domain an
forward it to the correct destination.
Now I have the problem, that indeed I need that some messages have to be
forwarded directly to the destination, while the ones generated by my
mail application should be sent trhough a smart host (setting up
relayhost=smart.host.tld).
How could I do
for MX of destination domain an
forward it to the correct destination.
Now I have the problem, that indeed I need that some messages have to be
forwarded directly to the destination, while the ones generated by my
mail application should be sent trhough a smart host (setting up
relayhost
On Sat, January 31, 2009 3:01 pm, Wietse Venema wrote:
Jack Knowlton:
Hi all.
I have an postfix installation configured to use my ISP's server as
relayhost.
I don't want to put too much load on it (and get blacklisted) so I'd
like
to limit the number of messages sent per minute.
I found
Jack Knowlton:
On Sat, January 31, 2009 3:01 pm, Wietse Venema wrote:
Jack Knowlton:
Hi all.
I have an postfix installation configured to use my ISP's server as
relayhost.
I don't want to put too much load on it (and get blacklisted) so I'd
like
to limit the number of messages sent
Hi all.
I have an postfix installation configured to use my ISP's server as
relayhost.
I don't want to put too much load on it (and get blacklisted) so I'd like
to limit the number of messages sent per minute.
I found previous posts on how to do that per destination domain - but how
about
Jack Knowlton:
Hi all.
I have an postfix installation configured to use my ISP's server as
relayhost.
I don't want to put too much load on it (and get blacklisted) so I'd like
to limit the number of messages sent per minute.
I found previous posts on how to do that per destination domain
, because postfix behavior is documented.
When the relayhost is a hostname enclosed by [ ] brackets, postfix
asks for an A record and does not ask for an MX record.
If relayhost is an IP address enclosed by brackets, postfix uses that IP
with no additional lookups.
If realyhost
likely nobody cares, because postfix behavior is documented.
When the relayhost is a hostname enclosed by [ ] brackets, postfix
asks for an A record and does not ask for an MX record.
If relayhost is an IP address enclosed by brackets, postfix uses that IP
with no additional lookups
Hello,
i read the documentation about the usage of [ and ] in relayhost
entries ...
I still not quite sure what happens or not happens when using an IP with
or without such signs...
relayhost = 1.2.3.4
may use MX records from DNS?
What if there is no nameserver configured? Will there be any
Thomas Ackermann wrote:
So, does anybody know what technically is the difference between the
use with and without the signs?
I mean, what network things may happen or not happen?
Nobody knows the technical differences?
:-(
behavior is
documented.
When the relayhost is a hostname enclosed by [ ] brackets,
postfix asks for an A record and does not ask for an MX record.
If relayhost is an IP address enclosed by brackets, postfix
uses that IP with no additional lookups.
If realyhost is a hostname with no brackets
documentation?
http://www.postfix.org/postconf.5.html#relayhost
Duane Hill wrote:
Care to take a look at the Postfix documentation?
http://www.postfix.org/postconf.5.html#relayhost
As i wrote, i read the documentation i found - it was exactly this small
entry about relayhost!
The answer from Noel Jones contains quite some more and deeper
information
Noel Jones wrote:
... more likely nobody cares, because postfix behavior is documented.
When the relayhost is a hostname enclosed by [ ] brackets, postfix
asks for an A record and does not ask for an MX record.
If relayhost is an IP address enclosed by brackets, postfix uses that
IP
Thomas:
Duane Hill wrote:
Care to take a look at the Postfix documentation?
http://www.postfix.org/postconf.5.html#relayhost
As i wrote, i read the documentation i found - it was exactly this small
entry about relayhost!
The answer from Noel Jones contains quite some more
Hello,
normally, you can say relayhost = domain and postfix searches the MX
record for that domain in DNS to get the list of relayhosts.
For domains where no MX record is configured into the DNS, i would need
to use more than one relayhost ...
Is that possible?
The configuration seems
Maybe i should better explain the reasons behind this question:
We have some domains, where the mail-relay is mapped to several
IP-Adresses (and servers) over an DNS entry.
That is, we have ONE mailrelay that can be configured as relayhost.
So far, so good.
BUT, we also have systems without
Thomas Ackermann:
I can map the mail-relays hostname only to one IP with /etc/hosts and
therefor, any redundancy is lost.
That is a bug in your operating system.
As a workaround, use smtp_fallback_relay.
I have used multiple IP addresses per name in /etc/hosts for as
long as I can remember,
Thomas Ackermann wrote:
Wietse Venema schrieb:
That is a bug in your operating system.
That made me test all of them :)
I used several runs of ping against the hostname after including it
with two entries into /etc/hosts
Cannot use getaddrinfo ...
getaddrinfo is a test program who's
Thomas Ackermann:
Wietse Venema schrieb:
That is a bug in your operating system.
That made me test all of them :)
...
Solaris 8 and 9:
AIX (AIX hostname 3 5 00C9FC9A4C00):
Linux (SuSE 9.3 and SuSE 10.3):
...
Which OS is not buggy then?!?
SunOS 3 (hey I said 21 years ago :-), maybe
delivered so I assume it's something to do with
the relayhost authentication.
Perhaps the log of that delivery attempt will be useful to the diagnosis.
So here's my main.cf configuration file, hopefully one of you can
point out my fault?
Thanks!
main.cf
Arthur Wiebe wrote:
[...]
Also I've monitored my firewall and I can see the connection to my
ISP's mail server when attempting to send an email using postfix. But
the email never get's delivered so I assume it's something to do with
the relayhost authentication.
So here's my main.cf
when attempting to send an email using postfix. But
the email never get's delivered so I assume it's something to do with
the relayhost authentication.
Perhaps the log of that delivery attempt will be useful to the diagnosis.
The firewall log I'm assuming you're talking about, just a very
to my
ISP's mail server when attempting to send an email using postfix. But
the email never get's delivered so I assume it's something to do with
the relayhost authentication.
Perhaps the log of that delivery attempt will be useful to the diagnosis.
The firewall log I'm assuming you're
My question is: My relay host is only allowing a certain number of
relayed mails per month. So rather than sending everything through the
R What about your ISP's SMTP server,
Yep, there's a limit (for non-arcor addresses, if I remember
correctly).
But do I read your response correctly that
On 26-Oct-08, at 12:11 AM, Stroller wrote:
On 26 Oct 2008, at 01:43, Charles Darwin wrote:
On 25-Oct-08, at 2:54 PM, Stroller wrote:
On 25 Oct 2008, at 17:01, Charles Darwin wrote:
...
In layman terms, what do mydomain and relayhost stand for? I am
running 9.5.0 Darwin (think BSD) and I
On 25 Oct 2008, at 17:01, Charles Darwin wrote:
...
In layman terms, what do mydomain and relayhost stand for? I am
running 9.5.0 Darwin (think BSD) and I would like to setup my
postfix to send messages to other machines on my network and/or over
the Internet.
In your case, from
On 26 Oct 2008, at 01:43, Charles Darwin wrote:
On 25-Oct-08, at 2:54 PM, Stroller wrote:
On 25 Oct 2008, at 17:01, Charles Darwin wrote:
...
In layman terms, what do mydomain and relayhost stand for? I am
running 9.5.0 Darwin (think BSD) and I would like to setup my
postfix to send
Hello all,
I have a problem with sender-dependent relayhosts. I'm using the stock
up-to-date postfix-2.3.3-2.1.el5_2 RPM that is part of CentOS 5.2 (if
that's a problem let me know and I'll try with a later version).
In short, if I put a relayhost parameter my sender-dependent relayhost
map gets
in main.cf...
relayhost =
sender_dependent_relayhost_maps = pcre:/etc/postfix/sender_relay.pcre
And here's the PCRE sender-dependent relayhost map with a wildcard
entry that sends all other mail through a different relayhost:
begin /etc/postfix/sender_relay.pcre
On Oct 3, 2008, at 2:49 AM, Wietse Venema wrote:
Johan Ström:
Hi
I got a situation where I need to relay ALMOST all mail through
another mail server. The catch is that I want a few specific sender
mail addresses to send directly from the postfix itself (as if I
didn't have a relayhost
If you really want no relayhost for a list of senders, this is not
easily done with Postfix. sender_dependent_relayhost_maps was
designed to do the exact opposite: specify a relayhost for a list
of senders.
If the sender list is REALLY small, you could use the pcre built-in
negation operator
Wietse Venema:
If you really want no relayhost for a list of senders, this is not
easily done with Postfix. sender_dependent_relayhost_maps was
designed to do the exact opposite: specify a relayhost for a list
of senders.
If the sender list is REALLY small, you could use the pcre built
For the record, in case this patch is missed at the end of a very
long message.
Of course we could introduce a hack where a special lookup result
of NONE (or some other magic string) means don't use a relayhost.
Postfix would then look like this:
/etc/postfix/main.cf:
relayhost
Hi, i want to restrict postfix to send mail directly to destination.
i m using ISP smtp server as relayhost ..i just want that postfix never
ever try to send mail directly to destination in case isp smtp server
fails.. i have already disabled DNS LOOKUPS. can any body tell me how
Hi, i want to restrict postfix to send mail directly to destination.
i m using ISP smtp server as relayhost ..i just want that postfix never
ever try to send mail directly to destination in case isp smtp server
fails.. i have already disabled DNS LOOKUPS. can any body tell me how
On Sun, 28 Sep 2008 19:53:07 +
Mumtaz Ali [EMAIL PROTECTED] wrote:
Hi, i want to restrict postfix to send mail directly to
destination. i m using ISP smtp server as relayhost ..i just
want that postfix never ever try to send mail directly to
destination in case isp smtp server fails.. i
Apologies if this is a trivial question, I haven't seen it discussed.
Searching brought up 1 related issue, which 1) was not answered and 2) was
looking at the problem from the wrong side. This was someone wondering how
to exclude bounces from the rest that he relayed to his relayhost.
I'm
relayhost.
I'm at the other side of the problem. We've got a server that's
relayhost for lots of clients of various configurations and sizes. Some
of these clients are, in fact, MX-es directly connected to the net, but
still use our server as an outgoing relay. Those of them that do delayed
I run Debian etch and i use smtp.gmail.com as postfix relayhost.
I also have a list of senders from different domains allowed to relay
smtp traffic on my server .
While for local senders in $myorigin i want my postfix to relay smtp
with gmail , for users in the list i want my local postfix
401 - 500 of 500 matches
Mail list logo
