On 2012-06-28 email builder wrote:
Do not accept mail that you know you can't deliver. Either use
$relay_recipient_maps (building the list and pushing it to the
frontend server can be implemented with a simple script), use LDAP
lookups (in case your recipients are listed in an LDAP directory),
Thanks for the help everyone. Does anyone have experience
or comments about this:
The only other solution I can see is to use something
like Nginx to just proxy the SMTP conversation through
the relay to the internal MTA. I haven't tried this before,
but if Nginx can perform fast enough
email builder:
Thanks for the help everyone.? Does anyone have experience
or comments about this:
The only other solution I can see is to use something
like Nginx to just proxy the SMTP conversation through
the relay to the internal MTA.? I haven't tried this before,
but if Nginx can
Specific questions I had were if I can use the standard
DNS load balancing (multiple MX records, same priority,
possibly multiple IPs resolving to one A record) setup
*behind* a relay server (those MTAs behind the relay
only being available via the relay and never directly).
Well, it looks
On 2012-06-28 email builder wrote:
Specific questions I had were if I can use the standard DNS load
balancing (multiple MX records, same priority, possibly multiple IPs
resolving to one A record) setup *behind* a relay server (those MTAs
behind the relay only being available via the relay and
Specific questions I had were if I can use the standard DNS load
balancing (multiple MX records, same priority, possibly multiple
IPs
resolving to one A record) setup *behind* a relay server (those MTAs
behind the relay only being available via the relay and never
directly).
On 2012-06-28 email builder wrote:
Well, it looks like I could do
relay_domains = example.com
transport table: example.com relay:other.com
I have to use other.com in the transport because I need to use
DNS-based load balancing of multiple SMTP servers on the backend,
but the relay is
Ansgar, thank you for your patience:
Well, it looks like I could do
relay_domains = example.com
transport table: example.com relay:other.com
I have to use other.com in the transport because I need
to use
DNS-based load balancing of multiple SMTP servers on
the backend,
On Thu, Jun 28, 2012 at 07:30:02PM -0700, email builder wrote:
example.com relay:internal.smtp.example.com
* mail for example.com arrives at the relay because
it is the highest priority MX record for example.com
Yes, but don't use the word relay here, it is too easily confused
with the
* mail for example.com arrives at the relay because
it is the highest priority MX record for example.com
Yes, but don't use the word relay here, it is too easily
confused
with the transport name, calle it the border MTA or the SMTP gateway,
OK thanks for the language tips
* the
Hi everyone,
I haven't played with relay servers much. I really thought
there was a RELAY_README but I find no README
files with RELAY in them at all. Hmmm. Where can
I get the basics?
Specific questions I had were if I can use the standard
DNS load balancing (multiple MX records, same
11 matches
Mail list logo
