mathiasbynens / mathiasbynens/dotfiles
Junk characters in mail
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 31.5k
- Forks
- 8.4k
- PR merge metrics
- No merged PRs in 30d
Description
Our cron failures are forwarded by using .forward mail on an ubuntu server, and some seemingly junk characters are introduced in the mail.
While we use a forked version of this, I have boiled it down to the following lines
```
if [[ $COLORTERM = gnome-* && $TERM = xterm ]] && infocmp gnome-256color >/dev/null 2>&1; then
export TERM='gnome-256color';
elif infocmp xterm-256color >/dev/null 2>&1; then
export TERM='xterm-256color';
fi;
```
All our mails have the following content at the start
```
(B [m
```
Any idea why?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the .forward mail setup on the Ubuntu server and the TERM/infocmp snippet shown in the issue; reproduce a cron failure forwarded through that path and inspect the leading characters. Done means identifying why “(B [m” appears and documenting or applying a fix, but the issue does not name a target file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, shell, ubuntu
- Domain
- cli, devops, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100