After recent upgrade to Openserver 5.07, all security and patches to-date,
with MMDF as MTA, have come across the following problem.

PC's in network send email through 507 box, which channels it out over net.

the SMTP process, however, is adding the pc name to the host-name, after
which some upstream SMTP server is rejecting it because of a malformed
host-name header - apparently, the PC's name is getting pre-pended to the
user@hostname.

for example,
Your message cannot be delivered to the following recipients:

Recipient address: @tech1:marena@magnatechonline.com
Reason: Illegal host/domain name found

anyone know where this is happening and how to stop it?

--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
-Joe Chasan- Magnatech Business Systems, Inc.
joe@magnatechonline.com Hicksville, NY - USA
http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264

In article <20031114143845.A6904@magnatechonline.com>,
Joe Chasan <joe@magnatechonline.com> wrote:
>After recent upgrade to Openserver 5.07, all security and patches to-date,
>with MMDF as MTA, have come across the following problem.
>
>PC's in network send email through 507 box, which channels it out over net.
>
>the SMTP process, however, is adding the pc name to the host-name, after
>which some upstream SMTP server is rejecting it because of a malformed
>host-name header - apparently, the PC's name is getting pre-pended to the
>user@hostname.
>
>for example,
>Your message cannot be delivered to the following recipients:
>
> Recipient address: @tech1:marena@magnatechonline.com
> Reason: Illegal host/domain name found
>
>anyone know where this is happening and how to stop it?

That's a strange message. MMDF will in some cases generate a source route for
the *return* address, but not the recipient address. It may be that the
message is simply incorrect, and it's actually complaining about the return
address. This behavior can in some cases be worked around - see for example
http://groups.google.com/groups?selm...ader.tycho.net

But, there is currently no way of just turning it off. Correctly configured
MTAs don't have a problem with such addresses, but it wouldn't be surprising
to find some with anti-spam hacks applied that did. I'm working on an MMDF
supplement in which source routes are no longer added by default, but it'll
be a while before it's available.

John
--
John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/

On Fri, Nov 14, 2003 at 11:52:51PM +0000, John DuBois wrote:
> In article <20031114143845.A6904@magnatechonline.com>,
> Joe Chasan <joe@magnatechonline.com> wrote:
> >After recent upgrade to Openserver 5.07, all security and patches to-date,
> >with MMDF as MTA, have come across the following problem.
> >
> >PC's in network send email through 507 box, which channels it out over net.
> >
> >the SMTP process, however, is adding the pc name to the host-name, after
> >which some upstream SMTP server is rejecting it because of a malformed
> >host-name header - apparently, the PC's name is getting pre-pended to the
> >user@hostname.
> >
> >for example,
> >Your message cannot be delivered to the following recipients:
> >
> > Recipient address: @tech1:marena@magnatechonline.com
> > Reason: Illegal host/domain name found
> >
> >anyone know where this is happening and how to stop it?
>
> That's a strange message. MMDF will in some cases generate a source route for
> the *return* address, but not the recipient address. It may be that the
> message is simply incorrect, and it's actually complaining about the return
> address. This behavior can in some cases be worked around - see for example
> http://groups.google.com/groups?selm...ader.tycho.net

i believe that *IS* the return address mmdf is constructing.
so you are saying i should put something like
@tech1:marena@magnatechonline.com: magnatechonline.com
in the root.dom file?

i probably should have posted more of the error as i think i posted the
return failure - not the original delivery failure, which is more like:

Remote host responded: 550ification failed for
<marena%magnatechonline.com@tech1>


> But, there is currently no way of just turning it off. Correctly configured
> MTAs don't have a problem with such addresses, but it wouldn't be surprising
> to find some with anti-spam hacks applied that did. I'm working on an MMDF
> supplement in which source routes are no longer added by default, but it'll
> be a while before it's available.

my guess is it is an anti-spam thing that is trying to verify validity of
sender address.

--- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---
-Joe Chasan- Magnatech Business Systems, Inc.
joe@magnatechonline.com Hicksville, NY - USA
http://www.MagnatechOnline.com Tel.(516) 931-4444/Fax.(516) 931-1264

In article <20031114214345.A17904@magnatechonline.com>,
Joe Chasan <joe@magnatechonline.com> wrote:
>i believe that *IS* the return address mmdf is constructing.
>so you are saying i should put something like
>@tech1:marena@magnatechonline.com: magnatechonline.com
>in the root.dom file?

You need to map the source hostname that MMDF sees to the hostname the user is
supplying in the return address, so that MMDF will believe a source route isn't
needed:

tech1: magnatechonline.com

John
--
John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/