[RTTY] Fw: Mail delivery failed: returning message to sender

Jack West w7ld at olypen.com
Sat Jan 14 14:11:09 EST 2006


----- Original Message -----
From: "Mail Delivery System" <Mailer-Daemon at olypen.com>
To: <w7ld at olypen.com>
Sent: Saturday, January 14, 2006 11:08 AM
Subject: Mail delivery failed: returning message to sender


> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   w7why at verizon.net
>     SMTP error from remote mailer after MAIL FROM:<w7ld at olypen.com>
SIZE=3365:
>     host relay.verizon.net [206.46.232.11]: 550 You are not allowed to
send mail:sv4pub.verizon.net
>
> ------ This is a copy of the message, including all the headers. ------
>
> Return-path: <w7ld at olypen.com>
> Received: from ppp-2234.olypen.com ([208.229.228.239] helo=w7ld)
> by olypen4.olypen.com with esmtp() (Exim 4.43)
> id 1Exqkp-0004rf-EF
> for w7why at verizon.net; Sat, 14 Jan 2006 11:08:00 -0800
> Received: from 127.0.0.1 (AVG SMTP 7.1.371 [267.14.17/229]); Sat, 14 Jan
2006 11:08:27 -0800
> Message-ID: <005701c6193d$e63b8e40$8c13fea9 at w7ld>
> From: "Jack West" <w7ld at olypen.com>
> To: "Tom Osborne" <w7why at verizon.net>
> References: <007301c618d5$f0b4cfc0$c080a8c0 at laptop>
<003201c6193b$97be8c10$1f12fea9 at Tom>
> Subject: Re: [RTTY] ARRL Bandwidth Proposal - FCC Invites Comments
> Date: Sat, 14 Jan 2006 11:08:23 -0800
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook Express 6.00.2800.1106
> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
> Mime-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain; charset=iso-8859-1
> X-SENDER: w7ld at olypen.com
> X-Olypen-Virus: clean
>
> Hi Tom,
> This is kinda funny.  I agree with you.  Sometimes just for giggles when
in
> large SSB
> round table QSO, I will say to my buddy...."Hey Dave.  Lets drop down into
> the CW
> band where we can talk about these guys and they wont have a clue as to
what
> we
> are saying!"   This is true as my fist is not that good and most
"auto-copy
> CW software"
> will not copy it.  I just had to throw that out..
> 73
> de Jack / W7LD / "Lucky Dog"
>
> ----- Original Message -----
> From: "Tom Osborne" <w7why at verizon.net>
> To: "RTTY" <rtty at contesting.com>
> Sent: Saturday, January 14, 2006 10:51 AM
> Subject: Re: [RTTY] ARRL Bandwidth Proposal - FCC Invites Comments
>
>
> > >first, make sure that a frequency is
> > > not in use before transmitting and second no transmission is
> > > encrypted or obscured in any way.
> >
> > How about after morse code is abolished--will cw be an encrypted mode as
> > most won't be able to decode it :-)  73
> > Tom W7WHY
> >
> >
> >
> > _______________________________________________
> > RTTY mailing list
> > RTTY at contesting.com
> > http://lists.contesting.com/mailman/listinfo/rtty
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG Free Edition.
> > Version: 7.1.371 / Virus Database: 267.14.17/229 - Release Date: 1/13/06
> >
> >
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.17/229 - Release Date: 1/13/06
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.17/229 - Release Date: 1/13/06
>
>



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/229 - Release Date: 1/13/06



More information about the RTTY mailing list