Can Green-Flame Blade be cast twice with the Hunter ranger’s Horde Breaker ability?

I am currently working on a multiclassed Ranger/Sorcerer character, and I have decided to take the Hunter ranger archetype. The Horde Breaker option for the Hunter’s Prey feature seems to allow me to use the green-flame blade spell twice in one round.

Horde Breaker reads:

Once on each of your turns when you make a weapon attack, you can make another attack with the same weapon against a different creature that is within 5 feet of the original target and within range of your weapon.

This ability does not mention taking the Attack action, just making an attack.

The green-flame blade cantrip (SCAG, p. 143) reads:

As part of the action used to cast this spell, you must make a melee attack with a weapon against one creature within the spell’s range, otherwise, the spell fails. On a hit, the target suffers the attack’s normal effects, and green fire leaps from the target to a different creature of your choice that you can see within 5 feet of it. The second creature takes fire damage equal to your spellcasting ability modifier.

Green-flame blade also requires you to make an attack roll.

Am I missing anything, or can I cast green-flame blade twice in one round using this ability?

Is there a limit to how many enemies can be attacked using the Hunter ranger’s Volley, Horde Breaker, and the second attack?

From other questions on here, I know that both Horde Breaker and Volley can be used together, as discussed here: Do the Hunter ranger's Horde Breaker and Volley features interact?

Is there any limit to how many enemies you can attack using this combo if they fall into the 10-foot radius of the initial Volley?

Say there is a shield-wall type of formation of enemies, all nicely lined up side by side and multiple rows deep. In theory, based on the phrasing of Volley, you can use Volley to attack every creature in the 10-foot radius, potentially attacking 16 targets – and you can use Horde Breaker on any that are within 5 feet of the point of origin. If the origin is the middle of the group, then possibly 8 additional targets – and then use Volley again for your second attack as a Hunter, making 40 total attack rolls in this situation (assuming they are all lined up nicely). Is this correct?

In my current campaign, we have stumbled into a war-torn region where large armies of Orcs are massing (my preferred enemy), and I’d love to use this loop hole if they end up lining up nicely for me.

Remote Server filtering on Horde with INGO AND SIEVE

I have the following setup running:

Server 1: Horde Groupware 5.2.22 Server 2: Dovecot, postfix

Now I’m facing some troubles with my filter rules. My filter on server1 do not work at all.

Server2 has sieve enabled and I can telnet from server1 to the sieve port on server2 succesfully.

My backends file have this configuration:

$  backends['sieve'] = array(     'disabled' => false,     'transport' => array(         Ingo::RULE_ALL => array(             'driver' => 'timsieved',             'params' => array(                 'hostspec' => 'server2',                 'logintype' => 'PLAIN',                 'usetls' => false,                 'port' => 4190,                 'scriptname' => 'ingo',                  'debug' => true,             ),         ),     ), 'script' => array(         Ingo::RULE_ALL => array(             'driver' => 'sieve',             'params' => array(                 'utf8' => true,              ),         ),     ),     'shares' => false ); 

My hooks file have this configuration:

class Ingo_Hooks {      public function transport_auth($  driver)     {         switch ($  driver) {         case 'timsieved':             // Example #2: Use IMP password/username.             $  ob = $  GLOBALS['registry']->call('mail/imapOb');             return array(                 'euser' => $  ob->getParam('username'),                 'password' => $  ob->getParam('password'),                 'username' => $  ob->getParam('username')             );         }         //return true;     } } 

Running tcpdump on server1 filtering for the sieve-port shows no traffic (except when we do the telnet test). Running Horde in debug-mode shows any error.

Is there something that we have forgotten here?