Date: 07 Jun 2001
From: Heimo Claasen <[EMAIL PROTECTED]>
Subject: Re: rotate dialing

Ronald - sorry for the slow reply but I've been away and am slow
to get through the backlog.

I remember from my own attempts to get around the problem with having
different "From:"s in a Nettamer-sent message that it was impossible to
get another than the one of the relevant "account #" as the first one
into the raw mail header (which is the one the receiving POP3 server
gets to see, and to compare with list subscrition e-ddresses for
acceptance, for instance) - Nettamer par force inserts the account-#'s
"From:" and "Reply-To:", and thus makes it impossible to use one
dial-up connection to an SMTP to get out the eventual other outgoing
mails (which should arrive with another "From:" thus at th server for
a subscribed list). No way.

With other MTAs (mail transport agent) there's quite some "batching"
needed, but at least it's doable.
(And it definitely saves me quite a number of these meter ticks for
otherwise each new dial-in.)
With Netmail for instance, it needs the substitution (kind of
"masquerading") of a different config-file for each different account,
and the restart of the MTA (with fetching mail).  Though this is
comparably fast, and in any case much less, in terms of metered fees,
than re-dialling. With outgoing mail this is simpler but the mails
have to be pre-processed so they would become a sequence in the same
source (sub)directory.

This would be exactly the same procedure with the NOS/uka_ppp MTA, for
instance, and other *nix derivates.

BTW, I think it _should_ work with a Yahoo access as the MTA does
negotiate always with the "right" _sender_ e-ddress, provided that
this one is set correctly in the "masquerading" MTA-config. (I have no
experience with Yahoo as NET access/service provider.) It depends very
much on which SMTP is used - if it's the _net_ access provider's, there
is no problem: the access server has authenticated the dial-in in any
case, and its SMTP would relay thus from the "legitimate" caller.

With a "third party" - an ISP's SMTP thus -, there is the usual check of
a preceding POP3 login: there is no other way to control the legitimate
use (and defence against unwanted remailing) for them, as for net access
via dial-in your IP address is temporary ("dynamically" attributed)
only. Thus this would be the Yahoo case.

The distinction between "net access" provider and (third party)
ISP-SMTP does not come out though - for me - precisely from what you
wrote there about your trial with CWnet.
(But in any case, and using Nettamer, I assume that you must have
dialled in anew each time - and that's the salient point for my case -,
in order to use a different "From:" account ?)

Now, to go back to the original problem posed by Constant, about the
rotating of dial-in points:
Nettamer offers 4 alternatives for dial-in phone numbers, but always
to the _SAME_ set-up of a net access/ISP combination.
(I think Constant's immediate consern had been answered in the meantime:
the non-rotating to a next number when there's a non-standard "busy"
event.)

HOWEVER, if you use a _different_ NET ACCESS provider through one of
these tel-no.s, you cannot use that very same setup of this precise
"account #" defined in Nettamer's "Setup #".
And thats _another_ problem than that we had it about here hitherto.

And as far as I can understand it, there's no solution for this problem
with using N't - those different tel-no.s must always go to the same
net access provider (with same entries for user-ID and login-PW).
Way out/around would be a more modular structure of the NAP/ISP setup.
(Which N't doesn't offer; q.e.d.)

// Heimo Claasen // <hammer at revobild dot net> // Brussels 2001-06-06
The WebPlace of ReRead - and much to read  ==>  http://www.revobild.net



********************************************************
To unsubscribe from this list,
send a message to [EMAIL PROTECTED] with the single word
                     Unsubscribe
as the subject.
You MUST use the same address with which you subscribed!
********************************************************

Reply via email to