On Thu, 2007-08-02 at 17:35 +1000, yhus Hu wrote: > How can I set up to call openchangeclient to fetch mails into an Inbox > rather than to print out mails on a stand output?
openchangeclient can't.
You should be using exchange2mbox instead (man exchange2mbox):
exchange2mbox provides a way to synchronize an Exchange mailbox with a
mbox file. The tool is developed so it only retrieve mails not already
stored in the message ID index database and reflect changes back to
the Exchange server if local message copy are deleted.
Basically it creates a mbox file you can read with mutt or any other
messaging client supporting mbox.
> I've set "--storemail="/home/work/TestOpenChangeMail/Inbox", but the
> mails were still print out on the stand output, only a frame dump file
> MAPIIN~2.TXT in the Inbox.
storemail only retrieves and store attachment files from you Exchange
mailbox messages (man openchangeclient):
Store mail attachments on the local filesystem in the specified
directory.
> How does the --notifications works with command line openchangeclient?
> Or, it is only working with a grafic email client?
Still from openchangeclient man page:
Monitor NEWMAIL notifications in the Inbox folder and display summary
on standard output.
If you want to test it, open 2 shells:
1. run openchangeclient --notifications in shell #1
2. Send an email to this exchange account with openchangeclient
--sendmail in shell #2
On shell #1, you should have something similar to:
[EMAIL PROTECTED] ~]$ openchangeclient --notifications
[+]New mail Received!!!!
Parent Entry ID: 0x8814000000000001
Message Entry ID: 0x1223000000000001
Message flags:
MSGFLAG_UNMODIFIED (0x2)
MSGFLAG_FROMME (0x20)
Message Class: IPM.NOTE
> I have also tried to run a server, following the howto.txt, it seems
> there is only a command to call "smbd -d3 -i -M single", does that
> mean that the server is running with in the smbd, or shoud there be
> another command to run server?
OpenChange server side runs within smbd. It benefits from Samba4 modular
architecture to register new endpoints and offers new features (Exchange
Address Book provider in our case).
> Then I try to create a profile to connect to the server, it failed and
> printed out following error, but debug messaes from smbd seems success
> for NSPI except a single_terminate from NT_STATUS_END_OF_FILE? Seems
> something I was missing on the set up ?
Indeed. When you complete profile creation successfully, you also have
NspiDNToEph and NspiGetProps debug strings on stdout:
[...]
##### in NspiQueryRows ####
emsabp_fetch_attrs: Comparing instance_key 0x6a91 with 0x6a91
emsabp_fetch_attrs: INSTANCE_KEY matches
NspiQueryRows : Success
##### in NspiDNToEph ####
NspiDNToEph : Success
##### in NspiGetProps ####
emsabp_fetch_attrs: Comparing instance_key 0xab7 with 0xab7
emsabp_fetch_attrs: INSTANCE_KEY matches
NspiGetProps : Success
##### in NspiUnbind ####
single_terminate: reason[NT_STATUS_END_OF_FILE]
In your case, the only reason why it fails at this stage of the process
is that it didn't find homeMDB attribute in the Samba4 Active Directory
user's record you are searching. It sounds to me like you have forgotten
to run ./script/oc_newuser.
That's the best I can do with the info you posted on the list.
Regards,
Julien.
--
Julien Kerihuel
[EMAIL PROTECTED]
OpenChange Project Manager
GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
