Please help.

I had a nightmareish fortnight - spyware etc (say no more). The bottom line
is I had to reinstall just about everything on our network. There are still a
few things that need sorting but my main problem is as follows:

POP3 accounts do not download on the exchange server
The event log goes
1027 - so I can log into the ISP
1029 - so the user name/password bounces

(this happenes to all my various ISP accounts so it is not an ISP problem.

If I telnet I can log in OK, and if I pop3 into the ISP from a workstation I
can download OK and the email goes into the mailbox also there is still an
error coming up (Task 'Microsoft Exchange Server' reported error
(0x8004010F): 'The operation failed. An object could not be found'. I am sure
this is a different issue and I rather sort out one thing at a time but any
ideas are appreciated.

It almost seems as if the username/password is getting scrambled. I checked
for malware - I saw that in one of the discussions in this newsgroup - but
that looked clean.

Of course I could always carry on using the workstation but it feels a bit
like pushing your car around town because you run out of fuel and the engine
would not start.

The registry entries for the POP3 look alright but then I am not sure if
that is the right place to start looking anyway.

Re: POP3 incoming mail not working by Lanwench

Lanwench
Tue Aug 15 18:55:24 CDT 2006

In news:3976D463-B9F3-497C-8099-314ED904BC17@microsoft.com,
Richard S (bridgetown) <Richard S (bridgetown)@discussions.microsoft.com>
typed:
> Please help.
>
> I had a nightmareish fortnight - spyware etc (say no more). The
> bottom line is I had to reinstall just about everything on our
> network. There are still a few things that need sorting but my main
> problem is as follows:
>
> POP3 accounts do not download on the exchange server
> The event log goes
> 1027 - so I can log into the ISP
> 1029 - so the user name/password bounces
>
> (this happenes to all my various ISP accounts so it is not an ISP
> problem.
>
> If I telnet I can log in OK, and if I pop3 into the ISP from a
> workstation I can download OK and the email goes into the mailbox
> also there is still an error coming up (Task 'Microsoft Exchange
> Server' reported error (0x8004010F): 'The operation failed. An object
> could not be found'. I am sure this is a different issue and I rather
> sort out one thing at a time but any ideas are appreciated.
>
> It almost seems as if the username/password is getting scrambled. I
> checked for malware - I saw that in one of the discussions in this
> newsgroup - but that looked clean.
>
> Of course I could always carry on using the workstation but it feels
> a bit like pushing your car around town because you run out of fuel
> and the engine would not start.
>
> The registry entries for the POP3 look alright but then I am not sure
> if that is the right place to start looking anyway

Hi - Exchange doesn't have a POP connector, which is what it sounds like you
want. Are you using SBS?

The POP3 service you're looking at would have to do with users connecting to
*your* server to download mail from it via POP3.

If you're using SBS with its POP connector, try posting in an SBS group - if
it's a third party POP connector, check their documentation.

Re the 0x8004010F errors - where and when are you seeing this exactly?

I don't recommend POP connectors, btw. Nor do most Exchange people.



Re: POP3 incoming mail not working by RichardSbridgetown

RichardSbridgetown
Wed Aug 16 03:44:02 CDT 2006

Thanks for your reply,

Sorry I should have been more specific; yes we use SBS, hence the POP3
connector is included in the Exchange. I appreciate the advise not to use it
(I can see why) but unfortunately I do not have a static IP and also I am
collecting from different ISP's (a 'safety net' I would like to keep - if one
ISP has got a problem I can at least send and to some extend receive
important stuff from another).

The point is that it worked fine before.

The 0x8004010F error is a different issue - what happened was, I tried to
create a new SMTP connector to see if there is a correlation - I know silly
me, but sometimes 'pulling your little toe can pop your shoulder back in the
socket'.
I have removed the second connector and the error does not appear anymore.

As I pointed out it seems as if my systems sends the password encrypted or
even not sent (no I have not selected SPA - I know neither of my ISP's
support it - I tried it just to be sure but there is no difference)


Is there actually a way of finding out what gets sent?


Kind Regards
Richard

Re: POP3 incoming mail not working by Lanwench

Lanwench
Wed Aug 16 07:57:40 CDT 2006

In news:3B837CC0-46EB-40B7-9BC5-C1918CC46221@microsoft.com,
Richard S (bridgetown) <RichardSbridgetown@discussions.microsoft.com> typed:
> Thanks for your reply,
>
> Sorry I should have been more specific; yes we use SBS, hence the POP3
> connector is included in the Exchange. I appreciate the advise not to
> use it (I can see why) but unfortunately I do not have a static IP
> and also I am collecting from different ISP's (a 'safety net' I would
> like to keep - if one ISP has got a problem I can at least send and
> to some extend receive important stuff from another).
>
> The point is that it worked fine before.
>
> The 0x8004010F error is a different issue - what happened was, I
> tried to create a new SMTP connector to see if there is a correlation
> - I know silly me, but sometimes 'pulling your little toe can pop
> your shoulder back in the socket'.
> I have removed the second connector and the error does not appear
> anymore.
>
> As I pointed out it seems as if my systems sends the password
> encrypted or even not sent (no I have not selected SPA - I know
> neither of my ISP's support it - I tried it just to be sure but there
> is no difference)
>
>
> Is there actually a way of finding out what gets sent?
>
>
> Kind Regards
> Richard

Try the SBS group, as I recommended. I haven't got a clue about the POP
connector.

Re static IP - that's no big deal. See www.dyndns.com or similar.
Re 20 different ISPs - that sounds messy. Register an Internet domain name
and host your own mail - you can still have someone else acting as backup
(store & forward) so mail won't get lost if your server crashes for some
reason. However, you should do your best to ensure that you have good
redundant hardware and a reliable Internet connection so this isn't a
constant issue!





Re: POP3 incoming mail not working by RichardSbridgetown

RichardSbridgetown
Wed Aug 16 08:42:01 CDT 2006

Thank's for your reply.


As it so happens we have a domain name and i us no-ip to get VPN connection,
but I thought for SMTP I need a static IP from my ISP.

Please can you enlighten me as to setting up a full SMTP without static IP?

(incidentely I only use two, not 20 ISP's and this is a bit of a historic
reason - thinking about it there is no desperate reason for keeping the
second one, since I always have one or two hotmail accounts for the 'just in
case' scenario.

Security is obviously an issue, so your advise would be gratefully
appreciated.

Kind Regards
Richard

Re: POP3 incoming mail not working by Lanwench

Lanwench
Wed Aug 16 08:58:06 CDT 2006

In news:A303A9F3-04FE-4A50-BAA3-3E9339F36F46@microsoft.com,
Richard S (bridgetown) <RichardSbridgetown@discussions.microsoft.com> typed:
> Thank's for your reply.
>
>
> As it so happens we have a domain name and i us no-ip to get VPN
> connection, but I thought for SMTP I need a static IP from my ISP.

Nope. But since you have a dynamic IP you'll want to send Internet mail out
via a smarthost, not directly.

>
> Please can you enlighten me as to setting up a full SMTP without
> static IP?

Set up your domain's primary MX record to point at your no-ip FQDN. You can
use the same A record for both your domains.

[Oh, and you should probably also look into a seconary (higher-cost) MX
record for backup. I use Dyndns.com and their MailHop BackupMX - which costs
a pittance and is worth it. They queue up the mail and automatically try
redelivery for X days. No-ip.com may have as similar service.]

See http://www.msexchange.org/tutorials/MF002.html for info on how this
works, but you'll need to re-run the CEICW in SBS to configure your server
itself.

>
> (incidentely I only use two, not 20 ISP's

Ah, whew.

> and this is a bit of a
> historic reason - thinking about it there is no desperate reason for
> keeping the second one, since I always have one or two hotmail
> accounts for the 'just in case' scenario.
>
> Security is obviously an issue, so your advise would be gratefully
> appreciated.

Well, when you use POP your credentials are being sent in clear text, so
that is actually *less* secure. If you don't want to expose your Exchange
server to the Internet at all, you could get another server
(postfix/sendmail/whatever) and stick it in a DMZ, have it get the mail and
relay it on to Exchange. But I probably wouldn't bother with this in a small
network....opening up port 25 inbound to your SBS box is not a real threat.

For more, post in the SBS group I mentioned. SBS does a lot of things its
own way, and you will get far more expert help in there.


>
> Kind Regards
> Richard