On the Exchange server, they should be able to enable
pop3 for just a specific account, only allowed access from a specific
IP.
But perhaps that's not "good enough" for
the Exchange/Security admins, as pop3 goes from "disabled" to
"enabled".
Not allowing external pop3 access, may only mean that they
prefer not having their users check private mailboxes from
work.
If any Perl hackers are listening, Win32::OLE or
Mail::Outlook may be of assistance in accessing an Exchange mailbox via
MAPI.
Both, i think, requires a working Outlook/MAPI install
on the server, though.
--
/Sune
Yes you are right,the problem is I don't think they would agree (where I
work) to open up POP3 access on the server.
I really don't know much about mail protocols, but Since they seem to even
block it to other external mail servers, I am guessing they think its a security
risk maybe.
Too much formality also!
On Feb 3, 2008 10:43 PM, Nils Breunese (Lemonbit) <
nils@lemonbit.nl> wrote:
Tcl Warrior wrote:
> Apparently where I work pop3
access is blocked/closed. port 110 on
> the mailserver is closed
>
I am also guessing that they are also blocking all pop3 access. I am
>
guessing so because I
> create a free account at hotpop, just to be able
to continue testing
> and figuring out otrs, but I can't even
>
access this mail box.
>
> Any ideas? Will otrs provide tigher
integration with MS exchange in
> future releases something that maybe
will
> bypass the issue I am having above or will email retrieval always
be
> pop3?
AFAIK Exchange supports POP3, but it needs
to be explicitly enabled.
Nils
Breunese.
_______________________________________________
OTRS mailing
list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
Support or
consulting for your OTRS system?
=> http://www.otrs.com/