Re: SMTP authentification

From: Don Sykes (alphase@pacbell.net)
Date: 04/03/03 

From: Don Sykes <alphase@pacbell.net>
Date: Thu, 03 Apr 2003 18:31:16 GMT

I just went through a similar exercise, moving from one DSL to another.
After lots of trepidations, everything seems to be working fine now. The
only distinction I can see is I requested a static IP (over here you
have a choice of dynamic or static for about the same price).

For what it's worth, I'm running DEC TCPIP Services 5.1 and, after
registering my domain name with the DSL's name service, this is all I
had to do:

1. Setup my LAN IPs - result:
TCPIP> sho host
     LOCAL database
Host address Host name
127.0.0.1 LOCALHOST, localhost
67.125.xxx.xxx MYGATE (Address of my DSL router/modem combo)
67.125.xxx.xxx NTONE
67.125.xxx.xxx VMS2

2. Establish the BIND Name routes - result:
TCPIP> sho name
BIND Resolver Parameters
 Local domain: ALPHASE.COM
 System
  State: Started, Enabled

  Transport: UDP
  Domain: ALPHASE.COM
  Retry: 4
  Timeout: 4
  Servers: 206.13.xxx.xxx, 206.13.xxx.xxx (These were provided by my
DSL ISP)
  Path: No values defined

3. Setup the default gateway - result:
TCPIP> sho route/ful/perm
                             PERMANENT
Type Destination Gateway
PN * 0.0.0.0 67.125.xxx.xxx MYGATE

4. Setup a substitute domain and zone - result:
TCPIP> sho config smtp
SMTP Configuration
                                                                  
Options
Initial interval: 0 00:30:00.00 Address_max: 16
NOEIGHT_BIT
Retry interval: 0 01:00:00.00 Hop_count_max: 16 RELAY
Maximum interval: 3 00:00:00.00
TOP_HEADERS

Timeout Initial Mail Receipt Data Terminate
  Send: 5 5 5 3 10
  Receive: 5

Alternate gateway: not defined
General gateway: not defined

Substitute domain: HIDDEN, ALPHASE.COM
Zone: ALPHASE.COM
---------

Now all mail is routed through the default gateway. I did not have to
configure any special mail gateways. I know you were asking how to do
this using *dynamic* IPs, but I thought this might help you, or others,
who may give up on the dynamic method.

Cheers 

-- 
Have VMS, Will Travel
Wire paladin, San Francisco
(paladinATalphaseDOTcom)
-------------------------------
Phillip Helbig wrote:
> 
> I have come upon an obstacle in moving my hobbyist system from ISDN to
> DSL.  I used to have everything---"physical" connection to the ISP via
> ISDN, "logical" internet connection via the ISP, IP addresses, DNS
> services, domain registration---at a one-stop shop, namely my ISP.
> However, I'm forced to drop him because the costs are too high compared
> to DSL.  With DSL, the "physical" connection to the ISP, the logical
> internet connection, DNS services and domain registration are usually
> separate (though in my case the last two might be combined).
> 
> The disadvantage of this move is that up until now I have been using a
> mail gateway at my old ISP.
> 
> My new ISP requires either one of "his" email addresses in the From:
> header, or SMTP authentification.  I had hoped that access to the mail
> gateway would be IP-based (this has been my experience in the past), but
> alas that is not the case.  It's not a valid option for me to be forced
> to use a certain style of email address in the From: header.  I've
> registered a couple of domains with the parent company of the new ISP
> and hope that I could at least use these in the From: header (perhaps
> the parent company can offer me a mail gateway---I'm still waiting for a
> reply for this). I've registered another domain with the parent company
> of a company I am also using for dynamic DNS services, so perhaps again
> I could use a mail router there, at least for that domain; again, I'm
> still waiting for a reply.
> 
> Of course, I would like to use one gateway for everything.
> 
> One option would be SMTP authentification.  Can that be done with
> out-of-the-box DEC/Compaq/HP TCP/IP Services?  Can it be done with some
> additional software (MX?)?  Can it be done with a different TCPIP stack?
> 
> Another option would be to not use a mail gateway at all, but try to
> deliver the mail directly myself.  Would this be an option?  The dynamic
> IP addresses I use do translate to something, but there is no obvious
> connection to the From: header.  (There have been threads here
> discussing rejecting email on the basis of reverse DNS lookups, though I
> don't recall if the criterion for acceptance was that it translate to
> something at all or that it translate to something connected to the
> From: header.  On the other hand, the mail gateway of my old ISP doesn't
> have a reverse DNS entry, and I've never had any problems sending mail
> through that.)  Another worry would be that certain ranges of IP
> addresses are known to be used for "dial-up" access and are blocked for
> that reason by some folks.  If I go this route, is it enough to just
> undefine the alternate gateway in the SMTP configuration?
> 
> I don't want to use some open relay somewhere, since many folks
> (understandably) black-list those as sources of spam.  However, if
> someone has a gateway I can use, with verification via stealth (i.e.
> no-one else knows that it exists; probably not practical), addresses in
> the From: header (I could send you a list of valid ones) or IP address
> (though this would change on average every 20 hours or so), please let
> me know.  I'd be willing to pay a reasonable fee for such a service if I
> can't solve my problem more easily through other means.
> 
> What about the Reply-To: field?  Perhaps the ISP would be happy if the
> From: header was in his style, but the Reply-To: field contained the
> address I want people to reply to.  (I'm assuming that all mail clients
> honour this these days.)  How can one set this with VMS MAIL?  Years
> ago, I seem to recall that /SUBSTITUTE_DOMAIN with the NOHIDDEN
> attribute would put the substitute domain in the Reply-To: field and the
> real address in the From: field (and HIDDEN would put the substitute
> domain in the From: field and not set the Reply-To: field), but IIRC I
> couldn't reproduce this later and, since /SUBSTITUTE_DOMAIN is mainly
> intended for something else, this might have been just a can-go-away-at-
> any-time side effect.

Relevant Pages

  • SMTP authentification
    ... ISDN, "logical" internet connection via the ISP, IP addresses, DNS ... mail gateway at my old ISP. ... to use a certain style of email address in the From: header. ...
    (comp.os.vms)
  • Re: Liunx and DSL routing
    ... So aaa.aaa.aaa.158 must be the IP address of a Zyxel interface, ... as the "gateway" IP address in the aaa.aaa.aaa.156/30 subnet as well as ... traffic from other hosts to your host and from your host to other hosts. ... the ISP? ...
    (comp.os.linux.networking)
  • Re: Sharing ISPs
    ... the faster ISP below the one for the slower. ... ISP's networks to the routing table using a merit value that was below ... either default gateway, ... Those URLs you provided seem to indicate that the problem of one ISP failing ...
    (microsoft.public.windows.server.networking)
  • Re: 2 Gateways on 1 NIC on Windows Server 2003
    ... >> gateway as the router connected to the DSL modem... ... >> the router connected to the Cable modem. ... >> I currently have 1 NIC in my AV server. ...
    (microsoft.public.windows.server.networking)
  • Re: Exchange Reverse DNS
    ... It isn't really an exchange issue at ... Armed with that info, I would contact your ISP, and persist in talking to ... I also would suspect the gateway, but it could be how they have the net mask ...
    (microsoft.public.exchange.admin)