EmailDelivery.com

🪵Velocity.log is vital to your success

Velocity.log knows all and sees all.

The most important component in the entire Velocity MTA ecosystem is velocity-install/logs/velocity.log.

  • Want to know if your configuration change went through? Check velocity.log.

  • Want to know why your message didn't get delivered? Check velocity.log

  • Want to know how an unsubscribe happened you swear you didn't do? Check velocity.log

  • Want to know why opens or clicks aren't showing up? Check velocity.log

  • Want a real-time look into the email delivery "black hole"? Check velocity.log

  • Want to open a ticket? Please check velocity.log

All outgoing email, incoming email, opens, clicks, and unsubscribes for mail sent through Velocity MTA are stored for eternity in the same file, to see the most recent 100 log entries do: 

tail -100 /root/velocity-install/logs/velocity.log

Upon startup, you should see output similar to the following

cdd9bc69586595e21c3404faf9814e2d534705de022132bfcf27ac33a427d114
License is activated!
:TRACE:::Starting

When changes to policies, server settings, or ip warmups have been pushed from the platform installation backend MTA UI you can verify they were received if you see output similar to the following 

:API:::172.50.100.1:33552 POST /settings
:API:::Finished writing settings

When sending a test message through the email marketing broadcast test widget, you should see output similar to the following for troubleshooting purposes

Test messages receive special handling

Messages using the test widget in broadcasts don't appear in the ip delivery reports or mail queue management, they receive the highest priority and bypass all other outstanding mail. This also applies to funnels.

When sending bulk production mail you should see output similar to the following

SEND, DEFER, SOFT, HARD

There are four types of potential delivery outcomes recorded in the velocity.log file

SEND means successful message delivery

DEFER means a sending pause has been triggered and shows you the complete error code and deferral message returned by the mailbox provider

SOFT shows you the complete error code and temporary bounce message returned by the mailbox provider

HARD shows you the complete error code and permanent bounce reason returned by the mailbox provider

Web activity for opens, clicks, and unsubscribes will be logged as HTTP GET requests, you should see output similar to the following

Complaints are processed by the incoming email MX server

PreviousGetting ready to sendNextInstalling Velocity MTA

Last updated

Was this helpful?