>>I thought we determined that it was the send not being recognized? Or the >>domain not being used with smtp verbiage? I failed at doing this because >>I couldn't figure it out. Hell I'm just a stupid web designer not a geek. >>:-) > >I don't know WHAT your issues are with AT&T honestly. The only AT&T issue >that I am aware of is the SMTP connection reporting a network stream >error at the end of the connection. And I already did the work to >determine that it is a phantom error and should be ignored. Yes, its a >tad annoying that the error icon will blink, but its dealable, and >frankly is something that really should be fixed in Emailer (even if the >source of the problem is AT&T, I personally really consider it a bug in >Emailer because there are legit times a similar instance can occur, and >Emailer should know that once it recieves an OK to its QUIT request, that >the email is gone and sent, and no other errors should be reported on >that session).
Just to throw my hat in here... I use attbi, athough not for this subscription, and I don't even have the Network Stream Errors. I looked when this thread started (ages ago) and I think I got *one* like in October. But generally I do NOT get any errors from attbi servers. Make of that whatever you like... And btw, AT&T Broadband is GONE as a business. Comcast owns 'em now, but they are rolling out the brand switch over time/location. I'm sure it'll be someday that we need to switch the domain again. And more possible server changes too... Michael ============================================================ B U R N I N G C H R O M E D I G I T A L M E D I A Michael Black 3645 Madrid Circle Norcross, GA 30092 404-386-5548 [EMAIL PROTECTED] ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
