Duh! 'Nuff said, my bad.

Jon


On Sun, Jan 15, 2017 at 11:18 PM, Rick Hiller -- W5RH via BVARC <
[email protected]> wrote:

> Jon,
>
> But you did not correct the .com bit    It is att.NET   NOT .
> [email protected] as in my e-mail stated......not .com as you keep
> using.
>
> Got it??????
>
>
>
> On Sun, Jan 15, 2017 at 7:28 PM, Jon Noxon via BVARC <[email protected]>
> wrote:
>
>> N5vcx at att.com bounced (and I correctly fixed the 'at' bit)!
>>
>> Jon
>>
>> Sent from my iPad
>>
>> Begin forwarded message:
>>
>> *From:* Mail Delivery Subsystem <[email protected]
>> -00191d01>
>> *Date:* January 15, 2017 at 6:44:20 PM CST
>> *To:* <[email protected]>
>> *Subject:* *Returned mail: see transcript for details*
>>
>> The original message was received at Sun, 15 Jan 2017 19:44:20 -0500
>> from m0049459.ppops.net [127.0.0.1]
>>
>>   ----- The following addresses had permanent fatal errors -----
>> <[email protected]>
>>    (reason: 550 5.1.1 <[email protected]>... User unknown)
>>
>>   ----- Transcript of session follows -----
>> ... while talking to [144.160.20.151]:
>>
>> DATA
>>
>> <<< 550 5.1.1 <[email protected]>... User unknown
>> 550 5.1.1 <[email protected]>... User unknown
>> <<< 503 5.0.0 Need RCPT (recipient)
>>
>> <mime-attachment>
>>
>> <mime-attachment>
>>
>>
>> _______________________________________________
>> BVARC mailing list
>> [email protected]
>> http://mail.bvarc.org/mailman/listinfo/bvarc_bvarc.org
>>
>>
>
> _______________________________________________
> BVARC mailing list
> [email protected]
> http://mail.bvarc.org/mailman/listinfo/bvarc_bvarc.org
>
>
_______________________________________________
BVARC mailing list
[email protected]
http://mail.bvarc.org/mailman/listinfo/bvarc_bvarc.org

Reply via email to