[nSLUG] Help! Eastlink is port-filtering my mail server
jeffw at chebucto.ns.ca
Tue Mar 2 19:38:09 AST 2004
There isn't a "sendmail packet". Aliant is blocking port 25, which is
almost, but not quite the same as, blocking SMTP.
The "mail message submission" protocol is SMTP with some fewer
restrictions, though every MTA that I have setup it is 'just' SMTP on an
alternate official port, 587. Before the machine crashed (and I lost the
configuration), I was sending mail out via (authenticated) SMTP on the
MSA port. I haven't yet reconfigured a remote machine to allow for this,
so I too have reverted to using Aliant to send mail. Others on this list
have reported sending mail out using SMTP listening on an alternate, and
My personal concern with using Aliant for outgoing mail is not that
blocking :25 is evil, but that there is a significantly less then 100%
delivery rate. And because my email address isn't an aliant one, I don't
get the error messages, if any are produced.
On Tue, 2004-03-02 at 18:43, Trevor Smith wrote:
> On February 5, 2004 06:46 pm, Chris Mikkelsen wrote:
> > Well, Eastlink isn't the only one that resently blocked all port 25
> > communication. Aliant has bocked outgoing mail about a month ago - fine I
> > have to use their stmp as a forwarder. About 4 days ago I noticed mail
> > bouncing, well Aliant blocked incoming mail as well.
> I am not too familiar with sendmail but I noticed a short while ago, when
> (re)installing FC1, that mail wasn't getting out from my computer. I seem to
> recall that I had assumed I could use sendmail directly from linux rather
> than using Aliant's smtp server. I also seem to recall that for a while, this
> worked. Then, IIRC, it didn't work. I shrugged and went back to using
> Aliant's smtp server (which is what I have always done in Windows anyway)
> because I had other fish to fry and couldn't spare the time to learn about
> sendmail to get things working.
> Is this all because Aliant is filtering outgoing sendmail packets?
More information about the nSLUG