Re: Cannot receive External POP3 Email

Inline:

-Cliff

"Matabra" <Matabra@xxxxxxxxxxxxxxxxxxxx> wrote in message news:%23N70eQf$IHA.1180@xxxxxxxxxxxxxxxxxxxxxxx
Cliff,

whilst moving to SMTP would solve the problems, it is a complex task to do on an already existing infrastructure.
I disagree. You make sure addresses are added to each user (a max of 75 because this is SBS) and change the MX record. Leave pop3 running while the MX record propogates. I've *never* seen a 'complex' switch to SMTP.

We deal with clients who stay with Pop3, just on the basis that they are paying for it.
As Les said, they've paid for Exchange as well. They are paying for the same functionality (receive email) TWICE. A good consultant can pitch it as a money saving effort. If the pop3 service is bundled with other services (web hosting, etc) then they aren't really paying for it...it is free with the primary service they are paying for. Either way, I've *never* had a client balk because of price when presented with the two options. And I've been supporting SBS for a long time.

At the end of the day no matter how much easier it is to deal with , you have to work with what youve got and what the client will allow you to do.
The client wants results. They go to IT consultants (or hire an IT staff) to achieve those results. I agree that you have to work with what you've got. The trick here is ... *YOU'VE GOT EXCHANGE ALREADY!* If the client *understands* the technical details of the switch, they'll approve it. And if they don't (which most don't, and don't want to...that's why they hired a consultant!) then they'll go with the consultant's judgement. Again, as already mentioned. The push to keep pop3 *rarely* (in my case NEVER) comes from the client. It comes from an IT staff or perhaps 'former' consultant that didn't want to make the switch. And maybe that former consultant planted a few bad seeds. But they are still easy to overcome.



Whilst moving to SMTP delivery would be easier to manage in the long term , In the short term it might be overkill to change an entire email infrastructure to resolve this one problem.
Even in the short term, it is easier. The amount of time it would take to 'change an entire email infrastructure' (as outlined in the three steps above) could be done in a half hour. Give 3 days for the MX record to flush out of cached DNS servers, and by now, if the process were started when the thread was started, email would be flowing 100% to the exchange box. With less time than it took to type these replies. :) I consider that 'worth it' in the short term.

POP3 should work with SBS and
The pop3 connector is flaky at the best of times. It was included as a transition tool to SMTP and has been abused ever since. There are other documented problems and it lacks features that make it suitable for a long-term installation. For example, it does not (and cannot) support SSL. That means that email paswords are being transmitted IN THE CLEAR every time it checks email. If the users set their internal account password to be the same as they did their 'old' email password...you've got an instant security situation. That is just one example of the shortcomings of pop3.

that is why I have attempted to resolve the issue.
Despite my rant above about pop3, I agree this situation seemed, on the surface, to be easy. That's why I didn't pipe up early...and I never meant my reply (then or now) to be taken as a criticism of you. You stepped up, grabbed the ball, and carried it a long ways and I'd never want to discourage a fellow contributor. I was simply voicing my opinion that I think the problem was more complex than initially thought, and felt (and still feel) that switcihng to SMTP is the better, faster, cheaper (if the client pays by the hour), and ultimately most reliable solution. Especially when it isn't a hack, kludge, or duct-tape solution..but is in fact the recommended configuration regardless of whether there is a problem or not. So I wanted to see if we could avoid a long drawn out thread trying to solve a pop3 issue that...in all likelihood isn't an SBS issue...and is definitely unnecessary to troubleshoot given the alternatives.

I guess my hopes of avoiding a long, drawn out thread just went down in flames though. :)






"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message news:vJadnQjNv_IH5z7VnZ2dnUVZ_sudnZ2d@xxxxxxxxxxxxxx
Okay, I'm just gonna say it since nobody else has:

Switch to SMTP delivery and pull your mail in-house. That is one of the main reasons to *get* SBS instead of just win2k3. Otherwise you could jsut configure outlook/outlook express/windows mail to use pop3 directly with any old server. Let exchange do what it is supposed to do. You will no longer have this issue or have to figure out if it is your fault, your email provider's fault, where the message is getting dropped, etc.

Not sure why you went down the OE troubleshooting road. Your telnet test already told you everything you needed to know. The message is not in the pop3 box when you check. That means one of two things:

1) The box is being emptied elsewhere (another client connecting by pop3 and pulling them down before you do) or
2) The mail is not getting delivered to the pop3 box in the first place, which is not an SBS issue, but an issue between you and the host.

Either way, moving to SMTP eliminates BOTH problems. You can disable POP3 on SBS, you can control which clients connect, and you have full access to all logs so you *know* what is happening, not just guessing.

Does this answer what is going on? No. But since right now the problem involves a third-party, you may never *get* those answers...and moving to an in-house solution is *infinitely* easier to manage.

-Cliff

"TrickyT" <wigwam326@xxxxxxxxxxxxxx> wrote in message news:50529aaa-7b74-4904-809b-07641d2f31a0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 13 Aug, 16:59, "Matabra" <Mata...@xxxxxxxxxxxxxxxxxxxx> wrote:
No Probs, Just remember to post to let me know how it goes

Matt

"TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message

news:34c30fa5-bc8e-4a57-9605-d0a52e03b6a1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

> On 13 Aug, 16:25, "Matabra" <Mata...@xxxxxxxxxxxxxxxxxxxx> wrote:
>> Hi,

>> If the info account hasnt received an email in Oe then it is a >> problem
>> with
>> your service provider, not sbs.

>> Best bet is to ask them to investigate. As it will almost certainly >> be a
>> problem with DNS or their servers.

>> Regards,

>> Matt

>> "TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message

>>news:387c4e2e-739e-4a7f-9cc3-8531056a84c0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

>> > On 13 Aug, 16:13, TrickyT <wigwam...@xxxxxxxxxxxxxx> wrote:
>> >> On 13 Aug, 15:50, "Matabra" <Mata...@xxxxxxxxxxxxxxxxxxxx> wrote:

>> >> > Hi,

>> >> > Ok, sent a test mail. Your email server should be receiving >> >> > mails.

>> >> > Like i said, Try to connect directly to the pop3 account >> >> > through OE.
>> >> > You
>> >> > should see a mail from me there.

>> >> > If not, then the problem is with your hosting provider.

>> >> > If so, then the problem is with SBS/Pop3 Connector. If you >> >> > could
>> >> > check
>> >> > this
>> >> > for me it shows where we can begin troubleshooting.

>> >> > Regards,

>> >> > Matt

>> >> > "TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message

>> >> >news:6d600c42-9d82-4837-9e2e-66e6e013e626@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

>> >> > > On 13 Aug, 15:24, "Matabra" <Mata...@xxxxxxxxxxxxxxxxxxxx> >> >> > > wrote:
>> >> > >> Hi,

>> >> > >> If you cannot see any emails within telnet then it means >> >> > >> that
>> >> > >> there
>> >> > >> are
>> >> > >> no
>> >> > >> emails in the mailbox. The reason i suggested accessing in >> >> > >> OE was
>> >> > >> to
>> >> > >> see
>> >> > >> if
>> >> > >> there actually were any mails on the server.

>> >> > >> If there are no mails on the server then its worth checking >> >> > >> your
>> >> > >> MX
>> >> > >> records.

>> >> > >> What is your email domain. I can then send some test >> >> > >> messages to
>> >> > >> see
>> >> > >> what
>> >> > >> happens?

>> >> > >> Matt

>> >> > >> "TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message

>> >> > >>news:6e4fe135-f356-4f99-9afb-e60c3fec3278@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

>> >> > >> > On 13 Aug, 14:30, "Matabra" <Mata...@xxxxxxxxxxxxxxxxxxxx>
>> >> > >> > wrote:
>> >> > >> >> Hi,

>> >> > >> >> Can you check the eventlog to see if there are any >> >> > >> >> problems in
>> >> > >> >> there
>> >> > >> >> and
>> >> > >> >> post what they are?

>> >> > >> >> Can you access the POP3 account directly from outlook >> >> > >> >> Express?

>> >> > >> >> regards,

>> >> > >> >> Matt

>> >> > >> >> "TrickyT" <wigwam...@xxxxxxxxxxxxxx> wrote in message

>> >> > >> >>news:5daa6385-60d3-459b-9dcb-a21a772145b5@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

>> >> > >> >> > I have been informed by my client that they cannot >> >> > >> >> > receive
>> >> > >> >> > external
>> >> > >> >> > pop3 email.

>> >> > >> >> > They can send out to recipients, but not receive a >> >> > >> >> > reply.

>> >> > >> >> > They only have 5 users and have an external company >> >> > >> >> > provide
>> >> > >> >> > their
>> >> > >> >> > website and email. I have contacted the external >> >> > >> >> > company
>> >> > >> >> > who
>> >> > >> >> > inform
>> >> > >> >> > me there are no issues.

>> >> > >> >> > I have checked the following

>> >> > >> >> > Server Management

>> >> > >> >> > Internet and Email

>> >> > >> >> > Connect to the internet

>> >> > >> >> > Left all the other settings as they were

>> >> > >> >> > Enable Internet Email

>> >> > >> >> > Use DNS to route e-mail

>> >> > >> >> > Use the Microsoft connection for POP3 Mailbox

>> >> > >> >> > Email domain name xxxxxxxx.com

>> >> > >> >> > Pop3 mailbox

>> >> > >> >> > mail.xxxxxxxx.com
>> >> > >> >> > Port 110
>> >> > >> >> > user name - correct
>> >> > >> >> > passwords - correct
>> >> > >> >> > sending to correct Exchange mailboxes

>> >> > >> >> > Enable exchange to remove attachment.

>> >> > >> >> > I have also tried disabling the firewall but no >> >> > >> >> > difference.

>> >> > >> >> > The server has 2 NIC's

>> >> > >> >> > Any ideas?

>> >> > >> >> > Regards

>> >> > >> >> > Trevor

>> >> > >> > I have used the following command to check the account

>> >> > >> > Telnet mail.xxxxxxxxxxxxxx.com 110

>> >> > >> > user (username)
>> >> > >> > pass (password)
>> >> > >> > stat
>> >> > >> > OK 0 0

>> >> > >> > The server is only checking the for emails every 15 >> >> > >> > minutes but
>> >> > >> > if
>> >> > >> > I
>> >> > >> > send and email in between the checking times I still get >> >> > >> > no
>> >> > >> > emails
>> >> > >> > when I use Telnet.

>> >> > >> > Regards

>> >> > >> > Trevor

>> >> > > I have sent several messages to the users at the company, but >> >> > > also
>> >> > > CC
>> >> > > them to my personal email. I receive them but they do not.

>> >> > > The email domain in bancummsurfacing.com you could try >> >> > > sending it
>> >> > > to
>> >> > > i...@xxxxxxxxxxxxxxxxxxxx

>> >> > > I have no dealings with MX records as this is all done by our
>> >> > > email
>> >> > > hosting company.

>> >> > > Regards

>> >> > > Trevor

>> >> I have set up Outlook express on the INFO account and checked for
>> >> messages, none are in the inbox.

>> >> However, I see you replied at 15:50, and I did not check until >> >> 16:10.
>> >> Could the server have done its 15 minute check at 16:00 and taken >> >> the
>> >> mail?

>> > I have changed the retrieve setting on the POP3 account so it >> > checks
>> > every 2 hours. I then sent a message to the INFO account. With >> > my
>> > own address on the CC. I received the email but the INFO account >> > has
>> > not.

>> > Hope this helps.

>> > Trevor

> Matt

> Thanks for your help. I spent around 2 hours trying to work this > out,
> especially as they have a member of staff who occasionally tinkers!

> Did not think it would be an issue with the email company. Last > place
> I would have started looking.

> Regards

> Trevor

Matt

Just to let you know that I received your email sometime tonight. I
disabled checking on the SBS and have been monitoring it with OE. It
said I received it at 15:49. Yet it was not in my inbox until gone
21:00 tonight.

Regards

Trevor


.

Relevant Pages

  • Re: SBS users - Outllook 2003 vs Office 2002
    ... Client got used to it with Office 2002 and expects to have the same ... Monday I will uninstall Outlook ... POP3 virtual server disabled without warning. ... Les its OK - I have cancelled my order for a Linux version of SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: Autenticated SMTP Relay
    ... Your main decision is whenther to send email directly from your server out ... Since you are using POP3 to retrive incoming email, ... It is not a POP3 issue, but a SMTP issue ... >> The POP3 and IMAP services are by default are disabled on an SBS server. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SBS users - Outllook 2003 vs Office 2002
    ... My bet is the client won't know he's not using pop3 if you don't configure ... But that assumes you like outlook 2k3;-/. ... Les Connor [SBS Community Member - SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: POP3 access and Exchange server Message handling
    ... POP3 is not used for sending mail, ... Check the SMTP settings at the clients. ... mail sent through SMTP from a relaying client ... will not be sent to the SENT folder of that user. ...
    (microsoft.public.exchange.clients)
  • Re: POP3 connector to SMTP migration question
    ... SMTP, check this out: ... Javier [SBS MVP] ... > Due to one of my customers getting multiple emails since we put in a new ... Currently they are using the POP3 connector with a global mailbox. ...
    (microsoft.public.windows.server.sbs)