On 3 Feb 01 at 2:54, Howard Schwartz wrote:
> My corporate ISP just installed what the level-1 techs call a ``spam
> filter'' for the SMTP mail server. As a result, this server refuses
> to send mail out to anyone not already in its domain, unless my
> mail transport software identifies me as a trusted user, presumably
> with a userid and password.
Btw, just fyi: Pegasus Mail for Windows have used a similar
approach for a long time, think current version (3.x) still does ( I
use ver 2.55). David Harris implemented it as simple spam
prevention measure. What the client does is, when you try to send
mail, it will first connect to the POP3 host to verify you - the user
- can access it - before it starts the SMTP upload. But this is one-
sided client verification only, it does so even if the host do not
request or expect it. The latter seems to be the case for your SMTP
host. So the above info will probably not help you in anyway, just
thought I should mention it. On the other hand....it might be that
this is all that is required, that you log onto your pop account, and
once this is done, the SMTP host will allow you to upload... nah..
probably not that simple - since how can the SMTP host know the user
have been verified at the POP3 host? So probably some
authentication protocol in use in your case. Just thinking out load
here.
All the best,
Bjorn
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
