Trace Anonymous Gmail Sender
$750-1500 CAD
Posted 1 minute ago
•
Ends in 23 hours
$750-1500 CAD
Paid on delivery
This project centres on pinpointing the individual behind a Gmail account that keeps posting misleading messages to a mailing list of organisation members. I can supply every original message with full headers as well as our list-admin logs, so you will have raw material for a proper header and path analysis, log correlation, and any other forensic techniques you prefer. Scope of work • Use your tech knowledge to come up with a plan to investigate as needed to find the culprit No threats or harassment are involved, just persistent nuisance posts, so the goal is confirmation of identity, not emergency takedown. Tools such as Wireshark, exim/postfix log analysis, DNS, SPF/DKIM checks, and IP geolocation are welcome—use whatever combination you deem effective, provided the chain of custody for the data remains intact. ChatGPT has already done the below checks: Full email header examination SPF authentication verification DKIM authentication verification DMARC authentication verification Sending server IP analysis Sender's originating IP investigation Message-ID analysis Gmail proprietary header analysis Email-client identification Operating system identification HTML and MIME formatting analysis Embedded tracking and external resource examination Attachment metadata examination Sending versus delivery timestamp analysis Duplicate message identification
Project ID: 40809237
About the project
13 proposals
Open for bidding
Remote project
Active 23 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
13 freelancers are bidding on average $917 CAD for this job


Hello, Identifying an anonymous Gmail sender requires careful technical writing as well as disciplined handling of evidence, and my background as part of a multidisciplinary technology team supports a clear, accurate forensic report. Live Experts LLC has over a decade of technical delivery experience and hundreds of completed technology projects, with expertise spanning Python, cloud integrations, automation, and system analysis. I can document the investigation in a structured, evidence-focused manner using the supplied original headers and list-admin logs, while clearly distinguishing verified findings from assumptions. My technical writing skill is particularly relevant for correlating available records, explaining authentication and routing evidence, and presenting conclusions that are understandable and suitable for organisational review. I will also respect the integrity and chain of custody of the supplied data rather than overstating what Gmail headers can prove. I am ready to apply this technical and analytical background to produce a professional investigation report that helps you assess whether the available evidence can confirm the sender’s identity. Thanks!


Hello Tracing the source of misleading posts on your mailing list requires careful analysis of the email headers and server logs. Examining the full headers of the messages you provide, along with your list-admin logs, will allow for detailed path analysis and correlation. Techniques like SPF/DKIM validation and IP geolocation can help confirm the identity behind the Gmail account in question. Using tools such as Wireshark or postfix log analysis will assist in constructing a clear picture of the message origin. Maintaining the integrity of the data's chain of custody throughout the process is essential. A thorough plan can be developed based on the data you supply to identify the responsible individual accurately. Kind regards


Hi, one thing worth being upfront about before you send the files: when someone posts through Gmail's web interface, Google doesn't put the sender's IP in the headers, so the Received chain shows Google's servers, not the person. Headers alone rarely name anyone. These cases usually crack in your own data instead. What I'd build: a parsed timeline of every nuisance post (Date, Message-ID pattern, client hints, SPF/DKIM/DMARC results to rule out spoofing) correlated against your list-admin logs, subscription and join records, bounces and member activity around each post. Timing overlaps, the address's join date and recurring writing or client quirks often narrow it to a short list. I'd work only from data you hand over, hash every file on receipt and log each step so the chain of custody holds. Formal confirmation of the account holder comes through a lawyer's request to Google, and the report would be written to support that. You'd also get list fixes: moderation on that sender, posting limited to verified members, and DMARC-aware settings. Could you send the raw .eml files and logs? Which list software do you run, and does it keep signup confirmation records? Thanks, Daniel


EMAIL FORENSICS & HEADER ANALYSIS — READY TO INVESTIGATE! I can help develop a structured technical investigation plan to examine the misleading mailing-list messages and determine what the available evidence can reliably establish. My approach would include: ✦ Full email-header analysis, including Received paths and originating mail infrastructure ✦ SPF, DKIM, and DMARC authentication checks ✦ Correlation of message timestamps, message IDs, and list-administrator logs ✦ Review of relevant Exim/Postfix logs, where available ✦ IP address and mail-server infrastructure analysis ✦ Evidence preservation, documentation, and chain-of-custody procedures I'll distinguish verified technical findings from assumptions. Email headers and IP geolocation do not necessarily reveal the sender's real-world identity, but they can help establish message origins, routing patterns, and possible abuse of accounts or infrastructure. I can also prepare a clear forensic report with findings, limitations, and recommended next steps for reporting the activity to the relevant email provider or administrator. I'd be happy to review a sample message and the available logs before defining the investigation scope. Best regards!


Hi, I hope you're doing well. I understand you need a structured email-forensics investigation to determine what can reliably be established about the source of persistent misleading posts sent through a Gmail account. The key is to correlate full message headers with mailing-list administration and mail-server logs while preserving evidence and avoiding unsupported identity assumptions. I will develop an investigation plan covering header and Received-path analysis, SPF/DKIM/DMARC results, IP and infrastructure assessment, timestamp correlation, and relevant Exim/Postfix logs. I will preserve original files, record hashes and analysis steps, and distinguish verified findings from indicators or inconclusive evidence. The final report will explain the likely origin, confidence level, limitations, and appropriate next steps. I’ll keep the process evidence-led, confidential, and defensible, with a clear chain of custody throughout. Best regards, Volha


⭐⭐⭐Hello, and thank you for the detailed brief. I can help, but I want to be direct about what this evidence can establish. Messages sent through the Gmail web interface normally have the sender's internet protocol address stripped from the headers, so analysis will typically confirm the sending infrastructure and authentication results but rarely identify a person. My scope would be honest and still valuable: preserve every message with full headers and your list logs under a documented chain of custody, perform header, path, and authentication analysis, correlate the logs to establish patterns, and report precisely whether identity is ascertainable. Where it is not, I would set out the lawful routes, being an abuse report to Google, a formal request through legal process, or a complaint to the appropriate authority, alongside practical moderation such as restricting posting to confirmed subscribers. On a previous engagement titled Anonymous Message Investigation for a Membership Mailing List, the mission was to assess whether sender identity could be established from retained data, and my role was the analyst responsible for evidence preservation, header examination, log correlation, and the written findings report. Best Regards


Hi — Dzianis Charkasau here. I would work from the original messages and list-admin logs you supply, keep a clear chain of custody, and report what the evidence actually supports. First I would normalize each message: full Received path, Message-ID, Date, Return-Path, From/Reply-To/Sender, X-headers, and authentication results (SPF, DKIM, DMARC, ARC). I would correlate those with your list logs (submission time, size, client IP if logged, moderation events) and look for stable patterns: timing, subject/body fingerprints, and whether posts come through the list only or also direct. I would map IPs to ASN and hosting where headers permit, check PTR/forward DNS consistency, and flag mismatches (e.g. claimed Gmail but failing or inconsistent auth). I would not use threats, harassment, or unauthorized access, and I cannot obtain a Gmail account holder’s identity from Google without lawful process. Deliverable: a written report with methodology, timeline, technical findings, confidence levels (confirmed / likely / unknown), and practical next steps if identity stays masked (internal process, legal preservation, or provider abuse report with your evidence pack). Fixed price $800 CAD, 5 days from receipt of the full header set and admin logs. Are posts sent only via the list, or also directly to members—and is the list Google Groups, Mailman, or something else? Best regards, Dzianis Charkasau
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗