POP Mail Service ready but invalid login!

surjan

Hi Team,

I have been working on this problem for about 3 days and we need to launch in 5 days time!!, but have a really peculiar problem. SMTP has been tested and is working...so brill, BUT the problems is with the incoming mail settings. OSticket is saying that the service is ready, however, the login is invalid, (SCREENSHOT ATTACHED). The username and password has been tested and is an account which has been used to access mail.itchen.ac.uk through a web browser!

We are using Microsoft exchange server 2007, any suggestion would be really helpful!:

Look forward to your reply.

Surjan

ntozier

Ah excahange, how I love and hate thee.

Please goto "Admin Panel" -> "Emails" -> click on the email address that will be polling -> scroll down to "Mail Account (Optional)".

Here is what we use for our Exchange 2007 server.

Status: Enable

Host: SERVERNAME (the short non-FQDN NetBios name)

Port: 143

Protocol: IMAP

Encryption: None

Fetch Frequency: 2

Maximum Emails Per Fetch: 10

Delete Message: checked

If that looks good head over to exchange. Three things to do and remember here:

1. Open the Exchange Management Console. Navigate to Recipient Configuration -> Mailbox and browse to the user that you are using to send/receive email. open up properties . Click on the "Mailbox Features" tab. Make sure that which ever protocol you are using is enabled. .

Remember neither of these are enabled in the stock Exchange 2007 installation so you will need to enable them if you haven't already.

2. Exchange 2007: ships with SSL/TLS turned on by default so try enabling SSL at encryption in OST. If it still doesn't work, then it might be #2. Alternatively you can shut this off I believe that it is called "Opportunistic TLS".

3. Exchange 2007: Requires a Transport rule to accept mail from other devices on the network.

Open the Exchange Management Console and goto Server Configuration -> Hub Transport -> under Receive Connectors. Most of the exchange servers I have looked at have a "Default" entry there. We also set on up for the "Copiers" in the building which are scan to email copiers. You can shut off or require different levels of security in this tab.

I hope that this points you in the right directions.

surjan

thanks for the quick reply, however, I did exactly everything you said and used the same parameters....however, it loads and then I get a "http 505 error", as thought its almost timing out....can u suggest anything else?

Surjan

ntozier

You're getting a 505 response... *blink blink*

What web browser are you using? What webserver are you using?

surjan

IE Explorer 8 is the browser and I am using a all in one development web server called XAMPP, therefore hosted locally on 127.....address

really appreciate your help on this....

S:)

ntozier

Does this help?

http://support.microsoft.com/kb/811262(http://support.microsoft.com/kb/811262)

surjan

Thanks "ntozier" that was great the browser provided me the error I needed to fix the problem....it was the clearing of of the earlier http protocol.....:)

I was hoping you could also help me with something else, as you have been so helpful, is there anyway to archive the "closed" tickets (as at the moment they just sit under the closed tab, and there could be hundreds over a period of time if not backed up somewhere) and then have some sort of way of searching for them via different criteria's i.e. ticket number, name of ticket etc, this would be a great feature to add to the "Dashboard" of the admin panel....or put me in the right direction to someone that has done this.......

Surjan

ntozier

I completely neglected to re-visit this thread. Sorry about that.

OST does not currently have that sort of functionality built in stock.

If you just wanted to get rid of tickets that wouldn't be that hard, but to archive them would involve either

1. altering the current tickets table and adding an "archived" column. Then the code would have to be modified to check and see if archived = 1 then do not display the closed ticket. You would also have to make a script that allowed you to view and/or change that status to ever see them easily again.

2. creating a tickets_archive table with identical fields as tickets and moving the entries from one to the other after a certain age. You would then need to make a custom interface to be able to view the "archived" tickets which I imagine would be as easy as slightly modifying some of the existing php files.

In my opinion though neither would be easy for a PHP newbie. someone with some experience though should be able to bang out a solution in a few hours.

If you do not care about ever viewing them again though it would probably be easiest to make a SQL command that you could run monthly that just purged tickets over say 6 months old. Personally I don't think that I would do either. I like having the historical tickets around both for me to track things, and for clients to be able to view their old answers. It amazes me how many people end up asking the same thing more then once.