Return-Path: Received: from p3plzcpnl505020.prod.phx3.secureserver.net by p3plzcpnl505020.prod.phx3.secureserver.net with LMTP id m3SoGXfuimixexIA8crYLQ (envelope-from ); Wed, 30 Jul 2025 21:17:59 -0700 Return-path: Envelope-to: soumyaranjanlenka@abseclab.com, pravakar@abseclab.com Delivery-date: Wed, 30 Jul 2025 21:17:59 -0700 Received: from mail-ed1-f44.google.com ([209.85.208.44]:50404) by p3plzcpnl505020.prod.phx3.secureserver.net with esmtps (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1uhKjq-000000054Nh-48vl; Wed, 30 Jul 2025 21:17:59 -0700 Received: by mail-ed1-f44.google.com with SMTP id 4fb4d7f45d1cf-615a115f0c0so817053a12.0; Wed, 30 Jul 2025 21:17:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753935413; x=1754540213; darn=abseclab.com; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oLLKMZcdfTX42p3uJStqJkBbSqCOP6W/AA9lC6jZbIw=; b=jMsVqbo/96gyU728GVKK62fy9xqYpwiCrkujbD1GdkUtExgJqJlw8agumvo/ahPuV1 xrGelIAsDymHEuPGvKqDY3I8aN8P5/09HoLMx8FfEfsHB8kS65qsfshjxUKpv93zx1po Yko1fLG+bNHVC0JdGmpcdqC0/gmhfzj+tmLEaGk5AUqDi12lMq1xXALM2zcQpcG7WPXt jI8mbQZkdPiBuVvrRCqYDjurqey6RVHPYSeW+BXc37YXdO1REr/TiX6KS39ERh+aHleW ExNF487QQCxViZ+WD11phAFkXpHfE8NE4NX/JamSeTerGnbzjKFbFJ/yifCcYh+LK9t+ B0lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753935413; x=1754540213; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oLLKMZcdfTX42p3uJStqJkBbSqCOP6W/AA9lC6jZbIw=; b=eBPv8UP5P9VZI++rlv9WdjSeCAeq71UG5x0T3SdQ5uCHLGS1FumQdB/DnXHll3P8vX zbaU52GfP50XBd68YBl5bRWbbz1aveDRNx8URnzQWsVQYg+41EIwyDRV1B02VK6MNI3K LfurtMcYwYPN1fJv9xJopMpVttHBzeN6rG82FAHVy0okd+j1A6B80VjWN0Zh1h9DhIFS fRoU8ykFmMEEupxyzPuoIb6QJYE1sF9ysbqFIiB3+9nIafz7p5I/6knDEL2slM3Uh+bd i/tN/6AQOBbgjJ+9vPVTF4QNMV7mdoRDp0G5J9tCoHIM0+8cj30HWTGEO9Xke/c/2IIv haqA== X-Forwarded-Encrypted: i=1; AJvYcCW8RJRVaL72nMTSh+9nRUjThsYDcfpoKgBICqywtBcxwCW+0e9pxeTFBPQKZMgylw0RGWDdaaS7Kg==@abseclab.com X-Gm-Message-State: AOJu0Ywlx+X3PJ1xfhAFyEfz19G/TPY4uojgi047PGYjH+JMmuBRqTbm mCpt8gUjp+jzGj2w6T8/IxTQFqcUCnLlkmu2CONQZBvSI7cRJy09suWCqDwDP1YVZwwZ599Znif XR/QdDdRY1bNlONa5jV3EZKz7NEFKpDnw/baj X-Gm-Gg: ASbGncv5JMJrnIbiKPY9m0nr23xal+m2cBmUWcA7orzz/zX8PBlNQj2qlDGt1Kn8KNb We1+9YZFnJqz5J7mgal0PAOBmJuQXNpwI41OA9Os7g+dB/jFR8pvPLsdereWaalMbDs76z0f5/T 6YHeZLGj/XeMCiyAxtABOri5t5yzTtc9doLoeE7Z2dQqNY6gdy4dxbppnFOuXZdjETvPqZbxPPy ulEA2HIzq1yzPLBsZyfn9PH40yWsX2QmncpTYRIeASNSYQ= X-Google-Smtp-Source: AGHT+IEG6lB1DvwpthpTY53uppBHcP6WiPEUAylUW9CIb+/hvV9URxMHAHmgyRD0eMUAOwr+lwFkMGCszGVpOa4gP5g= X-Received: by 2002:a05:6402:1d4b:b0:615:4d39:a72b with SMTP id 4fb4d7f45d1cf-61586f3bbcemr5859590a12.11.1753935412800; Wed, 30 Jul 2025 21:16:52 -0700 (PDT) MIME-Version: 1.0 References: <477d787f4d93ef7e25d5d08968352163@abseclab.in> In-Reply-To: From: priyanka nath Date: Thu, 31 Jul 2025 09:46:40 +0530 X-Gm-Features: Ac12FXwh8lD_EGe0pB0PNl7zm_uQmtC1EFnIg_dFl9eVKWNx8dq8upsODShU_Zg Message-ID: Subject: Re: Missing Work Plan & Sheet Updates (28, 29, 30) To: "soumyaranjanlenka@abseclab.com" Cc: "hr@abseclab.in" , Satya , Pravakar Content-Type: multipart/alternative; boundary="0000000000003d30ad063b31e922" X-Spam-Status: No, score=1.0 X-Spam-Score: 10 X-Spam-Bar: + X-Ham-Report: Spam detection software, running on the system "p3plzcpnl505020.prod.phx3.secureserver.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: Dear HR Team, Thank you for bringing this matter to my attention. I would like to clarify that from my end, all issues have been resolved and the work is progressing as expected. The delay in sharing [...] Content analysis details: (1.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider [priyankanath187(at)gmail.com] 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit [priyankanath187(at)gmail.com] 0.0 RCVD_IN_VALIDITY_SAFE_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [209.85.208.44 listed in sa-accredit.habeas.com] 0.0 RCVD_IN_VALIDITY_RPBL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [209.85.208.44 listed in bl.score.senderscore.com] 0.2 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. [209.85.208.44 listed in sa-trusted.bondedsender.org] 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 GB_FREEMAIL_NUM Freemail spammy address X-Spam-Flag: NO X-BRAND: GoDaddy X-PRODUCT: cpanel-shz X-ENVIRONMENT: prod --0000000000003d30ad063b31e922 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear HR Team, Thank you for bringing this matter to my attention. I would like to clarify that from my end, all issues have been resolved and the work is progressing as expected. The delay in sharing the work plan for the dates mentioned (28th, 29th, and 30th) was due to extensive team discussions that extended beyond our usual working hours. During our team meeting, which ran past 9:30 PM, we identified several critical issues that required immediate attention and resolution. Since these technical issues can arise at any time during the day and need prompt fixing, we decided to finalize the work plan only after ensuring all concerns were properly addressed. Additionally, on July 15th, I had requirement discussions with the team to align on project specifications and deliverables, which also contributed to the overall planning process. I want to emphasize that these delays were purely work-related activities and should not be considered as leave or absence from duties. The team was actively engaged in project discussions, requirement analysis, and problem-solving during these periods. Moving forward, I will ensure better communication regarding any delays in documentation updates, even when the delay is due to extended work sessions= . Thank you for your understanding. Best regards, Priyanka Nath On Thu, Jul 31, 2025 at 9:44=E2=80=AFAM soumyaranjanlenka@abseclab.com < soumyaranjanlenka@abseclab.com> wrote: > Dear Team, > Thank you for bringing this matter to my attention. > I would like to clarify that from my end, all issues have been resolved > and the work is progressing as expected. The delay in sharing the work pl= an > for the dates mentioned (28th, 29th, and 30th) was due to extensive team > discussions that extended beyond our usual working hours. > During our team meeting, which ran past 9:30 PM, we identified several > critical issues that required immediate attention and resolution. Since > these technical issues can arise at any time during the day and need prom= pt > fixing, we decided to finalize the work plan only after ensuring all > concerns were properly addressed. > I want to emphasize that this delay was purely work-related and should no= t > be considered as leave or absence from duties. The team was actively > engaged in project discussions and problem-solving during this period. > Moving forward, I will ensure better communication regarding any delays i= n > documentation updates, even when the delay is due to extended work sessio= ns. > Thank you for your understanding. > Best regards, > Soumya Ranjan Lenka > ------------------------------ > *From:* hr@abseclab.in > *Sent:* Wednesday, July 30, 2025 11:01 PM > *To:* priyanka nath ; Soumyaranjanlenka < > soumyaranjanlenka@abseclab.com> > *Cc:* Satya ; Pravakar > *Subject:* Missing Work Plan & Sheet Updates (28, 29, 30) > > Dear Team, > > It has been observed that the work plan was not shared and the sheet was > not updated for the dates 28th, 29th, and 30th. Please provide a proper > reason for this delay at the earliest. > > Kindly ensure that such lapses do not occur in the future and keep the > updates consistent. > > Regards, > Hr Dept of absec lab > --0000000000003d30ad063b31e922 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear HR Team,
Thank you for bringing this matter to my = attention.
I would like to clarify that from my end, all issues have bee= n resolved and the work is progressing as expected. The delay in sharing th= e work plan for the dates mentioned (28th, 29th, and 30th) was due to exten= sive team discussions that extended beyond our usual working hours.
Duri= ng our team meeting, which ran past 9:30 PM, we identified several critical= issues that required immediate attention and resolution. Since these techn= ical issues can arise at any time during the day and need prompt fixing, we= decided to finalize the work plan only after ensuring all concerns were pr= operly addressed.
Additionally, on July 15th, I had requirement discussi= ons with the team to align on project specifications and deliverables, whic= h also contributed to the overall planning process.
I want to emphasize = that these delays were purely work-related activities and should not be con= sidered as leave or absence from duties. The team was actively engaged in p= roject discussions, requirement analysis, and problem-solving during these = periods.
Moving forward, I will ensure better communication regarding an= y delays in documentation updates, even when the delay is due to extended w= ork sessions.
Thank you for your understanding.
Best regards,
Priy= anka Nath


On Thu, Jul 31, 2025 at 9:44= =E2=80=AFAM soumyaranjanl= enka@abseclab.com <soumyaranjanlenka@abseclab.com> wrote:
Dear Team,
Thank you for bringing this matter to my attention.
I would like to clarify that from my end, all issues have been resolved and= the work is progressing as expected. The delay in sharing the work plan fo= r the dates mentioned (28th, 29th, and 30th) was due to extensive team disc= ussions that extended beyond our usual working hours.
During our team meeting, which ran past 9:30 PM, we identified several crit= ical issues that required immediate attention and resolution. Since these t= echnical issues can arise at any time during the day and need prompt fixing= , we decided to finalize the work plan only after ensuring all concerns were properly addressed.
I want to emphasize that this delay was purely work-related and should not = be considered as leave or absence from duties. The team was actively engage= d in project discussions and problem-solving during this period.
Moving forward, I will ensure better communication regarding any delays in = documentation updates, even when the delay is due to extended work sessions= .
Thank you for your understanding.
Best regards,=C2=A0
Soumya Ranjan Lenka
From:= hr@abseclab.in <= ;hr@abseclab.in>=
Sent: Wednesday, July 30, 2025 11:01 PM
To: priyanka nath <priyankanath187@gmail.com>; Soumyaranjanlenka <<= a href=3D"mailto:soumyaranjanlenka@abseclab.com" target=3D"_blank">soumyara= njanlenka@abseclab.com>
Cc: Satya <satya@absecmy.com>; Pravakar <pravakar@abseclab.com>
Subject: Missing Work Plan & Sheet Updates (28, 29, 30)
=C2=A0
Dear Team,

It has been observed that the work plan was not shared and the sheet was not updated for the dates 28th, 29th, and 30th. Please provide a proper reason for this delay at the earliest.

Kindly ensure that such lapses do not occur in the future and keep the
updates consistent.

Regards,
Hr Dept of absec lab
--0000000000003d30ad063b31e922--