Miniserv error - Use of uninitialized value $be in concatenation

what does the following error mean?

Use of uninitialized value $be in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 227, line 218.
Use of uninitialized value $qstart in concatenation (.) or string at ./mailbox-lib.pl line 2034, line 218.

Use of uninitialized value $bs in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 203, line 218.
Use of uninitialized value $be in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 203, line 218.
Use of uninitialized value $bs in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 211, line 218.
Use of uninitialized value $be in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 211, line 218.
Use of uninitialized value $bs in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 212, line 218.
Use of uninitialized value $be in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 212, line 218.
Use of uninitialized value $bs in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 227, line 218.
Use of uninitialized value $be in concatenation (.) or string at /usr/share/usermin/mailbox/index.cgi line 227, line 218.

and the relevant code lines in /usr/share/usermin/mailbox/index.cgi

if ($showfrom) {
push(@cols, $bs.&view_mail_link($folder, $id, $in{‘start’},
$m->{‘header’}->{‘from’}).$be);
}
if ($showto) {
push(@cols, $bs.&view_mail_link($folder, $id, $in{‘start’},
$m->{‘header’}->{‘to’}).$be);
}

# Date and size columns
push(@cols, $bs.&eucconv_and_escape(&simplify_date($m->{'header'}->{'date'})).$be);
push(@cols, $bs.&nice_size($m->{'size'}, 1024).$be);
$rowtds[$#cols] .= " data-sort=".$m->{'size'};

# Spam score
if ($folder->{'spam'}) {
	if ($m->{'header'}->{'x-spam-status'} =~ /(hits|score)=([0-9\.]+)/) {
		push(@cols, $bs.$2.$be);</code>

Howdy,

For an issue like that, I’d suggest filing a bug report. Jamie may need to take a look to see what’s causing that notice.

If you aren’t seeing any actual problems, it’s likely not causing any problems, but we’d also like to prevent unnecessary errors and warnings in the logs.

-Eric

Howdy,

For an issue like that, I’d suggest filing a bug report. Jamie may need to take a look to see what’s causing that notice.

If you aren’t seeing any actual problems, it’s likely not causing any problems, but we’d also like to prevent unnecessary errors and warnings in the logs.

-Eric