gromox-import(8)

πŸ“¦ version 3.6, in alpine 3.24

πŸ’… gromox-import β€” the import bestie (gromox-import(8), from the Gromox admin reference)

okay so listen, bestie, this page is literally the gromox-import page from the Gromox admin reference, and it's about yeeting all your mail items into Gromox. no cap, it's giving "glow-up for your mailbox." πŸ¦‹


✨ NAME ✨

gromox-import β€” the utility for importing various mail items into Gromox πŸ’–


🌸 SYNOPSIS 🌸

gromox-import [...] [-Dcpt] [-u [localpart]@domain.example] < input.mt

πŸŽ€ DESCRIPTION πŸŽ€

so gromox-import reads a Gromox-specific mailbox transfer format data stream (GXMT) from standard input, as generated by gromox-pff2mt(8) or other similarly named utilities. slay. πŸ’…

when the username option (-u) is provided, the folders and messages included in the stream get written to the specified Gromox mail store. otherwise? the utility just parses the stream β€” which is lowkey useful with -t,-p. 🫢

🚨 heads up: there is no cross-check for already-imported messages at this time. messages from the input stream will always generate new messages in the target mailbox. so yeah, no dupe protection, periodt. 😭

note that messages are always owned by the store they are in. and note that, when importing to a public store, you may need to set some additional permissions on that public store's folders so that a particular user is able to modify messages after they have been imported. (all import/export utilities use superuser access and need no permissions, iykyk.) πŸ‘‘


πŸ’œ OPTIONS πŸ’œ

  • -B name β€” place unanchored messages (those loose objects that don't request placement in any particular folder) into the folder specified by -B. the accepted names are documented in the gromox-mbop(8) manpage under section "Folder specification". unanchored messages can be produced by e.g. gromox-eml2mt, gromox-tnef2mt, gromox-pff2mt --only-obj, gromox-kdb2mt --only-obj. default: draft
  • -D β€” use delivery mode, i.e. treat messages as if they were sent through the mail system rather than being imported. as such, messages are subject to inbox rules, and folders in the MT stream will be ignored altogether β€” which also implies that -B is ignored. πŸ”₯
  • -c β€” continuous operation mode. errors during the import of a message are reported, but the utility will continue with importing more messages. the default is to exit after reporting a delivery error. (iconic "keep going bestie" energy ✨)
  • -p β€” show properties in detail (enhances -t).
  • -t β€” print a folder/message summary as these items are processed.
  • -u [user]@domain.example β€” the target mail store which to import mails to. for the public folder of a domain, leave out the local part, i.e. use @domain.example. πŸŽ€
  • -v β€” verbose mode: report individual FID/MIDs for newly created objects.
  • -x β€” when importing an MT stream that does not request message splicing, the utility will raise an error if a to-be-created folder already exists. this behavior can be turned off with -x. this option can be thought of what mkdir's -p option would do. 🧚
  • --loglevel n β€” maximum verbosity of general logging (not connected to -p, -t or -v). 1=crit, 2=error, 3=warn, 4=notice, 5=info, 6=debug. default: 4 (notice)
  • --skip-notif β€” skip emitting MAPI notifications (when -D is used). this is for development only. πŸ™ˆ
  • --skip-rules β€” skip executing rules (when -D is used).

⭐ EXIT STATUS NOTES ⭐

all input streams must have at least a valid magic signature (first eight bytes) β€” an input stream of length zero is treated as invalid rather than as a valid stream without any commands. so like, empty input is not a vibe, it's an error. πŸ’€


🌈 EXAMPLES 🌈

PFF import to a private mailbox:

gromox-pff2mt sample.pst | gromox-import -u user@domain.example

PFF import to a public folder:

gromox-pff2mt sample.pst | gromox-import -u @domain.example

πŸ¦‹ SEE ALSO πŸ¦‹

gromox(7), gromox-pff2mt(8)


πŸ’– aaaand that's the whole page, bestie! this was brought to you by Gromox β€” the source of the gromox-import(8) page β€” so go forth, pipe your .mt streams, and slay those imports. mwah! πŸŽ€βœ¨πŸ‘‘
πŸ“¦ where this page comes from