On Thu, 30 Nov 2000 14:34:23 PST, Steve Witt writes: > [EMAIL PROTECTED]: > SMTP error from remote mailer after RCPT TO:<[EMAIL PROTECTED]>: > host smtp.flashcom.net.criticalpath.net [209.228.150.115]: > 553 To send mail, first check your mail with a valid POP account; this pre >vents unauthorized SPAM relaying. (#5.7.1) >
This is simple SMTP-after-POP, some ISPs allow relaying through them only if they know who sits on the IP which is sending them mail. Normally you do that only when someone tries to relay through you from a "foreign" IP eg via another ISP. After you authenticate via POP your IP is usually allowed relaying for ~30 mins or something, so you have two options: - run fetchmail before you flush your queue (that their pop-server is different from their smtp-server doesn´t matter, usually the ISP stores the IP in a backend-database which the smtp-servers check against) - do not relay, deliver yourself In the list-archives there is something about smtp-after-pop, I can remember seeing a thread about from ~6-12 months ago. hth, &rw -- / Ing. Robert Waldner | Network Engineer | T: +43 1 89933 F: x533 \ \ <[EMAIL PROTECTED]> | KPNQwest/AT | Diefenbachg. 35, A-1150 /
