Joseph L. Casale <[EMAIL PROTECTED]> wrote:
> >To clarify, destination MTA != relay, right? According to your logs,
> >the problem (lost connection) occurs with the relay on port 24.
>
> The relay is not being used as I push out to the primary via port 24 which
> is not blocked by the ISP. As a
>To clarify, destination MTA != relay, right? According to your logs,
>the problem (lost connection) occurs with the relay on port 24.
The relay is not being used as I push out to the primary via port 24 which
is not blocked by the ISP. As a result, the backup mx communicates directly
with the pr
Joseph L. Casale <[EMAIL PROTECTED]> wrote:
> >Does the mail you successfully send via telnet contain the exact same
> >text/body as the one stuck in your queue?
>
> Yea, and upon further investigation, smaller sized mail gets through fine.
> The destination MTA is Postfix as well with ASSP in fr
>Does the mail you successfully send via telnet contain the exact same
>text/body as the one stuck in your queue?
Yea, and upon further investigation, smaller sized mail gets through fine.
The destination MTA is Postfix as well with ASSP in front. In order to rule
out ASSP I stopped it and reconfi
Joseph L. Casale <[EMAIL PROTECTED]> wrote:
> I am now having trouble sending mail to a domain that I am also backup mx for.
> as port 25 outbound is blocked, I route with a relayhost, but for the domain I
> am backup mx for, I have the following in my transport file:
> example.com smtp:[mail.exam
I am now having trouble sending mail to a domain that I am also backup mx for.
as port 25 outbound is blocked, I route with a relayhost, but for the domain I
am backup mx for, I have the following in my transport file:
example.com smtp:[mail.example.com]:24
This was working for some time? I can sen
