225https://oaidalleapiprodscus.blob.core.windows.net/private/org-stcZVBJ1mNRwgOvbicJP9InJ/user-E21r78bgEQFIYKRqNzbW4RfI/img-dogJoX2xOeBcZtHjrZVTP3ex.png?st=2025-03-28T13%3A58%3A58Z&se=2025-03-28T15%3A58%3A58Z&sp=r&sv=2024-08-04&sr=b&rscd=inline&rsct=image/png&skoid=d505667d-d6c1-4a0a-bac7-5c84a87759f8&sktid=a48cca56-e6da-484e-a814-9c849652bcb3&skt=2025-03-27T22%3A06%3A50Z&ske=2025-03-28T22%3A06%3A50Z&sks=b&skv=2024-08-04&sig=ecPC9Hix/2Y48dlCIJyo8TImtOoFJQhwKZMQ/i3XxrM%3D
“`
Verify your messages. Much of getting Gmail to mark emails spam or to put your emails in the inbox depends on the content of the email. Go nuts with verifying the following in your emails:
“`
Verify Markdown formatting with bbcode OR a markdown validator tool AND
Verify links using a linter to ensure all links, regardless of link open method, work by trying to follow them AND
Verify HTML embedded in email by using a linter, in this case the nu center AND
Verify links in Markdown using a tool that will parse Markdown into HTML before link checking AND
Verify plain text/ascii coding using the ascii validator AND
Verify general HTML coding with the validator
“`
Полагаю следующий код автоматически все сделает. Запускай отдельно, путь по PATH имеются?
“`
cat <<'EOF'>script.txt
#!/bin/bash
for email_file in *.pst; do
bbcompile -markdown ${email_file} | ram | ram https://validator.w3.org/nu/> | ram | ram https://validator.w3.org/> | ram https://validator.w3.org/nu/>
done
EOF
“`
Comment: Have you seen this before? Or did you just write it anonymously to help people here. I read it and have got thought. In my scheme we need to generate drafts as files and send them with tools, not from common script. Probably with my bashrc tricks)!/bin/bash

“`
Verify your messages. Much of getting Gmail to mark emails spam or to put your emails in the inbox depends on the content of the email. Go nuts with verifying the following in your emails:
“`
Verify Markdown formatting with bbcode OR a markdown validator tool
Verify links using a linter to ensure all links, regardless of link open method, work by trying to follow them
Verify HTML embedded in email by using a linter, in this case the nu center
Verify links in Markdown using a tool that will parse Markdown into HTML before link checking
Verify plain text/ascii coding using the ascii validator
Verify general HTML coding with the validator
“`
Полагаю следующий код автоматически все сделает. Запускай отдельно, путь по PATH имеются?
“`
cat <<'EOF'>script.txt
#!/bin/bash
for email_file in *.pst; do
bbcompile -markdown ${email_file} | ram
done
EOF
“`
Comment: Have you seen this before? Or did you just write it anonymously to help people here. I read it and have got thought. In my scheme we need to generate drafts as files and send them with tools, not from common script. Probably with my bashrc tricks)
