Sounds good, thanks!

On Mon, Aug 14, 2023, 7:20 AM Neil Bowers <ne...@neilb.org> wrote:

> Hi Timothy,
>
> I’ll see if I can get in touch with TTAR, so give me a week or two to try
> different avenues. If I can’t track him down, or don’t get any response,
> then I’ll give you co-maint on TTAR’s behalf.
>
> Cheers,
> Neil
> On 12 Aug 2023 at 22:38 +0100, Timothy Legge <timle...@gmail.com>, wrote:
>
> Hi
>
> Do you have any contact info for TTAR author of Crypt::OpenSSL::AES
> the c...@ttar.org does not work.
>
> I have been reviewing older Crypt::OpenSSL modules and updating for
> OpenSSLv3 and I am happy to take over maintenance to this one if you
> have no active contact information.
>
> TIMLEGGE
>
> Not sure what happened in my previous emails - one was garbled and the
> other less than clean.
>
> Timothy Legge
> timle...@gmail.com
> timle...@cpan.org
>
> ---------- Forwarded message ---------
> From: Mail Delivery Subsystem <mailer-dae...@googlemail.com>
> Date: Sat, Aug 12, 2023 at 1:11 PM
> Subject: Delivery Status Notification (Failure)
> To: <timle...@gmail.com>
>
>
> Address not found
>
> Your message wasn't delivered to c...@ttar.org because the address
> couldn't be found, or is unable to receive mail.
> LEARN MORE
> The response was:
>
> 550 5.1.1 The email account that you tried to reach does not exist. Please
> try double-checking the recipient's email address for typos or unnecessary
> spaces. Learn more at https://support.google.com/mail/?p=NoSuchUser
> r2-20020a50d682000000b0052545d31bfasor306441edi.3 - gsmtp
>
>
>
>
> ---------- Forwarded message ----------
> From: Timothy Legge <timle...@gmail.com>
> To: c...@ttar.org
> Cc:
> Bcc:
> Date: Sat, 12 Aug 2023 13:11:07 -0300
> Subject: Crypt-OpenSSL-AES
> Hi
>
> I have been going through some of the older OpenSSL perl modules and
> updating fro OpenSSL 3. Are you still interested in this module? If not can
> you assign COMAINT or FIRSTCOME to TIMLEGGE on pause?
>
> Or reply with approval and I can ask the pause admins to make the change.
>
> regards
>
> Tim
>
>

Reply via email to