Problems with BLU mail?

[John Abreau]

Jerry just changed the MX for blu.org a few days ago to point to olduvai
instead of asgard. Asgard is the older machine, still running Redhat 7.x,
and I've had no luck trying to upgrade it in-place. It's too old to get
current versions of MailScanner and SpamAssassin to work properly.

We're migrating everything off asgard for now so we can rebuild it from
scratch, with either RHEL or CentOS. Once that's done, the plan is to do
the same with olduvai.

Ultimately we're thinking about having four servers: one that's strictly for
email, one that's strictly for web, one for trying out VMware or Xen, and
one for everything else.


On 12/27/06, Tom Metro <blu at vl.com> wrote:
> David Kramer wrote:
> > I noticed that my discuss at blu.org posts were taking a very long time
> > (hours) to come back.
> ...
> > Am I the only one this is happening to?
>
> I'm seeing some of this too.
>
>
> > Dec 24 07:00:53 uninew postfix/smtpd[19189]: connect from
> > asgard.blu.org[216.235.254.231]
> > Dec 24 07:00:53 uninew postfix/smtpd[19189]: lost connection after
> > CONNECT from asgard.blu.org[216.235.254.231]
> > Dec 24 07:00:53 uninew postfix/smtpd[19189]: disconnect from
> > asgard.blu.org[216.235.254.231]
> >
> > Dec 26 19:22:07 uninew postfix/smtp[22793]: 87CF03F698: conversation
> > with olduvai.blu.org[216.235.254.232] timed out while receiving the
> > initial server greeting
> > Dec 26 19:22:08 uninew postfix/smtp[22793]: 87CF03F698:
> > to=<discuss at blu.org>, relay=asgard-usdc.blu.org[216.235.254.231]:25,
> > delay=301, delays=0.24/0.01/300/0.23, dsn=2.0.0, status=sent (250 Ok:
> > queued as 095D426FAB)
>
> It seems like there are two different issues going on here. One is
> dropped inbound connections to you from asgard.blu.org. I didn't check
> my logs for that.
>
> The other is timeouts when you send mail to olduvai.blu.org, the primary
> MX for BLU. When I try connecting to port 25 on olduvai.blu.org, I
> connect after a long delay, and after many minutes still haven't seen an
> SMTP banner. I can ping it fine, but traceroutes show !C ("access to the
>   network or host is prohibited") showing up on the final hop. It seems
> to respond immediate to ssh (presenting the banner and key fingerprint),
> so I'd say there's probably something wrong with the SMTP daemon.
>
> I can connect to asgard.blu.org's SMTP server fine, after a slight delay.
>
>   -Tom
>
>
> --
> Tom Metro
> Venture Logic, Newton, MA, USA
> "Enterprise solutions through open source."
> Professional Profile: http://tmetro.venturelogic.com/
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>


-- 
John Abreau / Executive Director, Boston Linux & Unix
GnuPG KeyID: 0xD5C7B5D9 / Email: abreauj at gmail.com
GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.