Re: All RCVD_IN_VALIDITY rules being applied to every email.

Greg Troxel <[email protected]>
Newsgroups gmane.mail.spam.spamassassin.general
Message-ID <[email protected]>
Nick Howitt <[email protected]> writes:

>> ... the account is free and then they hit you with an EULA that says
>> 
>>> The Services are available at the then-current rate. Customer shall
>>> pay all applicable fees when due as invoiced and, if fees are being
>>> paid via credit card or other electronic means, Customer authorizes
>>> Validity to charge fees using Customer’s selected payment method.
>> By my reading that means they can just decide to start charging you
>> and
>> you have no recourse?! Though the account is explicitly stated in huge
>> letters to be "free", so one hopes that would count as the "then-current
>> rate". The near-contradiction is unfortunate though, and there's no
>> indication about them having to tell you when they change their fees.
>> (Not that they could get any money from me without asking anyway.)
>> The account requires a 'company name', so I guess if you're an
>> individual you're... fucked?
>> 
> Sorry but this is conspiracy theory rubbish. You can open an account
> easily and use your name as a business. You can possibly easily put in
> "none" or "n/a" and the account is yours. No billing details or
> address details at all so how can they suddenly start billing?
>
> Just accept that if you want to start using their information for
> free, you will have to give a name and email address. You will also
> need to declare an IP address or CIDR, presumably for their whitelist.

That is not rubbish.  Terms that say you agree to pay are a serious
problem even if there is no credit card information on file.  That has
the strong appearance of the Service intending to create an enforceable
contract.   And a mandatory "company name" field appears to mean just
that.  Nix makes an entirely fair point.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.