On Sun, Mar 14, 2004 at 09:18:52AM -0700, Monique Y. Herman wrote:
On 2004-03-14, Vineet Kumar penned:
That part about the process on port 25 is a bit strange, but having
the init scripts in place shouldn't be a problem. Init scripts hang
around when you remove (without purging) a
On 2004-03-16, Andy Firman penned:
I finally got motivated and upgraded to Exim4 as well but I did not go
to the effort of using a backup MX. From what I know, most good MTA's
are built with redundancy and will try for a couple of days before
they drop any mail. My concern was being down
* Monique Y. Herman ([EMAIL PROTECTED])[20040313 21:47]:
In summary, the conversion itself was fairly painless. The only gotchas
were that the exim start links were not removed from /etc/rc?.d and that
for some reason something (presumably some undead form of exim3) was
holding on to port 25.
On 2004-03-14, Vineet Kumar penned:
That part about the process on port 25 is a bit strange, but having
the init scripts in place shouldn't be a problem. Init scripts hang
around when you remove (without purging) a package, but they usually
begin with something like
Hi all!
This is just a description of what I did to upgrade from exim3 to exim4.
I hope it's useful to someone.
I have an MX backup, so the first thing I did was to disable port 25 on
my router. The logic was that this way, I could test my mail server
internally without risking a loss of mail
5 matches
Mail list logo
