Craig White wrote:
> On Sat, 2006-06-03 at 09:46 -0700, Eric "Shubes" wrote:
>> Craig White wrote:
>>> On Fri, 2006-06-02 at 18:58 -0700, Eric "Shubes" wrote:
>>>> Just to let everyone know what happened:
>>>>
>>>> I found out that I have vDSL from Qwest. Normal DSL is not available,
>>>> and neither is a static IP address. I can't use another ISP either. I'm
>>>> locked in to Qwest for my ISP, with no static IP. My only option would
>>>> be Cox, and I'm not going there.
>>>>
>>>> I decided to use DynDNS's Mailhop Outbound service. There's a limit of
>>>> 150 relays/day, but it only costs $15/yr, and $10/yr for additional
>>>> increments of 150. The only destinations I've had a problem with are
>>>> cox.net and my brother's work. I seemed to remember getting a bounce
>>>> from AOL too, but I can't confirm.
>>>>
>>>> I found out how to tell qmail to route outgoing email through DynDNS's
>>>> service only for domains that I specify (control/smtproutes file), and
>>>> it's working nicely. Everything else (the majority by far) goes straight
>>>> out from my server to its destination.
>>>>
>>>> BL, I don't need a static IP address after all. I'm really liking
>>>> DynDNS.org. qmailtoaster.com is pretty nice too, but the documentation
>>>> is sketchy (welcome to Linux ;) ).
>>>>
>>>> Thanks for all the input.
>>> -----
>>> Use smarthost features...
>>>
>>> Sendmail
>>> define(`SMART_HOST',`smtp.west.cox.net')
>>>
>>> Postfix
>>> relayhost = smtp.west.cox.net
>>>
>>> Of course, you would need to change the smtp.west.cox.net to
>>> pop.phnx.qwest.net or whatever it is for Qwest but it's something very
>>> close to that.
>>>
>>> This would get all your mail delivered.
>>>
>>> Craig
>>>
>>>
>> I haven't been able to get that to work with Qwest.
>>
>> When I try to use their smtp server directly from my email client, they
>> reject it because the sender address in the *body* isn't from their domain.
>>
>> When I try to authenticate from qmail (like I'm doing with dyndns's
>> mailhop), quest's server doesn't recognize the authentication method:
>> No supported AUTH method found, continuing without authentication.
>> 63.231.195.31 does not like recipient.
>> Remote host said: 553 relaying denied.
>> Giving up on 63.231.195.31.
>>
>> Any idea how I can get qmail to authenticate with qwest's server(s)?
>> I'm running qmail-toaster.com's release of qmail, which includes the
>> qmail-remote-auth patch:
>> Robert Sander - qmail-remote-auth
>> http://www.ornl.gov/lists/mailing-lists/qmail/2002/03/msg00091.html
>>
>> Thanks for the assist.
> ----
> for reasons that have been hashed on list many times, I don't use qmail
> so I am of no use there.
>
> for usage of smarthost...you might want to check with Qwest DSL support.
> Cox has an interesting arrangement...if you are a residential user
> (DHCP), you can use smtp.west.cox.net. If you are a business user (fixed
> ip addresses), you have to call their technical support and get your ip
> address permitted to relay via a different smarthost. Qwest might permit
> you to use a smarthost if you register...best worked out through them.
I'll see if I can find a tech support person at Qwest who knows
something about smarthost (and learn more about it myself).
> Qwest does offer fixed ip addresses, if I recall, they are $15 a month
> for a 255.255.255.248 subnet mask (8 ip addresses, 5 usable). They will
> also fix the reverse lookups to point to whatever fqdn you want which
> basically solves all issues.
With regards to residential service, this is true for their normal DSL
(Choice DSL) services. For their vDSL (Choice Online) service, they do
*not* (yet) offer static IP addresses. Also, they offer either one
service or the other in any given location (area). Just wanted to make
this clear.
>
> Craig
Thanks, Craig.
--
-Eric 'shubes'
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss