Re: Need help with import *.ldf

An import file will not use the same format as an exported file will.
Period. The only time you use the changetype of add is when you are
creating a new object, such as when you use an ldif import file to create a
new user account.

When you *modify* an existing attribute, you have to change the format of
the file. I just built an import file for the turflist to make sure this is
correct, and it is. Below is an example of an import file that will
successfully work. Please note the "-" at the end. This is required.

dn: CN=Default Message Filter,CN=Message Delivery,CN=Global Settings,CN=Your
Exchange Org Name,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=yourdomain,DC=com
changetype: modify
replace: msExchTurfListNames
msExchTurfListNames: *.yahoo.com
msExchTurfListNames: *.hotmail.com
-

OR, in your case, it would look like this. As I mentioned, when you are
modifying this attribute, you will need to leave in all the old entries, and
just add the new ones as additional lines, otherwise you will be sad when it
removes all of your old entries.

dn: CN=Default Message Filter,CN=Message Delivery,CN=Global
Settings,CN=INTERLOGICA,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=interlogica,DC=nl
changetype: modify
replace: msExchTurfListNames
msExchTurfListNames: *@kentmaster.com
msExchTurfListNames: *@mail.ru
-

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"addy" <addy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2BCA3B66-A879-45AB-ABD6-66C6C59D422A@xxxxxxxxxxxxxxxx
Ben,

Many thanks......
I think de format of the senderfilter.ldf file is correct.
When ik do a export from that specific server the is generated by it self.
So i cant see whats wrong about the file.
If you have any idee please let me know.
Kind regards,

Addy

"Ben Winzenz [Exchange MVP]" wrote:

Ah - ok. I thought it was just the two.

ADSIEdit forces you to enter them one at a time, so it won't be a good
solution when you have to enter that many, but do take a look at what I
said
about the format of the LDIF file - it does need to be set to a
changetype
of modify. I also suspect you'd need to have all the old entries in
there
as well, though I'm not positive on that - I haven't had a need to add
entries to the turflist, so I don't know if the import needs all the old
entries or not.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"addy" <addy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4D13B29D-16F3-44E9-B704-33745C68E94F@xxxxxxxxxxxxxxxx
Ben,

many thx i try ADSIEdit.
Iám not adding 2 entries but sometimes 100 on one day.

Kind regards,
Addy

"Ben Winzenz [Exchange MVP]" wrote:

I'm anticipating that the problem is that you need to "modify" this
particular attribute, rather than "add" it. You also probably want to
make
sure that your first line isn't improperly wrapping. The error
reported
"error on line 2: Object Class Violation". Well, you can't start a
line
with "Settings", so that would be part of the problem as well.

If you are just adding 2 entries to the Turflist, why don't you just
use
ADSIEdit? Constructing the proper LDIF file for this will take loads
more
time than simply adding the entries. ADSIEdit (if you haven't used it
before) is included in the Windows Support Tools (which is on the CD
in
the
/support/tools folder). Navigate to Configuration, Services,
Microsoft
Exchange, Your Org Name, Global Settings, Message Delivery, Default
Message
Filter properties, then scroll down until you see the
msExchTurfListNames
attribute and add the entries you want.

If you *really* want to use LDIF to import this, look at the link I
sent
earlier. The changetype needs to be set to "modify", not "add".
There
also
needs to be a "-" at the end of the entry - the site I included
earlier
shows you the correct context for modifying a record. I'd just be
careful
with this, though - if you aren't careful, you could completely
overwrite
anything that's in there now.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"addy" <addy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:24803951-49C3-455E-8811-C1D9C10F8BBD@xxxxxxxxxxxxxxxx
Ben,
thx again for reply.
this is the text in the file;
dn: CN=Default Message Filter,CN=Message Delivery,CN=Global
Settings,CN=INTERLOGICA,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=interlogica,DC=nl
changetype: add
msExchTurfListNames: *@kentmaster.com
msExchTurfListNames: *@mail.ru
I hope you can see what's going wrong.

Kind regards,
addy

"Ben Winzenz [Exchange MVP]" wrote:

I don't know what's wrong without looking at the ldif file. All I
can
say
is that the format of the file itself is probably incorrect.

What does line 2 of your import file contain?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"addy" <addy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8ED1BCB2-5381-4E7C-AEE5-660EFB7479EA@xxxxxxxxxxxxxxxx
Ben,
thx for reply, when i use that filter i get the following error
C:\>ldifde -i -f senderfilter.ldf -s mailsrv0
Connecting to "mailsrv01"
Logging in as current user using SSPI
Importing directory from file "senderfilter.l
Loading entries.
Add error on line 2: Object Class Violation
The server side error is "The object class at
0 entries modified successfully.
An error has occurred in the program
No log files were written. In order to gener
specify the log file path via the -j option.

what's going wrong?
Please help.
Kind regards addy

"Ben Winzenz [Exchange MVP]" wrote:

You don't have to specify a filter when you are importing.

Try it again just doing ldifde -i -f senderfilter.ldf

Also, make sure that you have the format of the import file
correct,
otherwise it won't work.

Refer to the following site for ldifde help.
http://www.computerperformance.co.uk/Logon/CSVDE_LDIFDE.htm

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"addy" <addy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:825C3218-4A5B-44A1-B9E8-1260D07E3101@xxxxxxxxxxxxxxxx
Please can enyone tell me how to import a file.

for export i use this commando;
ldifde -m -f senderfilter.ldf -r
"(objectcategory=msexchsmtpturflist)" -d
"cn=configuration,dc=interlogica,dc=nl" -l msexchturflistnames

I get the senderfilter.ldf file so i can modify it.
The problem is after i modify the file and try to import it
For the import i use this commando;
ldifde -i -f senderfilter.ldf -r
"(objectcategory=msexchsmtpturflist)" -d
"cn=configuration,dc=interlogica,dc=nl" -l msexchturflistnames

But this isn't going to work.
Please help.
Greets,
Addy














.

Relevant Pages

  • Re: Need help with import *.ldf
    ... replace: msExchTurfListNames ... changetype: modify ... removes all of your old entries. ...
    (microsoft.public.exchange.admin)
  • Re: Output to txt:
    ... Then to follow, are all the entries ... : column entry. ... To get around this for now, I format the output as html ... Word stores a file with embedded code to display it as it is seen on screen ...
    (microsoft.public.scripting.vbscript)
  • Re: QDE (Quick Date Entry)
    ... > ambiguous entries interpretted. ... I'm with you that an *individual* user has his format and sticks to it. ... > functionality just ain't that complicated. ... What one can argue about is if using ...
    (microsoft.public.excel.worksheet.functions)
  • Re: Need help with import *.ldf
    ... I think de format of the senderfilter.ldf file is correct. ... I also suspect you'd need to have all the old entries in there ... Read my blog! ... Refer to the following site for ldifde help. ...
    (microsoft.public.exchange.admin)
  • Re: QDE (Quick Date Entry)
    ... The user DOES NOT have to enter dates in yyyy-mm-dd format. ... alternative 2- or 3-digit short date entry treatment. ... QDE is the logical opposite of a one-size-fits-all approach. ... I'll admit my macro doesn't handle such entries ...
    (microsoft.public.excel.worksheet.functions)