I must have accidentally removed the comment (which is needed for removal of the section from the crontab file) before committing.

Some tickets suggest that the mailsync process doesn't have all environ-
ment variables set which are needed. For example:

https://github.com/LukeSmithxyz/mutt-wizard/issues/678
The error messages indicate that for mailsync, `XDG_DATA_HOME` is empty/
unset and hence it cannot resolve the user's gnupg folder.

This commit defines  those variables via the crontab,  which I think are
the relevant ones. Not sure though if these are all we need or if I for-
got some.

add uni.strath.ac.uk

Update UPMC/SU email address configuration

These might need STARTTLS explicitly disabled in the msmtp config file though

A user reports notifications not working on their setup because there is
no display id  contained in the `ps`/`pgrep` output  concerning the Xorg
process.

This commit checks if there's a display server running at all, and if so
it sends notifications even if there's no display id.

Resolves https://github.com/LukeSmithxyz/mutt-wizard/issues/661

Add ucsb.edu to domains.csv

Update domains.csv

Fix notifications on Wayland-based environments

remove old vars like pass_prefix, muttdir
reorder mailbox detection to find inbox case and later delim
offline delim set to _ which should avoid most issues

Fix duplicate mailsync notifications

mailsync: Check for ZDOTDIR when looking for environmental variables inside .zprofile and .zshrc

inside .zprofile and .zshrc.

~/.profile is not necessarily present when using zsh for login and
setting $ZDOTDIR in ~/.zshenv

Fix: `macro index o` overlapping with next account

When the transition is made from an offline profile to an online
profile, there is still someone else's macro - side effects...
Variables, macros, and so on must be taken-into-account
**symmetrically** with any of the `mutt-wizard`'s profiles.

🐛 Fix ProtonMail log-on failure when adding a new account

Part 2 of 2 for "Log-on not successful" bug when using ProtonMail.

The curl login check uses the imap(s) protocol, which means it will use
the default ports. However, when using ProtonMail, these ports are
different (namely 1143 instead of 993).

We now use the port variable in the curl login command, defaulting to
993 when the port was not overridden.

The port variable was already set when the ProtonMail flag (-p) was set.

Bug mentioned in:
Fixes:
- https://github.com/LukeSmithxyz/mutt-wizard/issues/608
- https://github.com/LukeSmithxyz/mutt-wizard/issues/622

Part 1 of 2 for "Log-on not successful" bug when using ProtonMail.

The curl login check defaults to `imaps` when `protocol` isn't set.
Because ProtonMail isn't using any TLS, we have to use the `imap`
protocol.
The `protocol` variable was never set, so now we set it when the
ProtonMail flag (-p) is set.

Bug mentioned in:
Fixes:
- https://github.com/LukeSmithxyz/mutt-wizard/issues/608
- https://github.com/LukeSmithxyz/mutt-wizard/issues/622

Update mailsync to check XDG_CONFIG_HOME for mutt config dir

added unitn.it related email infos