[Mailmunge] make test failures

[Alan Premselaar]

Dianne,

Thanks again for the quick response.
I switched my nameserver setting from my internal DNS server to a public
one and the 91-getmx.t passed so perhaps it is some DNS caching issue.
Thanks for pointing me in the right direction there.

I also updated the IO::Socket::SSL via CPAN and all the tests pass as
expected.

Thanks again!

Kind regards,
Alan

On 2021/06/14 20:17, Dianne Skoll via Mailmunge wrote:
> Hi,
>
> I spun up a CentOS-7 LXC instance.  91-getmx.t failed the first time,
> but now always succeeds.  I suspect a DNS caching bug.
>
> 10-smtp-forward.t always fails because the version of IO::Socket::SSL
> that ships with CentOS 7 is 1.94, and Mailmunge::Test::SMTPForward
> requires at least 1.994.  I didn't realize this until now.
>
> If you are not planning on using Mailmunge::Test::SMTPForward, you can
> ignore the test failure.  Otherwise, you'll need to install a newer
> version of IO::Socket::SSL from CPAN.  Running the following:
>
>         yum install cpanminus
>         cpanm -n IO::Socket::SSL
>
> fixed it for me.
>
> Regards,
>
> Dianne.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x04556E8B7F1CA2C5.asc
Type: application/pgp-keys
Size: 28330 bytes
Desc: OpenPGP public key
URL: <http://www.mailmunge.org/pipermail/mailmunge/attachments/20210614/8f1aea9e/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://www.mailmunge.org/pipermail/mailmunge/attachments/20210614/8f1aea9e/attachment-0001.sig>