Not quite right. If you're running it on port 25 on another
IP, just set the MX for the gatewayed domains to hit that
other IP directly. No need to have the messages spool twice.
...except we do realy for this messages only because we're scanning them for
viruses and spams ;-)
I'll try to
...except we do realy for this messages only because we're scanning
them for viruses and spams ;-) I'll try to implement such a double
spooling on the same machine on different IP's.
Gotcha.
--Sandy
Sanford Whiteman, Chief Technologist
Broadleaf
Now the question is: What can we do if the other MTA has a longer
failure then our queue timeout?
Well, that's what we call a queue timeout. :)
Seriously, that's why you set your queue lifetime for gatewayed
domains to a much longer timeout than the lifetime of general outbound
mail.
I don't want to sound stupid, but what do you mean by 'dns-based routing'?
My relay server (IMail 8.2) receives messages for two domains and forwards them
to the appropriate server using aliases (acampbell - [EMAIL PROTECTED]). How would
MS' SMTP do this?
adamc
Sanford Whiteman wrote:
as
Sandy, thank you for your answer.
Seriously, that's why you set your queue lifetime for
gatewayed domains to a much longer timeout than the lifetime
of general outbound mail.
As this Imail-Server is only gateway but this for 200k msgs/day for another
Mailserver near to this
).
Dan Donnelly
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sanford
Whiteman
Sent: Wednesday, June 01, 2005 3:18 AM
To: Markus Gufler
Subject: Re: [IMail Forum] Mail relaying change IP in hosts file
Now the question is: What can we do if the other MTA
So If I understand right you mean to set up MS SMTP on the same
machine but bound to a second IP on port 25 and configure Imail to
forward all messages to this IP? So this messages can have a much
longer queue timeout then the value on Imail. Right or completely
wrong?
Not
Actually Sandy, the Failed Domain Skipping setting gives you a
longer period, by default, doubling the queue time when the host
cannot be reached. It does have the effect of not delivering quite
as quickly after the host comes back up (1 hour, not 30 min, again
assuming defaults
Maybe someone has had this to solve before and so can help me a little bit:
Our Imail Server does relay (and filter) messages for another MTA. So we've
added the other MTA's IP to the relay for IP-list and to the hosts file.
Now the question is: What can we do if the other MTA has a longer
