forked from wingrunr21/griddler-mandrill
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datadog log formatting #1
Open
etlund
wants to merge
10
commits into
master
Choose a base branch
from
datadog-log-formatting
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Build CI against modern rubies I am not comfortable deprecating support for 2.1/2.2/2.3 etc until it starts becoming a pain point at run-time due to deprecation warnings, or when adding new features or fixing bugs. * Tempfile is not included in stdlib in modern ruby Depending on it implicitly seems like the kind of thing that could cause downstream suffering.
* Developers may include debug messages in their application logs There were some breaking changes with how the griddler gem was packaged. This caused rake to fail until we downloaded the photos and updated the spec helper. * Use Ruby 2.0 compliant syntax for defining protected methods
There appear to be several ways SPF fails where an application may want to still receive those messages. See [RFC4408 Section 2.5](https://tools.ietf.org/html/rfc4408#section-2.5) to determine whether a particular use case conforms to the SPF standard. Co-authored-by: Eric Lund <[email protected]>
Not sure why, but when an email has `dkim` it sets the spf to `nil` even if the domain *does* have a working `spf` record. This starts to treat `nil` `spf` values as `none` Example body: ```rb [{"event"=>"inbound", "ts"=>1682029694, "msg"=> { # ... "spf"=>{"result"=>nil, "detail"=>nil}, "dkim"=>{"signed"=>true, "valid"=>true}, } }] ```
…ow to configure it outside the gem
4194fca
to
6bd302d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.