exchange2grommunio.ps1: "Could not open (null) for writing..."

dneuhaeuser

I'm currently preparing a migration and using this wonderful script.
After recent fix in gromox the imports are working now.

I'm just getting 2 identical error messages (in red) at the start of each mailbox import:
"Could not open (null) for writing: Bad address. Using stderr."

The script still continues and as far as I can tell imports are complete.
So I'm unsure how serious this message is and how it could be solved?

snippet from log:

[...]
Starting import of mailbox: abc@domain.de in grommunio.
Keyboard-interactive authentication prompts from server:
End of keyboard-interactive prompts from server

Could not open (null) for writing: Bad address. Using stderr.

pff: Reading /mnt/pstexport/abc@domain.de.pst...

Could not open (null) for writing: Bad address. Using stderr.

pff: ... 0.312703s

pff: Processing "abc@domain.de"...
[...]

WalterH

Which Windows Server and which Exchange Version including SP?

dneuhaeuser

Server 2016 and Exchange 2016 CU23 SU17

DVCon

It also happens with Exchange 2019 CU15 Sep25HU on Windows Server 2022.
Even though, migration seems to be OK.

crpb

are you all using password authentication or pubkey w/ or w/o pageant?

dneuhaeuser

I am using password auth.
Could this make a difference here?

crpb

dneuhaeuser I am using password auth.
Could this make a difference here?

Yes, as i added a bunch of stuff recently and didn't realy test passwordauth as i personally don't like to use it if i can avoid it.

Maybe i get to test it in the next couple days but i would still recommend using a pubkey instead.

Best to use a "ED25519" Key as the pubkey is very short for copy paste and current best-practice anyhow
Look at the bottom selection.

https://the.earth.li/~sgtatham/putty/0.83/htmldoc/Chapter8.html#pubkey
https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html for puttygen.exe download link.

/me could probably add some notes about it to the file...

WalterH

I have now seen this message with kopano2grommunio.sh, I suppose this must be one of the migration tools. Unfortunately, I do not currently have time to investigate.

dneuhaeuser

I just gave this a try with key auth (with and without pageant).

it is more elegant indeed, but does not make a difference regarding the error message:

Starting import of mailbox: administrator@domain.de in grommunio.
Could not open (null) for writing: Bad address. Using stderr.
Could not open (null) for writing: Bad address. Using stderr.

pff: Reading /mnt/pstexport/administrator@domain.de.pst...

crpb

Well, i found some silly errors i made when vimdiffing through my hackjob that worked as it should.

Only thing left that is odd are those messages but well..

Will create a merge-request later i guess which also will support a config-file to not have to change anything in the script itself. (just a . exchange2grommunio.config.ps1 🙈 )

crpb

This should now be fixed (haven't tried it tho)

https://github.com/grommunio/gromox/issues/180

dneuhaeuser

confirmed: updated grommunio to newest version (supported) and pulled newest exchange2grommunio.ps1 from github.
no more errors. thank you!